12 ms·
Sticking with an operating system is a matter of convenience. Changing to a new OS requires learning a different way of doing things, be it different keyboard s
by kstenerud 15y ago
Sticking with an operating system is a matter of convenience. Changing to a new OS requires learning a different way of doing things, be it different keyboard shortcuts, different names and locations for everything, different behaviors, and most importantly, a different set of unfixed bugs that you must discover as landmines.
The same goes for using a new piece of software or a new programming language. It's not so much the different paradigm that's the problem (though that does contribute to the friction against change somewhat), but rather the myriad different ways in which it is broken, that you must discover via trial and error.
Black boxes are great so long as you can actually look inside them when they don't work as expected. But even then, one approaches new things with caution because one cannot look inside some code and instantly spot the flaws.
But hey, there's no such thing as flawless, so encapsulation or no, you'll deal with this stuff all the time as a developer. At best, you'd restrict yourself to using popular code (since there would have already been a lot of pressure brought to bear to fix the most egregious flaws), well-established code (since it would likely be more mature, and more help would be available), or code from a reputable source.