I’ve never “got” the appeal of a Mac. But I have to use one for work. Here’s a partial list of everything I cannot do on a Mac, but I can do on Ubuntu. These are all objecti…
I completely agree that the workers do struggle with garbage proprietary software.
The problem is that unless a large scale shift is made, switching to Linux will just cause even more of a workflow disruption because you won’t be able to use the same, albeit garbage tier proprietary software that everyone else has to use.
I’m pro FOSS and I’d love it if my field shifted away from proprietary software but until it does, me switching to Linux only puts me at a massive disadvantage.
It’s not really a cycle like that, I don’t think. It’s usually just because nobody in charge of software (i.e a department’s IT team) wants to deal with the inevitable wave of complaints and "things USED to be good until you started this new BS!" comments.
Sure people may get used to the change in the long run, but often times that involves the person who was originally responsible for the change to get fired and then the next guy replaces him to manage the chaos while saying “blame the last guy!”.
Also, money plays a big factor in this. Microsoft along with a lot of proprietary software companies know how to grease the wheels by exploiting corrupt administrators and higher ups.
I completely agree that the workers do struggle with garbage proprietary software.
The problem is that unless a large scale shift is made, switching to Linux will just cause even more of a workflow disruption because you won’t be able to use the same, albeit garbage tier proprietary software that everyone else has to use.
I’m pro FOSS and I’d love it if my field shifted away from proprietary software but until it does, me switching to Linux only puts me at a massive disadvantage.
“I’m not going to use Linux in the workplace because there are isn’t the software I need for it”
“We’re not going to port our software to Linux because no one uses it in the enterprise”
The cycle continues…
It’s not really a cycle like that, I don’t think. It’s usually just because nobody in charge of software (i.e a department’s IT team) wants to deal with the inevitable wave of complaints and "things USED to be good until you started this new BS!" comments.
Sure people may get used to the change in the long run, but often times that involves the person who was originally responsible for the change to get fired and then the next guy replaces him to manage the chaos while saying “blame the last guy!”.
Also, money plays a big factor in this. Microsoft along with a lot of proprietary software companies know how to grease the wheels by exploiting corrupt administrators and higher ups.