I got my account locked on BLU because I stopped seeding when my RAID went down. I was able to recover the data and get back up in about 24 hours but there was literally no recourse other than begging some random mod’s reddit account.

Always sad to see a tracker go down, but this place was a shit show.

The only thing Samba is really great for is interop with Windows. If that’s not an issue, Dolphin can browse SFTP directly by adding it as a network share (you may need to setup a password-less key pair to avoid having to login). SSHFS is a similar option and works even if the client is totally naive (it just looks like any other mounted FS).

Right. GCC -f optimizations are basically like “how hard are we going to try to be clever” and are, I believe, orthogonal to the actual instructions used. Machine dependent args start with -m, like -march or -mavx etc.

Reason number one million capitalism sucks. We should be happy to turn over dangerous or menial jobs to machines but we can’t do that because without jobs our society views us as worthless.

You can, but it’s not a perfect solution. Mostly because the TVs interface is still designed around this app mentality.

I bought a Samsung TV recently and it’s never been on the internet, but I still have to go to a dead home screen where all of the ads would be just to switch inputs and half the buttons on the remote are for services I don’t want.

This better not awaken anything in me…

John Carmack, author of the Doom engine, is a long time Linux user and for a while the policy was to open source the idTech engines once they had moved on.

However, Doom was hugely popular on its own before this, and was actually more pivotal for making Windows a gaming platform (over DOS).

The reason it runs everywhere is a combination of it’s huge popularity, it’s (now) open source and it’s generally low system requirements.

Honestly, with Flatpak and immutable base systems this is a place Linux is really excelling now too. Being able to show a novice user a shared package manager with a search and a bunch of common apps and them actually install/remove them in a safe manner with a high likelihood they’ll work out of the box (since they come with all their deps in sync independent from distro) is kinda huge.

It does that everywhere, even on non .deb distros.

One thing I’d like to suggest is get most of their forward facing apps as Flatpak and let them install software that way instead of using the system package manager (even if it has a GUI). This jibes with others suggesting an immutable base system.

Obviously this may be more of a concern for older kids, but my kid started with Linux and it did fine… Right up until Discord started breaking because it was too old and they didn’t want to tangle with the terminal. Same thing when Minecraft started updating Java versions. Discord and Prismlauncher from Flatpak (along with Proton and Steam now) would have kept them happier with Linux.

As for internet, routers come with parental controls these days too, which have the added advantage of being able to cover phones (at least while not on mobile data). Setting the Internet to be unavailable for certain devices after a certain time on school nights may be a more straightforward route than DE tools.

For kernel dev it would be a disaster, there’s too much implicit action, and abstractions that have unknown runtime cost. The classic answer is that everyone uses 10% of its features over C, but nobody can agree on which 10%.

As someone forced to get up to date with C++ recently, at this point it’s a language in full identity crisis. It wants so badly to be Rust, but it’s got decades of baggage it’s dragging along.

In a world where Valve controls 90% of what is running on a device with immutable / containerized images, yeah I think Arch makes a lot more sense. A distro focused on rolling release is a lot less likely to hang you up when you choose to update.

Debian is great, but depending on where you are in the release cycle it can be a pain in the ass to stay up to date and, frankly, the last time I ran it, shit like apt/dpkg configuration and so many /etc files and structures just felt like mis-features or too complex for their own good.

This isn’t a benchmark of those systems, it’s showing that the code didn’t regress on either hardware set with some anecdotal data. It makes sense they’re not like for like.

I used (u)xterm for like 20 years before discovering that Konsole is solid and beautiful. My whole tiling setup is backed up with KDE apps now.

And there’s also William Gibson’s entire Sprawl series, which would be very cool to see on a screen.

I love the Sprawl books, and Neuromancer has been in development hell a few times IIRC, but I’m hesitant.

Reading Gibson’s words, they’re so evocative, but a lot is left unspecified and the reader kinda fills in the blanks based on the feeling he is conveying. A show pins everything down visually and I’m afraid even Neuromancer would get rendered as generic cyberpunk without Gibson’s unique style.

I didn’t mind the pie chart, the slices are labeled clearly, no need to use coloring like you have to read a legend.

I’m a little sad this ended up in the ACM. There’s plenty of shit computing can be tried and convicted of as a discipline… This ain’t it.

I test drove a Leaf and honestly it felt bad brand new. I got range anxiety just taking it on the highway and back to the dealer.

So far, I think Tesla has a monopoly on practical EVs. Say what you will about the cars (or their leadership) but the charger network they built out and having ~150 miles of actual range is hard to beat in an existing product.

That’s an interesting thought. I’ve wondered this about Chrome’s market share in browsers too. How much of it is just that so much traffic is now from phones where, even if you have another browser installed, apps open links in embedded Chrome web views.

Yeah, I don’t really see much of an issue here. If you get a defective chip back, it’s probably a good data point to know if it was “abused”. Even if it’s just so you can ask more questions, or prioritize problems that show up on non-OC’d chips rather than flat rejecting an RMA.