You think Linux is living a Renaissance with Gaming and New Non-Technical Users?
I've switched to Linux as my daily driver sometime late 2019, and initially went with Manjaro (with XFCE, because I was using an ancient laptop back then) after it was recommended to me. The installation and set-up process was pretty quick and painless.
When I got my current desktop, I stayed with Manjaro. However, I got some problems with my NVIDIA video card's drivers. Proprietary support for it was dropped shortly after I got my system. Nouveau was decent. I can use my system at the very least, but gaming was a lot iffy. I didn't mind since I don't really do gaming, however. Since then, I've moved on to Arch, btw. Also since then, I've got an AMD card. Neither of them gave me much problems. A lot of my problems with Arch deal with the changes I've made to my configuration.
This is basically my Linux experience: when it works, which is 90% of the time, it's excellent. When I do have some problems, 90% of the time (9% overall), I can get by with a few internet searches. That remaining 10% of the time (so, 1% overall), I feel that I'm just too smooth-brained to resolve it, and even attempting to resolve it seems to be a foolish errand.
While lot of help is out there online, I don't appreciate the elitist tone of some of the more Arch-specific fora—they're helpful, but I'll never want to put myself to the position of asking those people for help, not with how newbs are treated. That is basically why I said earlier that I have no confidence that Linux will soon be able to shed its "for advanced users" image. Newbs to Linux don't have the knowledge to "properly ask questions" required by a lot of those online fora. IMO, they only resort to asking questions online when they're knee-deep in shit and are desperate for an answer. Being faced with an "elitist RTFM attitude" when one's already desperate for help doesn't alleviate that "Linux is too hard for me" image.
So, yeah, there's that.
90% of the time, Linux works swimmingly fine. 9% of the time, some problems might arise, but an online search (Arch Wiki is very helpful in this regard) and digging around some fora would resolve it. 1% of the time is where you'd find yourself wondering if you're smart enough for Linux. Unfortunately, it only takes a handful of (second-hand) bad interactions (thread closed with no answers, being told to RTFM, being told that the query is too vague without any helpful nudge towards a refinement of the query, etc.) to sour a user's impression of Linux as a whole.
I must admit that newbs not knowing how to ask questions isn't a problem exclusive to Linux alone. However, Windows and even Mac have the luxury of larger user numbers, and more importantly, paid staff to address user queries. With Linux, as a rule, the ones answering user questions are but other users volunteering their time and effort to answer questions. It's understandable that facing the same malformed question again and again is infuriating. However, I think it takes time and effort to be rude. IMO, it's just better to walk away from a possible unpleasant interaction. Of course, this wouldn't help the user at all, but I'd rather see a thread with no replies than someone telling me to shut up and read the fucking manual. Perhaps there'd be someone more helpful who'd step in before the thread inevitably gets locked due to inactivity.
I don't want to be negative about Linux, but if the "year of the Linux desktop" is to happen, this is one crucial thing that we (and I count myself in being a Linux user myself) must address. Every Linux user is, whether we like it or not, an ambassador, and how we deal with newbs/noobs asking questions will shape their impression of not just us, but Linux as a whole. I think there are a lot of people who are still on the fence, not because of Linux's capabilities, but because of a pre-concieved notion of what a Linux user must be: tech-savvy and above all, willing to devote the time to learning about their machine and OS. A lot of people aren't like that. Moreover, I think there are some people using Linux (even Arch, btw) who aren't like that, but ... yeah.
At any rate, I agree with you that a lot more people will be able to get by with a pre-installed Linux system. I think Linux is ready for being a mainstream daily driver.
Oh, yeah, I don't think not having native MS Office apps isn't that much of a deal-breaker. I personally use Libre Office, and despite some hiccups (their documentation do have a lot of problems IMO), it's got a decent amount of feature-parity with MS Office. For almost all of what I want to use an office suite, Libre Office would suffice. For the exceptions, I can usually find a workaround.
Overall, I'm happy with my Linux system—to the point I barely even touch Windows anymore (my SO installed Win10 on a separate SSD for me so that I can dual-boot), but I've got no reason to log on Windows. I might have had some problems (mostly of my own making), but with that small exception of times that made me wonder if I'm smart enough for Linux (or yeah, basically Arch), I'm more than content a huge majority of the time.
I'm sorry for the rambling wall of text, and I hope I've put my message across clearly.
This is just based on my personal experience, so please take it with a grain of salt.
Rather than gaining ground from the wider population, I see the recent rise in Linux usage as coming from a pool of "interested users" who have in one way or the other, had some prior exposure and thus interest in Linux. These people have already been interested in making the jump, but have been held back in one way or the other.
This shouldn't be taken as discounting the recent advances amongst Linux distributions, however. Personally, the reason why I've made the jump is two-fold: dissatisfaction with Windows, and the advances in Linux itself that have made the jump far less intimidating than ever before. Not being a gamer, however, advances in Proton was only seen as a bonus, though a very welcome one.
Only one other person in my current friend group daily-drive Linux, and like me, they already have had experience with it beforehand. There are some other people I know of who have used Linux, but still, they all have had prior experience from school or work. For everyone else I know of, if they've even heard of Linux, they think of it as "for advanced users" and as one contact put it "way above my pay grade". Unfortunately, in so far as personal experience goes, I don't have confidence Linux will be shedding that image anytime soon.
As for the Steam Deck, I am guessing it'd be similar (with a lot of caveats) to how people see Android. It'd be seen as a separate thing, and not occupy the same mental space as "desktop Linux". For one, it being a hand-held system will reinforce that difference, and people aren't as willing to tinker about with their handhelds as people are with their desktop systems. Steam Deck's OS might as well be BSD or even Temple OS as far as the ordinary user is concerned. I am hoping I am wrong here, however, as interoperability might make a difference here: if people can install and use their desktop programs to their Steam Decks in as much the same ease as installing an Android app in their phones, then perhaps the choice of OS here will make an impression on the users and not just the tinkerers.
Despite saying all that, however, I still think Linux is undergoing a renaissance. There's quite a lot of improvements going on even as we speak. Usability, in a very general sense, like being able to daily-drive Linux without being hampered by a lot of issues, is way better than it was when I first used a Linux machine in a school computer laboratory close to twenty years ago. Advances like this is starting to pull people who are curious, interested, and already leaning towards making the jump—and if this trend continues, will lead more people into using Linux, leading to more people contributing towards advances, and so on.
Back when I tried it, I only had it in one device--which is great, since I dunno if I can do it on more than one device, let alone worry how a hardened Firefox mobile would even look like.
I actually don't remember if the settings change with updates. But I suppose they don't (as they don't either with Librewolf). What I meant with "hard to maintain" is basically keeping note that the hardened Firefox config doesn't behave like vanilla Firefox (and isn't expected to). Making some temporary changes to accommodate a "necessary evil" website, you'd have to make note what setting you "temporarily" have to change it to, what the hardened config should be for that setting, and most importantly: remembering to change it back to the hardened config.
So, I guess it's not really a matter of maintaining the config than being aware of all those config changes (from default). With LibreWolf, I'm just brushing it off as "yeah, that's how LibreWolf works."
More importantly, using Firefox (or any of its forks) would mean less people are dependent on Google's Chromium. With less people depending on Google's Chromium, the less Google can swing its weight around, imposing its dictum on unsuspecting users.
I tried using hardened Firefox before moving on to use LibreWolf. Manually hardening Firefox is arguably more powerful than what you'd have with LibreWolf out of the box, but the effort involved in making those changes in the settings and remembering what they are (what they were by default, and what they were changed to) makes it hard to maintain.
I looked it up and it looks great. Currently downloading it to give it a try. I wonder how it compares to LibreWolf though.
Yeah, I remember the IT department at work back then (circa 2006) recommending Opera to me. It had features that are more or less mainstream now, like tab reloading on a timer, and all that while running smoothly than any other browser I've used at that time.
Since then, I've tried a lot of browsers like Vivaldi and Maxthon, but for some reason or the other, like being bloated, or being taken over by entities I don't trust, had found a reason to move to a different browser. Currently using LibreWolf, and I hope I won't have any reason to switch browsers anytime soon.
My first computer was a hand-me-down Toshiba T3100. I was around ten years old at the time, in the late 90's. The portable computer, was way far different from any computer I've seen thus far. It also came with a printer, but I don't think I managed to make it work. The portable computer only had a 20MiB hard drive, and memory that can be measured in kibibytes. Its hard drive has already been reformatted, and had MS-DOS 6.21, Windows 3.11, as well as some DOS games installed in it.
I didn't really bother with the DOS games, but I've had a lot of fun playing Chips Challenge on Windows. However, a huge chunk of time went into me just messing around with QBasic. Later on, when I had programming classes, I installed Turbo Basic, Turbo Pascal, and Turbo C in there for homework and projects.
It could have lasted far longer but I couldn't resist myself opening it up. I didn't have a lot of trouble opening it up, but had a bit of trouble putting it back together. It didn't survive my prying though, and it got shoved into the storage.
Just recently, a few years ago, I found out that it's a bit of a collector's item, and was even expensive back when it was new. I couldn't have known it at that time, nor would I have cared, but I still regret not taking care of it a bit more.
Thanks for the explanation. Prior to our exchange, I didn't even know such a thing is possible. It's wonderful, though to be honest, being as technologically klutzy as I am, I might find it easier to just buy a different set of hardware for my win10 to use, if ever, and disable any networking capabilities (because if it's no longer supported, it needs to be taken offline).
Again, thanks!
I swear, I can read the first part of your first sentence just fine, but I don't understand what it means, lol!
I tried to look it up, and as far as I understood it, it's a technique that allows a virtual machine to access a physical GPU directly. I guess that means that even if your VM is elsewhere (a server or wherever) it can still use the GPU you have. But the more relevant part is that since your Win10 install is on a VM, it can't do shit on the rest of your system, and the GPU access is just there so that it won't run as slow as shit when gaming, right?
Huh, that's interesting. I've gotten used to using the Grub menu every time I had to reboot (which is quite often), but it defaults to the Linux installation (auto-selects the Linux install after a timeout), so if I want to go to Windows, I'll just have to make sure I catch the Grub menu.
I've kept a Windows 10 install on a separate SSD for the programs that stubbornly refuse to run on Linux (games, in my case). However, I won't be upgrading that to Windows 11. I'll just reclaim that SSD for other purposes and use Linux exclusively.
I can only speak from experience but from my understanding most people’s knowledge of Linux is derived solely from wanting to do something and then figuring out how to do it, instead of studying a list of “things you must know to use Linux”.
I second this. While I've been exposed to Linux quite a while back (Linux Mint, circa mid-2000's if memory serves me right) and was given a "Linux basics" rundown, I only started daily-driving Linux around late 2019, and by then, my knowledge of Linux pretty much have faded. It still hasn't prevented me from getting re-familiarized with Linux (Manjaro, then Arch). Of course, some bit of knowledge would help, but a lot of the Linux basics you'd need are already out there if you need it. Just look things up if the need arises.
Also, I find having to learn something I don't immediately would need to use not very productive, even counterproductive at times since it leads me to having a mindset of "I should already know this, why am I being so stupid?"
So yeah! I second this sentiment of "just use your computer, look things up if you have to, it's not going to hurt."
And oh, don't be afraid to mess with your computer from time to time. If you're concerned about breaking things, you can install the distro of your choice into an old laptop or something, and use that as a place to "mess things up."
Edit: I forgot that OP already is using Linux in a virtual box. OP can use that as a laboratory to "mess things up."
Thanks! I'm glad to have inspired you.
While KDE Plasma offers a whole lot of options for customization, it's really daunting especially if you're just new to it. What really helped me is to just go with a little bit of customization and tweaking at a time. As I got more experience, I started to want more and more which lead to a lot more customization and tweaking.
I'm weaning myself away from it. However, it's still unavoidable in my case because my work uses it. Thus, my work-related appointments and such are on there, which is one of the reasons why I had that widget in the first place (to monitor work-related appointments, deadlines, etc).
I've been working on it on and off since I've started using this system. It started with just the basics, tweaking the defaults, wanting more, and so on and so forth.
I usually can spend an entire (weekend's) afternoon just tweaking things, making a change here and then, and observing if I like the changes I've made. Rinse and repeat that over a period of several months.
I actually am trying to get it hooked to my google calendar. That widget used to support that feature and have it work. However, recent changes have borked that functionality, and I can't seem to find another widget that does the same.
Or I can just move away from google calendar.
Details:
The right screen has the following (KDE Plasma) widgets:
- Alpaca Clock and Weather (top-left)
- Event Calendar (bottom-left)
- System monitor sensor widget of various settings (the five widgets on the right side)
Both screens have side panels containing only a icon-only task manager. These side panels are installed on the outer edges of the screens instead of on the bottom as might be customary.
The top panels of both screens act as one whole top panel. However, both of them also have a collection of widgets (Window Buttons, Window Title, and Window AppMenu) that (should) only come into play if a window is maximized on a screen. That's what is demonstrated in the first screenshot of the OP.
As for the theming, I used WhiteSur-dark as the global theme, with particulars overriden as follows:
- Plasma Style: Monterey-dark
- Colors: MontereyDark
- Colors, accent color: custom (#636363)
- Window Decorations: Prof Dark
- Window Decorations, Window border size: No Side Borders
- Icons: Ultimate-Plata-Suru-Plus…
- Cursors: macOS-Monterey
- Splash Screen: 1604-Arch-Splash
As for the mouse gestures. I've got a mouse with additional buttons, so I used one of those extra buttons to indicate that I'm going to do a mouse gesture. Those mouse gestures are taken by KDE Plasma and act like a custom shortcut, which executes an action, which I defined via KDE Plasma.
The gestures are as follows:
Go to the previous Virtual Desktop: move right, move up
Go to the next Virtual Desktop: move left, move down
Move the active window to the previous screen: move right (a bit), move left
Move the active window to the next screen: move left (a bit), move right
Move the active window to the previous Virtual Desktop: move down (a bit), move up
Move the active window to the next Virtual Desktop: move up (a bit), move down
EDIT: Added theming details
That time was when I was forced to switch from Windows 7. I switched to Linux, found that I can do there most things I usually do on a computer anyways, and never looked back. It reached to the point that someone had to give me an entire SDD with a windows installation just to coax me to use Windows 10. I rarely touch it nowadays, and every time I do, I end up being frustrated with it.
Indeed, the phenomena of people being assholes to newbs isn't limited to Linux. Heck, I even witnessed this in a lot more places other than you've mentioned (like language learning). There is just this fact that people don't start out with enough knowledge to get the help they need. We need to be aware of this fact.
What makes this really problematic in Linux circles is how Linux is "a minority of a minority." Being a computer nerd is relatively rare enough, and being a computer nerd who is into Linux is even more rare. This makes the knowledge of the mores and culture of Linux circles even more scarce.
If you ask me, one good way to alleviate this is to "adopt a noob". That is, someone helps a new Linux user along, not only helping them in the installation, configuration, and maintenance of their system, but also how to interact online with other Linux users, and more importantly, how to get and use the debug data one would need to resolve their problems on their own, or ask for more expert help if necessary—or even to make a bug report or feature request if all else fails. All of this in the hopes that this new Linux user grow into someone who can pay things forward. That way, not only can users get the help they need, but also give the contributors the information they need to improve things (assuming more people make good bug reports and feature requests).
But if we're going by Linux user stereotypes...
Seriously though, I've seen this happen in real life, having been a member of a Linux users group in university. That group didn't go as far as teach members how to retrieve and use system debug data though, let alone how to ask for help online, but simply being part of a group of people who help each other with the inevitable challenges of using a Linux computer system is oftentimes enough to encourage someone to keep at it.
TBH, if it weren't for that group, I might have stayed a Windows user, with my Linux experience being negatively colored by schoolwork and struggling with
vi😅