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.
You’ll probably start with virt-manager then move to proxmox. This is the way, it’s only a matter of how long before you realize it’s better.
His point wasn’t to find a CPU, it was to make a political post in a tech community.
You don’t use the technical term, but you do ask.
I’m not against telemetry, I’m against making it hundreds of different hidden options.
We did fine without it for a very long time. We still do with a lot of software. It’s called voluntarily submitting a bug report and/or core dump.
Right. That’s why you build the software against a common library version.
Having every application load their own version of a library into memory is bloat.
The applications have binaries and libraries bundled for multiple arches. I wasn’t speaking to the package manager.
But have you seen how many people dihydrogen monoxide kills every year?
This isn’t a science post, it’s a political agenda post.
Of the future? They’re a duplicate of what Apple was doing with software as far back as the mid 90s.
Every ounce of performance we squeeze out of our hardware is replaced with pounds of bloat like this.
It’s fine for a utility or something you’ll hardly ever need to use, but running every day software like this is a complete waste.
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.