|
|
|
|
|
by demosthenex
3626 days ago
|
|
>> you created a business that depends on a single point of failure that is entirely outs0ide your control > Long term I will have to keep a close eye on Microsoft and see if it's something I have to move away from. I think there is a better analogy. Every business buys widgets from other businesses to enable them to function. There is only so much feedback or control you can get over that product, but as long as it meets your needs that's not a concern. The problem is when you rely on a widget that suddenly has disruptive planned obsolescence, does this new anti-feature impact your business? You control your internal processes, and now an external source is interfering in your change control process. Certainly you plan to replace widgets as they age on your schedule and budget. The issue is when it is forced on you. Free software isn't immune from this either, for example the rolling upgrade bandwagon (ie: its fixed in the next revision but it breaks yours) and the systemd debacle where the choice over important system components was removed. |
|