As for Windows, I don't know of any methods to get Windows running outside of macOS, but many people utilize Parallels for Windows apps or the desktop experience.
I stay away from “Full stack” dev roles. Keeping a UI current with all their demands and so many dependency updates is a full time job on its own. Then on top of that I need to implement back end systems and stay on top of security? Hire two people you cheap bastards!
Anyone who says the guy was "enjoying the show differently" is an idiot. They were just screwing up the show for the people behind them, and they're probably a sociopath.
As for possible reasons he was on his phone;
Argument with partner/friend - possibility resulting in them not going - spilled into the show via text (should have left)
Planted security, already seen the show a dozen times, just waiting for something rowdy enough to require intervention
Music/event/venue reviewer (seen all kinds of reviewers who apparently have a 5 second memory insist on taking notes in-situ. Movie critics are the fucking worst about this.)
Work "emergency", fixing from phone
Could probably come up with more, but it would be along these lines.
Like I said, he was playing games on his phone, so there was no emergency. We watched him do a crossword puzzle while we were trying to not be distracted.
Okay, yeah, either the security guard thing, or maybe their group was elsewhere and they were the designated driver or something? I dunno, totally dumb that they we in the middle of the audience and not in the back row or in their car.
As a newbie in this space, I had interactions with a few distros over the years and lately switched (hopefully) permanently.
My first experience was with Mint 10 years ago. Installing it would cause some GPU driver defect (AMD card) and would turn the whole login screen into an epileptic checkerboard pattern with no way of doing anything. It took me a few reinstalls and a ungodly amount of googling to find a solution which involved opening the terminal at boot process. You can only imagine how frustating that can be for a newcomer.
Later in time I had Ubuntu on my laptop which had a bug that wouldn’t spin up the CPU fan and it would simply overheat and shutdown. I had to take it to a technician to find out what was causing the random shutdowns.
A year ago I decided to try Debian on my desktop PC as many have praized it for it’s rock-wolid stability. It didn’t want to work on my PC. No internet connection and some weird bugs. Took me two-three days to get ti to work and I still don’t know what exactly fixed it as I have applied every possible solition I came across.
Much later, aka now, I decided to go with Bazzite on my desktop as many have claimed excelent support. I wanted to install the mimalloc because I play Factorio a lot and a few reddit posts claimed 20% UPS improvement over the stock scheduler. After downloading the source code and following the 4 very easy steps, cmake would throw some random eerors at me claiming some critical files were missing, although they were right there in the usr directory. Turns us Bazzite some some issue and Fedora 40 compiled the code in seconds without any issues.
Conclusion: Linux users, which are very tech savvy or work in that space, know what to do when things don’t work out, while the rest of us keeps googling and crying over error messages for things that seem trivial. You never seem to know if it’s you, the system or your hardware.
It’s something we’ll take for granted. With enough time and experience, you could fire off a one liner to fix a problem in less than a minute. For most people thst could take an hour, and they’d probably give up within 10 minutes
Could you point me to a good place to start learning how to troubleshoot? I added Unbuntu as a dual-boot to my gaming rig a while back, and when it works, it’s great. But as soon as I hit an error, I drop back to Windows because I know how to fix shit there.
First suggestion: commit to using Ubuntu for a set period of time. Could be a week, could be 2 hours. When you encounter issues, force yourself to stay on Ubuntu.
What you’ll find is that at first, errors will seem like gibberish, then you’ll do some snooping online, and find out how to access some log files or poke around your loaded modules. You’ll slowly learn commands and what they do.
Eventually, something will click, ie; “wait a minute, I just checked to see which kernel modules are loaded, and I’m missing one that was mentioned in my error, that must mean I need to load that module at boot.” You load that module, reboot, try your command again, and bam, everything works. You’ve learned how to troubleshoot an issue.
The best way to learn Linux is to immerse yourself in it. You can’t efficiently learn German if, every time you hear a phrase you don’t understand, you switch back to English, right?
Just come ask here when you have trouble, and we’ll try to help.
When troubleshooting, the biggest thing is searching the web honestly. But some more things to help you out: look for logs. Linux has loads of logs and sometimes can tell you how to fix the problem.
Logs may not be immediately apparent. Some programs have their own log files that you can look into. Sometimes, if you run the program from the terminal, it’ll print out logs there. Otherwise, you read look through journalctl, although this has logs for everything so might be harder to search.
Another useful tip, particularly for system tools and terminal tools, is manual pages. Just run man ls and replace ls with any command, you’ll get the documentation on how to use that tool.
The first thing I’ll say is the reason you’re more comfortable with Windows is because you’ve been using it for however long and learning to deal with the issues it has. The same needs to be done on Linux. You’ll have to learn how it works just like you forgot you did for Windows.
Second, along with logs like other users said, you have to know how to use a search engine well. Most issues will be easy to solve, but some may take some searching. The Arch wiki is a good resource even if you aren’t using Arch.
I recently had the realization that I’ve just been putting up with Windows bullshit forever recently when a friend asked me for help with their work PC. They’re a Mac user, but they just started working from home and have been provided a Windows laptop. They sent me a bunch of rushed texts when their headset stopped working. They changed the default audio device after they launched the program. Which never works on a Windows PC. I never have that problem because I have just learned to live with it, I don’t even think about it anymore.
Now I’m really starting to notice all the little things I put up with from Windows on my machine. To be fair my Linux machine is just as janky but at least I can say I made it that way. I keep telling myself to ‘tidy’ my Linux machine up but I never do, it still plays games just fine. Usually. If I didn’t fuck with it.
The wiki has some information and should correspond to how Ubuntu specifically is configured. You can ask for ubuntu specific help in those communities. You can also ask here and on several Linux communities on Lemmy.
The Arch Wiki I find to be more in depth than the ubuntu wiki. Of course some things may differ from Ubuntu’s defaults but I found it a useful resource when using Ubuntu.
Finally I suggest you learn a bit about how Linux works in general, what is in what directory, what is wayland and xorg, understand how drives are named etc and some understanding of the terminal (moving around in directories, how to use sudo etc, no need to learn to make bash scripts).
kbin.life
Oldest