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.
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 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.
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.
Same here in every point, except my wife’s work computer is Windows 10, not 11.
I still want Material back.
The nice thing about open source is that you can just contribute the feature if it’s important to you instead of needing to make an external utility to do it.
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.