this post was submitted on 28 Oct 2023
488 points (90.5% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54772 readers
412 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Windows and Office were successful in enterprises precisely because they were popular and the familiar choice among staff. They got popular from piracy.
it's a bit disingenuous to think that corporations are using windows just because employees are familiar with that. Unless the work is only using a web browser, you need programs and stuff, you don't simply switch to Linux. Especially when "familiar with windows" for an average employee it just means "know where the icons are, and open Facebook in a browser".
A corporation would surely love to save $100k if they could just have a windows skin on Linux and force employees to watch a 1-hour video on training to use the new system. But then if they need to run [PROGRAM X]? and if they need to run [PROGRAM Y]? And what if some quirk of running [PROGRAM Z] on Wine introduces some bug that causes slowdowns and monetary loss?
They intentionally choose windows, and they will pay whatever Microsoft tells them because:
they can have support from less specialized (=cheaper) techs
they can control everything of their computers from a centralized position. If they want, they can force push the goatse image as the wallpaper on each single employee and nobody could change that.
it works well with the programs they use, and they are in a configuration that can be supported by techs
I think your third point is key, one thing Microsoft does very well is backwards compatibility. We run programs from the 90s in production. It is a nightmare of APIs layered upon APIs, but the programs will run.
My employer is a sizeable tech firm that uses the Microsoft suite. The irony is that developers use WSL because the software they need are on Linux. We haven't switched to Linux just because the IT department doesn't know shit about managing a Linux fleet of devices. They haven't bothered to get the training/certificates because Windows is the status quo for big corps. This will stay this way until the next gen of sys admins form the majority, I guess.