3 ms·
>Inability to update internal implementation details inevitably leads to ossification and obsolescence of the whole system. No, in practice I think it leads to
by shiroiushi 2y ago
>Inability to update internal implementation details inevitably leads to ossification and obsolescence of the whole system.
No, in practice I think it leads to growing complexity, because the system then adds additional APIs (e.g., v1, v2, v3, etc.) to support new features, but has to continue to maintain the old APIs for backwards compatibility, leading to lots of extra code and a huge maintenance burden.
- ak217 2y agoYes, precisely. The escalating complexity, maintenance burden and constraints eventually cause the whole system to lose momentum, lose support and become obsolete.
- viraptor 2y agoLike winapi with its ...Ex and numbered functions (NdrClientCall4).
- poincaredisk 2y agoOr Linux with it's numbered syscalls (dup, dup2, dup3).