Probably because "the windows way" seems normal and its not something most people even think if it could be done differently, let alone if it should be done differently.
In my, albeit limited, experience of showing someone how to get something on linux, the reaction usually is : "what? ....why? is it installed now?", shortly followed by : "Is there like an app i can use to install what i need instead?"
Nvidia drivers turned me away from Linux completely.
I dont remember exactly but i think it was Fedora 25 or 26 (or around there) where they removed some symbols because some fucking moron thought "they arent used by anything" so they pushed them to torvalds linux repo. And the changed got accepted.
You know what used them? Nvidia drivers.
So after a couple of hours fixing that, which at one point started involving rebuilding the kernel and other things that a normal user shouldnt have to EVER do, i just said fuck it, and installed Windows. That laptop is still running decently as a browser/media player at my folks
Now im just using a Mac as a day to day pc, and a windows laptop for gaming.
Even if i deal with Linux at work on servers, and with containers and stuff, i'll never go back to linux.
I personally avoid start-ups like the plague. To the point where i dont even bother accepting linkedin requests from startup people
Im not that big of a fan of "Big Tech" either, i wouldnt go for something like FAANG, even if maybe the pay would be good
What gave me a happy life was "industry" firms. In my case those were either consultancy/strategy firms (MBB/Big4 ) at first, which was stressful, but had good advancement chances (jumping steps based on performance) and very good networking opportunities.
Now i've retreated in "an industry". In my case a forbes 100 company in the automotive sector (they have cloud systems and develop software too). And life is bliss.
the problem as many have already pointed out around this thread, is that, in an enterprise env. you cant really do that too much anymore. And as a result that starts being felt by non-enterprise shops too.
And you cant really do that because people dont really wanna deal with on-prem shit and server hostings
Tehnically speaking, i am rhcsa certified, i know how to do all of this on-prem, hybrid things. I dont even bother looking at job offers from companies that arent cloud based (even if i would get a 10-15% increase, or more if coming from the financial sector) because, i genuinely cant be arsed to deal with all that bullshit again.
I'm done with caring about disk space, and hw firewalls and configuring bs in linux. Fuck iptables, let me manage everything from a (network) security group. Fuck Traefik and F5 and all this bs, let me just plop an Application Gatway in Azure or API gateway in AWS. Fuck database clusters. At this point, i havent even configured an apache/nginx server in a couple of years. WebApps in Azure are more than fine; and for the rest K8s.
As a result, good "classic" sysadmins are a dying breed even at enterprise level. So they're even more rare and accessible for small/medium sized business. If i go to my IT dept. right now, i can guarantee 80% of them would be completely lost to setup and use an AD, AAD is just too convenient.
That basically leaves you with: move to cloud, or learn how to do all of these things by yourself. And those things take time (to learn and to manage)
It's like deciding to make apps with Perl. Can you do it? sure. But you'll probably have to do it on your own.
In 27 years, I've had exactly two jobs where I didn't have Linux on my desktop, for a total of 5 out of those 27 years. In both cases, I still did all of my dev work on Linux.
It boils down to what kind of jobs you look for.
> So yeah, running cloud services doesnt require sysadmin skills, unless you assume copy pasting from oficial documention "sysadmin skills".
If that's the extent of how you're managing your cloud setup, then I could equally argue running bare metal servers doesn't require sysadmin skills either. When I did contracting, a large part of my income was to come in and clean up after people had relied on "copy pasting from official documentation" as a substitute for actual ops.
The average users mainly cares if their friends are on it. As it stands most people use either iMessage, WhatsApp or FBs Messenger in the west and WeChat in the east.
Signal had at Jan 1st 2021 around 40 mln users. WhatsApp had 2 bln. FBs Messenger had 1.2 bln.
Between Jan 1st 2021 and Augst 1st 2021, Signal also lost around 60% DAUs
Kind'of hard to use a messaging app, no matter how feature rich it is, when you have nobody to message.
Well of course that's the most important one, which goes even without saying, I was just working with (my real life) scenario when you are able to convince someone and then they have to deal with inferior service.
There were 2 things I liked about Signal, shared photos had much higher resolution than compress Whatsapp mess and I didn't need extra app for SMS, I couldn't really care less about privacy, since it's no more private than half of the other messengers.
Dont know about others, but at my $Corp its the other way around. Business keeps pushing and making various channels and threads and stuff in Teams
They're basically doa. Maybe they'll see a bit of traffic when they are made and like 1 day after, but otherwise they're almost immediately abandoned.
One of our architects posted a diagram in the Files tab in a specific teams channel. 2-3 people actually looked and downloaded it. Everyone else got it when it was posted as an attachment to the group chat we were having.
Most people just gravitate to direct messages, myself included. Its not that threads/channels are hard to understand. Its simply that most people cant be arsed to use them and have no interest in following different topics/channels/threads for what they want, thats why even they do use Teams / Threads / w.e (worked with a client that did), you'll have _a lot_ of duplicate threads ... people would rather make a new one that search for whats there.
Notepad++