3 ms·
Because we write extensible instead of composable software. We do not distribute functions, but apps. How many instructions do you need in assembly to compute
by TheMode 3y ago
Because we write extensible instead of composable software. We do not distribute functions, but apps.
How many instructions do you need in assembly to compute `1+1`? How many instructions do you need to open your search bar, get the calculator and do the calculation?
We also make software responsible for way too much. Cross-platform is a joke. How can we expect developers to consider every platform? Obviously they will switch to some other magical solutions that promise support (and deliver overhead)
Software lacking composability also mean that if the developer doesn't provide a feature, users will most likely never have it. It is therefore encouraged to over-feature everything in case somebody somewhere want it.
- api 3y agoIt seems like sometime around the late 2000s we literally gave up on the idea of composability as a profession. I think economics has a lot to do with it. People buy apps and services, not functions and components. All the money is at the tail end of the development process when something becomes product, and that involves a lot of things that are at odds with composability.
- TheMode 3y agoIt is also due to how unstable software is. Is it possible nowadays to write a simple calculator function and ensure that nobody will ever need to care again for the rest of the century? Making software stable (including for example the web spec) would go a long way improving efficiency.