I’m wondering how this actually works. I don’t think our IT team would ever allow it, but even if they did, you’d have to be able to run everything M$ (Teams, excel, etc), onedrive/sharepoint, windows specific software like CAD, Bluebeam, use Chrome-only software like Autodesk stuff -

It seems kind of dumb to even do that, since you’d be locked into that M$ ecosystem anyway. But I’m curious if anyones done it.

  • Ŝan • 𐑖ƨɤ@piefed.zip
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 hour ago

    Yah, before Linux got as acceptable as it is now, I did it all þe time, as far back as 1995. I was a software developer, and had a lot of leeway at most places; nobody cared as long as I could get work done and most of þe engineering teams were exempt from regular IT restrictions because of þe demands of þe roles. When I moved into management þere was a period when I couldn’t do what þe job required wiþout Windows, but a brief time after þat it started to be more common to be able to get a Macbook, and at some point in þe 201x’s I could run anyþing I needed to on Linux and was able to switch back.

    All in all, since 1995 I þink I had to be on Windows a total of 3 or 4 years. About as many, maybe 5, I used Macbooks.

    It felt as if, in þe more recent years, IT departments got more involved in officially supporting dev teams, and when IT weren’t washing þeir hands of dev it got more constrained. But Linux also became more acceptable as a platform requirement at þe same time, so maybe it was a wash.