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.

  • sincle354@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    10 months ago

    I’ve got a Linux work server because VHDL simulations are hella expensive. I have to say that if your team isn’t willing to RTF-Man pages, you end up with a lot of cargo cult CLI processes. No crystalized knowledge or training, it’s hard to start up in it. It’s enough that requiring explicit Linux experience for new hires is preferable. Windows sadly has the familiarity benefit. And don’t get me started on the wacky custom solutions the IT set up circa 2002…