this post was submitted on 26 Apr 2022
20 points (91.7% liked)
Linux
48165 readers
1287 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
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The whole "workplace" argument was always dubious to me. If you ever actually have had to deal with those workplace environments on a daily basis the workers are constantly struggling with issues of how shitty their standard proprietary software is. Their productivity could always be improved by switching to FOSS.
I completely agree that the workers do struggle with garbage proprietary software.
The problem is that unless a large scale shift is made, switching to Linux will just cause even more of a workflow disruption because you won't be able to use the same, albeit garbage tier proprietary software that everyone else has to use.
I'm pro FOSS and I'd love it if my field shifted away from proprietary software but until it does, me switching to Linux only puts me at a massive disadvantage.
"I'm not going to use Linux in the workplace because there are isn't the software I need for it"
"We're not going to port our software to Linux because no one uses it in the enterprise"
The cycle continues...
It's not really a cycle like that, I don't think. It's usually just because nobody in charge of software (i.e a department's IT team) wants to deal with the inevitable wave of complaints and "things USED to be good until you started this new BS!" comments.
Sure people may get used to the change in the long run, but often times that involves the person who was originally responsible for the change to get fired and then the next guy replaces him to manage the chaos while saying "blame the last guy!".
Also, money plays a big factor in this. Microsoft along with a lot of proprietary software companies know how to grease the wheels by exploiting corrupt administrators and higher ups.