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.
It’s not reading the clipboard; it’s writing to it.
The kind of game-specific fixes that get added to GPU drivers on Windows are typically added to Proton, not the Linux GPU drivers. Waiting a week for the Nvidia driver so you can be sure it won’t break your system is only a plus in this instance.
EAC works in Proton, as long as the developer takes the time to configure it right.
Pop is great for gaming, and part of the reason I picked it was so I’d have access to more software packages. No regrets.
I wish he would have tested with a distro that at least has a custom scheduler instead of a bloated vanilla Ubuntu install.
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.