First point: over time, you need to be able to change your internals without changing your public APIs (which users & ecosystem libraries build on). If you can't do that, you'll be forced to maintain near-static internals (a maintenance nightmare) or else invalidate your ecosytem
-
-
Show this thread
-
Second point: no particular feature or performance advantage of a system can last very long. But ecosystem gravity is extremely tough to replicate, and is the single most impactful element when it comes to *reducing time to solution* for end users (which is the end goal).
Show this thread -
Who would use Windows without the apps? Who would use Python without the libraries? It's not the features. It's the ecosystem.
Show this thread
End of conversation
New conversation -
-
-
This Tweet is unavailable.
-
An example is in order
- Show replies
-
-
-
Software Design Principles: Low Coupling and High Cohesion
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.