I’m liking the recent posts about switching to Linux. Some of my home machines run Linux, and I ran it on my main laptop for years (currently on Win10, preparing to return to Linux again).

That’s all fine and dandy but at work I am forced to use Windows, Office, Teams, and all that. Not just because of corpo policies but also because of the apps we need to use.

Even if it weren’t for those applications, or those policies, or if Wine was a serious option, I would still need to work with hundreds of other people in a Windows world, live-sharing Excel and so on.

I’m guessing that most people here just accept it. We use what we want at home, and use what the bossman wants at work. Or we’re lucky to work in a shop that allows Linux. Right?

  • mko@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    2
    ·
    7 hours ago

    We can choose what we want to run at work. I work as with Solution Architecture and Platform Engineering mainly with Azure, PaaS and dotnet solutions. It’s atypical I suppose but surprisingly seamless.

    Doing this in Linux is pretty straightforward and my choice of distro is Ubuntu since last year. I have modified Gnome getting it sorta close to Omakub (the precursor to Omarchy).

    The stack, including Dotnet, C#, PowerShell, Bicep, Terraform and Azure CLI works well. I’m midway in my setup of Neovim and have it working with PowerShell and Bicep as well as an assortment of other LSP’s. Additional tools such as JetBrains Rider, Draw.io and Obsidian with Excalidraw are native and so is LibreOffice. For the few workloads I can’t run natively (basically Visual Studio and Office) I have a VM.

    The major issue I have found in a lot of workplaces with Windows since forever, disregarding the increasing mess in Windows 11, has been group policy lockdowns. IT tend to look at everyone including devs as office workers (assuming Office is the most advanced tools needed), meaning no admin access and blocked apps.