553
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Oct 2024
553 points (98.9% liked)
Technology
58698 readers
4023 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
Win10 LTSC still has quite a few years left.
What's the point of staying with Windows 10? You're just pushing the problem further ahead in time. You might as well start leaning Linux now, instead of waiting til you have no other choice.
I can only speak for myself, but I have always had bad luck with Linux on desktop. Something always breaks, isn't compatible, or requires a lengthy installation process involving compiling multiple libraries because no .deb or .rpm is available.
On servers, it's fantastic. If you count VMs, I have far more Linux installations than Windows. In general, I use Win10 LTSC for anything that requires a GUI and Ubuntu Server for anything that only needs CLI or hosts a web interface.
Try Pop_OS!, it just works.
https://pop.system76.com/
The problem with Linux is fundamental, and no distro is going to solve it.
It's made by devs and for devs. The reliance on the CLI is it's death knell. It will never be usable for normies until this problem is solved but nobody wants to solve it because it's "so great". Even when there is a simple solution, if you search for it, the only thing you will get is CLI solutions.
#1 is compounded by the variety of distros. Meaning often when you do attempt those CLI fixes, they simply don't work and return some sort of generic error with no hint as to what the actual problem is.
Things like changing the default power profile, adding fractional scaling, or changing the default audio device, all things that are super simple on any other OS, are ridiculously convoluted.
Ironic that Windows has become the same way. New functionality is available first as a Powershell command before the GUI control is written. This is because those are two efforts. First you write the function then you need to call the function from a GUI element.
Ironic #2 is that Pop_OS comes with more settings available in the GUI than any other Linux I have used. Maybe you haven't tried it.
To say no distro can fix is nonsense. Any distro can make new GUI elements and because it's open source once the work is done other distros can add the same to their own menus.
Just like it has taken Microsoft over a decade to develop the new settings app, they still haven't achieved feature parity with the control panel. This should make obvious how much hard work is required.
So the solution is that we just need to write more GUI menus for linux and I'm fine with that. It's nice to have the option to use a menu or edit the text file. Then everyone gets what they want.
Not at all. Windows might take a while to get it but they do eventually get it. Linux never does.
Any of the ones that I mentioned?
I didn't say they can't, I said they won't.
I just attribute that to a lack of fucks given. No way the largest company in the world can't figure out how to do that.
At least for me, the whole "made by devs for devs" isn't really the major downfall. It's the fact that it can't be trusted to remain functional in a dynamic environment. I like using the command line, but sometimes that's just not enough.
If I need a specific software package, I can download the source, compile it, along with the 100 of libraries that they chose not to include in the .tar.gz file, and eventually get it running.
However, when I do an "apt update" and it changes enough, then the binary I compiled earlier is going to stop working. Then I spend hours trying to recompile it along with it's dependencies, only to find that it doesn't support some obscure sub-version of a package that got installed along with the latest security updates.
In a static environment, where I will never change settings or install software (like my NAS), it's perfect. On my desktop PC, I just want it to work well enough so I can tinker with other things. I don't want to have to troubleshoot why Gnome or KDE isn't working with my video drivers when all I want to do is launch remote desktop so I can tinker with stuff on a server that I actually want to tinker with.
Most of those CLI instances I had to do on week one.
Since then.. Hardly ever. (On Pop_OS!)