gettodachoppa

If it was done as a desired choice rather than it being driven by economic fears, you're right, we shouldn't care. But for most people, they aren't having kids because they don't have a house, they don't have a stable partner (tangentially tied to economic needs), they just don't have money to raise kids.

With supply and demand, you'd expect a decline in workers would mean higher wages down the line. But the ruling class will always make sure there is endless immigration and free trade agreements to keep the average citizen broke and miserable.

I don't really get people's obsession with security updates for a smartphone. It's not a public webserver, bro. It's a phone. You're the one who decided it was etrash.

Not only is it not reachable by anyone except your mobile provider, but every app is sandboxed anyway. Unless you're downloading random apps every day, why would you care? What do you think is going to happen? Just stick to reputable apps.

You know what I do on my still-supported phone? Set it up, then disable automatic updates, for both Android and the Play store. I update the browser weekly, but that's it. I update the whole manually after a few months or year if I feel I have a good reason to.

It's trivial in C/C++ due to GCC being a first-class citizen in Linux, but idk how it's done for interpreted languages, Java, etc. If anyone can chime in I'm curious.

In C or C++, you just run 'ulimit -c unlimited' in your shell before running your program. When it crashes, a GDB-friendly core dump is generated. Then you can load it in gdb ('gdb myexecutable mycoredump'), and it takes you to the exact line where it crashed, including showing you the stack trace, letting you view local variables at every frame of the stack, etc. Every C++ IDE supports loading a core file, so it's literally an interactive debugger at the time you most need it. It's a life-saver.

Keep in mind you have to compile with debug symbols enabled to be able to make sense of the coredump. However, you can then strip your binary, as long as you keep an unstripped copy around to help you with debugging.

>Why? How? Wuh?

Uh oh, someone's trying to think! You know why. We all know why. But stating it out loud makes you a bad man.

Better to just nod along and pretend it's all OK, especially at work, especially if you're not posting anonymously. And remember to be extra furious at Russia in your comments when someone reminds us that Russia spent 100k in "both sides" Facebook ads in 2015 (an act of foreign interference so ignominous, MSM ink will never stop spilling ink about it). It's what's expected of all of us.

For a long time now I've been seeing this ugly trend in the titles of linked articles.

I wish every HN user would flag any article with these clickbait titles, instead they're always popular. You're encouraging this shameless virality tactic by engaging with content with titles like that. "$popularthing is just the worst" is crafted to engage you. By clicking, you reward the author's behavior.

Please just flag them without clicking the link, until blog authors take the hint and write sensible titles. That's what I'm going to do from now on. Flag on sight.

Least scammy racebait NGO.

Thanks, that link made me much more confident in using Docker.

I mean come on: "Attackers could try to exploit this issue by causing the user to build two malicious images at the same time, which can be done by poisoning the registry, typosquatting or other methods"

So basically ridiculous CVEs that will never affect people not in the habit of building random Dockerfiles off Github with 2 stars. Good to know. Only the 1st one isn't dismissable out of hand, I can't tell if it's bogus like the rest./

Anyone reading this, don't expect a smooth experience for desktop Linux under Hyper-V.

Hyper-V's team only cares about supporting servers. You're not gonna run a full-screen Ubuntu VM without a lot of banging your head against the wall, unless you spend days trawling random Github comments and reddit posts and fixing it whenever it breaks.

I'm the opposite, I need these desktop hypervisors because Hyper-V is trash for anything but a WSL shell or server VM.

I upgraded to Windows 11 for WSLg (figuring it would replace my Linux desktop), and it was buggy trash. You can't even get a high-resolution Ubuntu desktop (from Microsoft themselves, their own quickbox!) without jumping through hoops, searching all over reddit for knowledge obsoleted by the next update, tweaking arcane settings and running misc Powershell scripts. To say nothing of the occasional freezes.

By enabling WSL2/WSLg, your Windows host is now a privileged guest running under Hyper-V as a hypervisor. Which means lightweight desktop hypervisors like Virtualbox run like trash.

I ended up removing WSLg/turning Hyper-V off, using Virtualbox for desktop Linux, and using WSL1 (not 2) to have a quick Linux shell without enabling Hyper-V.

I'm now considering Workstation due to the superior graphics in the guest over Virtualbox.

I'm a casual Docker user, ran maybe 30 images my whole life. I've never used any of these flags and didn't know most of them even existed.

Are these serious threats? I mean it seems like common sense that if you give a malicious container elevated privileges, it can do bad stuff.

Is a VM any different? If you create a VM and add your host's / directory as a share with write permissions (allowing the VM to modify your host filesystem/binaries) does that mean VMs are bad at isolation and shouldn't be used? Because that's what these "7 ways to escaper a container" ways look like to me.

Try reading the author list of AI papers. Even those from western universities and labs. If you can't spot a pattern, then there's Sum Tin Wong with you.

Prepare for the talking points, folks.

Within a day, you'll start seeing the same words used across "journalism" organizations, about how "Iran is a destabilizing force for the Middle East", "sudden, unprovoked attack". Some articles about how wonderful life is for LGBT people in Israel.

If we're lucky, maybe this time around no one will say that Iranians behead babies or stab them in their hospital beds in the maternity wards. It was laid on a bit too thick last time, I felt.

Yep. I do this for Windows. I have a Surface laptop which requires tinkering to get Linux working on it (keyboard doesn't even work out of the box, you gotta use a USB keyboard until you install a custom kernel off Github).

I couldn't be bothered. I just keep Windows running and run Ubuntu in Virtualbox. With an SSD there's no noticeable performance penalty except in accelerated graphics (in which case you should be using VMware).