2 ms·
Part of the reason we're in the shitty everything-is-text/worse-is-better state we're in now is because we haven't invested a lot of effort in the top-down desi
by ModernMech 9y ago
Part of the reason we're in the shitty everything-is-text/worse-is-better state we're in now is because we haven't invested a lot of effort in the top-down design of systems that work really well.
This is in contrast to the current state of development, which was driven by Moore's law and the rapid improvement of single-core processors to consist mostly of imperative programming. As soon as we started hitting a wall in single-threaded CPU improvements and moving to multi-thread and multi-cores, the imperative programming model began to rapidly show its limitations. After all, Von Neumann meant for his architecture to be a prototype, and we went ahead and built an entire industry on top of it.
Leaving everything in the development ecosystem up to market forces has left us in a state that is entirely too complex. There is far too much accidental complexity in developing even the simplest applications today.
If we purposefully design smarter systems, maybe we can cut out layers out of the stack entirely, so worrying about things like distributed execution is a thing of the past for 99% of programmers.
- kmicklas 9y ago> we purposefully design smarter systems, maybe we can cut out layers out of the stack entirely, so worrying about things like distributed execution is a thing of the past for 99% of programmers. Actually I disagree. If your layers represent conceptual abstractions, and not arbitrary divisions of your code stack leaking details from below, then _more_ layers is actually a good thing.