

If it’s “barely a problem in practice” why did you bother to mention it like it’s an active performance issue?
This post is so full of inaccuracies that I don’t know where to begin. I’ll just mention the first thing I noticed: just because drivers are compiled with the kernel doesn’t mean they’re all loaded at runtime. modprobe
exists for a reason.
Nobody who packages debs are updating their applications for jammy anymore. Anything I install is several versions old at this point. Just the other day I tried to compile an application that uses Autocxx, only to find that it requires C++14 headers, and the jammy repo only had up to 12 or 13. I know I can add PPAs or get things other ways, but it kind of defeats the point of a package manager if I’m constantly hunting for things outside of it.
I’m looking forward to Cosmic, but I’m curious if it will delay the 24.04 LTS release. 22.04 is pretty long in the tooth at this point.
Try Sidebery instead.
Show me a standard that was destroyed by EEE and I’ll show you a standard that never took off in the first place.
XMPP says hi.
The suggestion here is that the type of game that can thrive on a subscription service is either a small one that benefits from better curation and visibility or a live-service one that can make up revenue on the backend by charging all the new players microtransactions (the new store shelves are inside the games themselves).
I’ve been saying this since Game Pass launched: it encourages scummy monetization. The kind of games that come to it are going to have more and more content locked away behind microtransactions to make up the money lost by not selling copies. It’s going to gradually become full of “free” to play garbage, and people will accept it because they didn’t pay for an individual game outright.
This is making perfect the enemy of good. What’s actually going to happen is people are going to use “password123” because they can remember it.
You’re free to suggest another method of comparing the two languages’ performance. This is the best we’re have, and Rust wins in every single benchmark shown there.
Citation needed.
I never said it did. I simply pointed out that it’s demonstrably faster than Swift.