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.
EAC works in Proton, as long as the developer takes the time to configure it right.
I use OnShape and it works great. There is also Plasticity, a newer CAD application that has a Linux version and looks promising.
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.
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.
Incorrect. If you aren’t using WifiManager
, you don’t need ACCESS_WIFI_STATE
or location permissions. ConnectivityManager gives information to know the connection type with only ACCESS_NETWORK_STATE
, which is granted automatically on install without prompting the user to allow.
And besides that, you should really be checking ConnectivityManager.isActiveNetworkMetered()
instead of the connection type anyway, since the user could be on tethered wifi, for instance.
You can determine if there’s an active Internet connection without checking the wifi info.
Same here in every point, except my wife’s work computer is Windows 10, not 11.
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.