-95
submitted 1 year ago* (last edited 1 year ago) by mub@lemmy.ml to c/linux@lemmy.ml

Not everything actually requires a GUI, obviously. But anything that requires configuration, especially for controlling a hardware device, should have a fully functional GUI. I know Linux is all about being in control, and users should not be afraid to use the command line, but if you have to learn another bespoke command syntax and the location and structure of the related configuration files just to get something basic to work then the developer has frankly half arsed it. Developers need to provide GUI's so that their software can be used by as many people as possible. GUI's use a common language that everyone understands (is something on or off, what numeric values are allowed, what do the options mean).

Every 12 to 18 months I make an effort to switch to Linux. Right now I'm using Archlinux, and it has been a successful trip so far, except my audio is screwed, I can't use my capture card at all, I had issues with my dual displays at the start, and the is no easy way to configure my AMD graphics card for over clocking or well anything basic at all.

I'm not looking for a windows clone, I love that I can choose different desktop environments and theme many of them to death. I even like the fact there are so many distros. Choice is a big part of linux, but there is clearly a desire to get more people moving away from Windows and until that path is 95% seamless most people just won't. Right now I think Linux is 75% to 85% seamless depending on the use case and distro but adding more GUI front ends would, imho, push that well into the 90% zone.

GUI is not a dirty word, it is what makes using a new OS possible for more people.

EDIT: Good conversation all. This is genuinely not intended to be a troll post, I just feel it is good to share experiences especially on the frustations that arise from move between OSes.

you are viewing a single comment's thread
view the rest of the comments
[-] idlewise@kbin.run 5 points 1 year ago

I was there during the early days. 93/94. Eternal September was in full swing, a year or two before the a.out / ELF Wars turned usenet into a bloody battlefield of technical debate. I was there when 'make menuconfig' was still new to the Kernel build process. Was hell of a lot easier than running 'make config' and answering 500 questions in a row. Back when the only way to install SLS/Slackware was to write 50 floppies and feed them all to your target system.

Even then there was a vocal, arrogant group who just didn't get it. "Devs, if you do this, then Linux will be better". That's it. No offer to help, no offer to implement. Not a single line of code. Just long, irritating screeds to "do better".

And you know, I was there for a bit, too. The sound drivers for my desktop didn't work. What did I do? I figured it out, built out the appropriate drivers and became the maintainer for the soundcard drivers for about a year or so. Not only did I learn a lot about sound drivers in general, I learned the build process, how to submit patches and... And receive shit little comments from end users on how I could "do better".

mhub, Linux "gets better" when "you make it better". What have you done to help? You're not even posting on the Archlinux boards or groups where someone might actually have an idea and can help. You're whining and kicking your little heels on Lemmy/Kbin and providing nothing of value.

This is your wake-up call, dude. If you can't figure it out, then Apple will be happy to sell you a good Un*x workstation. Otherwise, you get to learn along with the rest of us. You are not special. If you can't figure it out, then write your own.

[-] mub@lemmy.ml 3 points 1 year ago

If I had the time I could probably learn the required languager and code my own solution. But that is never the point. You don't need to gate keep an OS that is founded on the ideals of openness. The point of Linux is it can be what ever OS you need. The work done to make desktop enviroments more accessible and function is amazing, and if I'm able to help I will. For example, once I have the solution for my audio issue I'll be posting my fix in a few places. I've done this before for Windows and Linux stuff, and believe in sharing the knowledge. I won't give up until the answer is found, even if the answer is "it won't work". Pushing users away because they don't want to spend days trying to figure out something as basic as audio is not really understnading the point of my post, or helpful to anyone really. Feel free to keep your knowledge to yourself.

[-] idlewise@kbin.run 2 points 1 year ago

If I had the time I could probably learn the required [SIC] languager and code my own solution.

Or... You know... Do anything like "ask a technical question" or even "use ArchLinux forums for support". Something which would actually help yourself. Seems like you have plenty of time to complain about how developers have "...frankly half arsed it"

...You don’t need to gate keep an OS

I'm not "gatekeeping" a single thing. You never asked a single technical question. You sure as hell didn't ask a single technical question in the correct venue. No, you spent your precious time pissing and moaning about developers delivering you a functioning Operating System (for free!) but its not "good enough" because you have sound problems. I had sound problems before too! And I fixed them. Sorry you can't.

Feel free to keep your knowledge to yourself.

Oh man. This line is my personal fave. You have a technical problem. Instead of fixing it you run and bitch about developers on Kbin. Then you bitch about the lack of technical solutions to a problem you never described.

Here's a free tip. Have you thought about shutting the fuck up and go get help from people who can actually help you?

https://bbs.archlinux.org/viewforum.php?id=23

this post was submitted on 21 Aug 2023
-95 points (26.6% liked)

Linux

48073 readers
752 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS