I guess there is no way to mod up an ignore - a no-reply or, as other people might put it, mental hygiene? -- No, I'm really serious. It might actually be implemented. Do we need it? - which is not identical to us wanting it.
Seems the only thing left is making the autoupdate mandatory by virtue of the EULA and then charge subscription for that as well. The offer for virus protection by subscription might be just the thing to ease the barrier here.
End result: OS itself is primarily subscription based for all practical purposes. No more trouble with pirated copies. Needless to say, all in the name of making the world more secure.
Apologies for using ambiguous wording. What I really meant was "with experience in none, one, or both of the open and closed source worlds," which is not the same as skills. Nobody would want to hire people without any skills whatsoever.
It would be interesting to see how the costs converge over time. That experienced people will have a good head start is sure, given that it matches the required field. But non-experienced pepople might be faster to adapt to the specific situation, and I believe that they may be less prone to lock into one or the other approach.
Of course, measuring this may be near impossible. Results will depend heavily on the individuals and their flexibility of thinking.
More often than not the root of these TCO estimations favoring proprietary OS are attributing the cost of switching and / or re-training. But I believe this is blaming the chicken for getting caught by the fox.
Has anybody analyzed the TCO of hiring skilled vs. non-skilled people for the IT department?
Slashdot Mirror
I guess there is no way to mod up an ignore - a no-reply or, as other people might put it, mental hygiene?
--
No, I'm really serious. It might actually be implemented. Do we need it? - which is not identical to us wanting it.
Seems the only thing left is making the autoupdate mandatory by virtue of the EULA and then charge subscription for that as well. The offer for virus protection by subscription might be just the thing to ease the barrier here.
:-)
End result: OS itself is primarily subscription based for all practical purposes. No more trouble with pirated copies. Needless to say, all in the name of making the world more secure.
Of course I'm just theorizing
Apologies for using ambiguous wording. What I really meant was "with experience in none, one, or both of the open and closed source worlds," which is not the same as skills. Nobody would want to hire people without any skills whatsoever.
It would be interesting to see how the costs converge over time. That experienced people will have a good head start is sure, given that it matches the required field. But non-experienced pepople might be faster to adapt to the specific situation, and I believe that they may be less prone to lock into one or the other approach.
Of course, measuring this may be near impossible. Results will depend heavily on the individuals and their flexibility of thinking.
More often than not the root of these TCO estimations favoring proprietary OS are attributing the cost of switching and / or re-training. But I believe this is blaming the chicken for getting caught by the fox.
Has anybody analyzed the TCO of hiring skilled vs. non-skilled people for the IT department?