When you only need to hammer a nail every once in a while, any hammer will do. When you’re a roofer, you better have a roofing hammer.
If you don’t spend your life in a terminal and just need to edit a file, vim isn’t for you. If you want to learn complex strings of arcane wizardry to not only make your life easier but amaze your underlings, use vim.
From a developer standpoint you’re taking someone’s baby, cloning it into a language they don’t understand and deprecating the original. Worse, if you’re not actually interested in taking over the project you’ve now made it abandonware because the original developer lost heart and the person looking for commit counts on GitHub has moved on.
Obviously these extremes don’t always apply, but a lot of open source relies on people taking a personal interest. If you destroy that, you might just destroy the project.
I don’t know if they’re conflating rendering with display or just assuming those GPU are at max TDP 24/7, but they’re way off on actual energy consumption.
There seems to be a lot of recent articles attacking datacenters, particularly those involved in LLM “ai” work. This feels like one of those articles.
I’m not saying we shouldn’t keep them in check, but I also don’t like being manipulated by “grass roots initiative” marketing companies, particularly on Lemmy.
Using the max power use of a video card to math this is ridiculous. It’s not at full TDP pushing this content. They aren’t playing max FPS 3D raytraced gaming, they’re playing videos.
Under normal circumstances I wouldn’t expect any privacy between processes on a desktop OS under the same UID.
If you use Chrome’s password manager on Windows your password database is unlocked with your password upon login and is available to every process you run.
There’s only so much you can do, as an app, to protect against OS deficiencies.
The desktop app on Windows is a sacrifice of security for convenience.
Your primary search term here should be the USB ID. Model numbers can help but so many things are rebadged or go through cost optimization where different revisions require entirely different drivers.
Plug in the device and see what dmesg or lsusb says. Search for that device ID, if you don’t find any good matches search for the manufacturer ID – frequently a newer model builds on older models code bases and APi.