this post was submitted on 13 Sep 2023
181 points (73.1% liked)

Linux

47361 readers
1213 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
 

I'm just tired. On the last post about having Linux at our work, many people that seems to be an IT worker said there have been several issues with Linux that was not easy to manipulate or control like they do with Windows, but I think they just are lazy to find out ways to provide this support. Because Google forces all their workers to use Linux, and they have pretty much control on their OS as any other Windows system.

Linux is a valid system that can be used for work, just as many other companies do.

So my point is, the excuse of "Linux is not ready for workplaces" could be just a lack of knowledge of the IT team and/or a lack of intention to provide to developers the right tools to work.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 24 points 1 year ago (2 children)

At best, it means sysadmin have to support both Linux and windows. You're going to double everyone's tools.

This reads like an engineer who is way too invested in using their toolset and thinks everyone else is stupid for not using the same. Like someone who has never worked in management or had to make business decisions. They are looking at it only through a tech viewpoint.

Not only would you need to have an IT team that knew how to manage and support it (which costs money and time) but you then have to train your entire work force which costs insane amounts of time. You would have to do IT training for every new hire for them to even use their computer. That sort of time and training (which takes two employees, the trainer and trainee) costs a lot of money, far more than any OS licensing or end user software costs. Plus the decreased work output while the user to get used to the toolset.

In a software development company, sure, Linux might be a valid option. But it's not ready for most companies main workforce. And it's not a technological issue. It's a human resources issue.

[–] [email protected] 5 points 1 year ago

Many places support MacOS as well, so it would only be a third additional toolset. Plus, there's a ton of overlap between toolchains, which reduces the overhead further. If you're supporting enterprise MacOS, you're probably using Foreman, JAMF, or Puppet with Active Directory.

Not to mention, a lot of places already have Linux servers, so the configuration management toolchains and expertise may already exist in a given organization, unless they're absolutely pathologically mired in the Windows ecosystem. Which, granted, is a lot of places, but you're making it sound far harder than it would be in a real world situation.