In a certain way, it does feel close. We can’t figure out how to go faster than light, but we could theoretically get to a significant fraction of c and 20 years isn’t such a long time to plan for in terms of getting a probe there to start relaying messages that take 20 years to get back.

I mean, it’s the span of a career, but people could conceivably work on the launch and live to see it return data.

GNOME 3 introduced the current shell paradigm where you don’t really have a start menu but a variety of searches, integrated indicators, per-app desktops with a dock etc.

Before, it was far more conventional experience like Plasma/Windows/Cinnamon are now. GNOME 2 was forked to be the MATE desktop if you want to check it out.

Basically just start with what you’re aiming to enable and work backwards (as you’ve started to do). With judicious use of grep find out where that symbol is defined. If it’s in arch configs for other arches but not your own, it’s probably that.

There may be better tools out there to do this, but in my experience just sleuthing it out a bit will answer your question. The Kconfig system can be complex, but the files are pretty readable.

So it’s not fully self hosted then? I can’t see how it would do that without registering you with their own service as a middle man. Seems like that kinda defeats the purpose.

Sorry, why would Jellyfin be different from Plex for exposing to the Internet? Dynamic DNS service / static IP and router port forwarding just like any other self hosted thing. It requires a user/pass to login as usual. VPN is nice but not required.

It’s possible that it’s not supported on your arch.

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.

For XP, the machine KVM presents as may be too new, but that isn’t an issue with non-virtualized QEMU.

TIOBE is weighted toward languages that have existed for a long time by virtue of counting lines written / skilled engineers etc. but the speed at which Rust is climbing that list is a better indicator. Also, a lot of the languages above it wouldn’t be appropriate for anything like a DE.

But you’re right, it’s hyped, I just think the hype is real.

This is a weird take. Rust is very popular and is the current heir apparent to C for systems level stuff. It’s a great choice to start a new DE/toolkit.

As for the rest, you’re right the end user doesn’t care about the language their graphical app is in, but the developers fielding their bug reports and making fixes/features sure do.

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.