Docker's philosophy in a nutshell: 1) solve a painful problem with a simple tool. Ignore the purists criticizing the tech 2) get lots of happy users 3) gradually improve the tech without sacrificing simplicity 4) tech previously reserved for purists is now democratized 5) repeat
I like this approach as long as step 3 is actually possible and affordable. Sadly for many things that's not the case.
-
-
Because of essential complexity? Or just lack of resource to simplify?
-
Or because step changes are hard?
-
Or improvements have to add complexity? You have done a very good job of limiting complexity in
@musllibc while working in a defined domain. Other code often has to also define the domain which can go either way. -
Affordability varies, people often underestimate the affordability of complexity
-
I was thinking from a financial standpoint of being able to afford to go back and fix rather than perpetually chasing new requirements.
-
The key is that happy users create opportunities to fund work. If you start by pleasing the purists, you get an impressive but complex system with almost no users. Eventually resources dry up.
- 1 more reply
New conversation -
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.