3 ms·

I'm skeptical of "keep the money local" and "create local jobs" arguments. They sound good, but rarely end up being good economics. Beware: http://en.wikipedia

I'm skeptical of "keep the money local" and "create local jobs" arguments. They sound good, but rarely end up being good economics. Beware: http://en.wikipedia.org/wiki/Protectionism http://en.wikipedia.org/wiki/Protectionism In my mind, the two most important things to consider are: 1) How will worker productivity be affected by the transition? Retraining and relearning can be extremely expensive, especially for information workers who are set in their ways. Not to mention the cost of migrating all a company's documents, scripts, programs, assets, etc. over to the new formats. 2) How is worker productivity affected in the long run? OpenOffice is still far behind Office in usability for the average information worker. The savings in license costs is probably outweighed by the long-term productivity hit. In the grand scheme of things, software is pretty cheap. Wasted man-hours are very expensive. I haven't seen evidence that these transitions to open source actually save money.

rbanffy 16y ago
> How will worker productivity be affected by the transition? It's easy to run a pilot and check. From previous experiences, it drops a little in the beginning, but training smooths the transition. With increased decision freedom due to removed vendor lock-in, governments can both choose the best tool for a given job (even if it's incompatible with, say, MS SQL Server) or develop the missing functionality (because they have access to source code). And governments can cooperate over these developments across regional or national borders. Reduced licensing cost is just the beginning. > especially for information workers who are set in their ways In other words, who can't learn another IDE beyond Visual Studio and other language beyond VB. Oh! Wait! They have to learn a new Visual Studio every couple years. And they had to learn VB.Net (or C#, or managed C++). They already do relearn lots of stuff. And if you have a developer who is not willing to learn, fire him. > OpenOffice is still far behind Office in usability for the average information worker Come on... How many people within Microsoft really stress Words feature-set? 1%? The average "information worker" would be perfectly fine with WordStar and Visicalc. Also, it's not like Office 2003 users weren't completely lost when upgraded to 2007 and more so on 2010. The GDP of a decent-sized country was lost on menu repositioning over Office's history. > The savings in license costs is probably outweighed by the long-term productivity hit. Long term productivity hit meaning these workers cannot learn new things?
- lunchbox 16y ago
  Oh! Wait! They have to learn a new Visual Studio every couple years. And they had to learn VB.Net (or C#, or managed C++). Most information workers are not developers and have never heard of the above technology. Keep in mind that developers are more receptive to change than most computer workers, which is part of the reason MSFT evolves dev technology more rapidly. They already do relearn lots of stuff. Switching to the new version of Windows/Office is not the same as switching to Linux/OpenOffice. To keep things in perspective, the switch to the Ribbon was the biggest change to Office in many releases. Most releases (e.g. Office 2010) require little relearning. And if you have a developer who is not willing to learn, fire him. Long term productivity hit meaning these workers cannot learn new things? It isn't black and white like that. This isn't about not being willing to learn or not being able to learn new things. Many computer workers -- lawyers, managers, schoolteachers, administrative assistants, my parents -- hate having to learn new technology. They'll learn eventually, but it might be slow and costly, and might not result in any productivity boost in the end. Come on...How many people within Microsoft really stress Words feature-set? 1%? The average "information worker" would be perfectly fine with WordStar and Visicalc. It's not about feature set. It's about familiarity, muscle memory, ease of use, efficiency, stability, performance, interoperability, accessibility, backwards compatibility, ubiquity (Office is installed on most PCs), documentation, supportability, and visual polish. Alternate response: why are so few organizations switching to WordStar & Visicalc?

rbanffy 16y ago

> How will worker productivity be affected by the transition? It's easy to run a pilot and check. From previous experiences, it drops a little in the beginning, but training smooths the transition. With increased decision freedom due to removed vendor lock-in, governments can both choose the best tool for a given job (even if it's incompatible with, say, MS SQL Server) or develop the missing functionality (because they have access to source code). And governments can cooperate over these developments across regional or national borders. Reduced licensing cost is just the beginning. > especially for information workers who are set in their ways In other words, who can't learn another IDE beyond Visual Studio and other language beyond VB. Oh! Wait! They have to learn a new Visual Studio every couple years. And they had to learn VB.Net (or C#, or managed C++). They already do relearn lots of stuff. And if you have a developer who is not willing to learn, fire him. > OpenOffice is still far behind Office in usability for the average information worker Come on... How many people within Microsoft really stress Words feature-set? 1%? The average "information worker" would be perfectly fine with WordStar and Visicalc. Also, it's not like Office 2003 users weren't completely lost when upgraded to 2007 and more so on 2010. The GDP of a decent-sized country was lost on menu repositioning over Office's history. > The savings in license costs is probably outweighed by the long-term productivity hit. Long term productivity hit meaning these workers cannot learn new things?

lunchbox 16y ago
Oh! Wait! They have to learn a new Visual Studio every couple years. And they had to learn VB.Net (or C#, or managed C++). Most information workers are not developers and have never heard of the above technology. Keep in mind that developers are more receptive to change than most computer workers, which is part of the reason MSFT evolves dev technology more rapidly. They already do relearn lots of stuff. Switching to the new version of Windows/Office is not the same as switching to Linux/OpenOffice. To keep things in perspective, the switch to the Ribbon was the biggest change to Office in many releases. Most releases (e.g. Office 2010) require little relearning. And if you have a developer who is not willing to learn, fire him. Long term productivity hit meaning these workers cannot learn new things? It isn't black and white like that. This isn't about not being willing to learn or not being able to learn new things. Many computer workers -- lawyers, managers, schoolteachers, administrative assistants, my parents -- hate having to learn new technology. They'll learn eventually, but it might be slow and costly, and might not result in any productivity boost in the end. Come on...How many people within Microsoft really stress Words feature-set? 1%? The average "information worker" would be perfectly fine with WordStar and Visicalc. It's not about feature set. It's about familiarity, muscle memory, ease of use, efficiency, stability, performance, interoperability, accessibility, backwards compatibility, ubiquity (Office is installed on most PCs), documentation, supportability, and visual polish. Alternate response: why are so few organizations switching to WordStar & Visicalc?