zacharypinter
Joined 18 years ago
Joined 18 years ago
Minor typo at the bottom:
s/wite/write
By the time a project gets large enough it starts optimizing for its major stakeholders. New use cases or new ways of rethinking common use cases come along, and the small libraries that approach it from scratch have a narrowly-defined advantage. If the advantage is significant enough (e. g. virtual dom for browser UI), then new frameworks start being written around them, bringing back some but not all of the features of the older frameworks.
At some point (different for each user/use case) the newer frameworks have enough functionality that people start considering them over the older ones for new projects. When enough of that happens, the older frameworks start looking like yesterday's software.
http://ia.media-imdb.com/images/M/MV5BMTY2MjQ2MzAwOF5BMl5Ban...
And it suggested Nick Offerman :)
Cool exploration though!
It strikes me that this is a pretty good insurance policy against a poor implementation of Hyperloop being used as an argument against its feasibility. SpaceX/Musk gets to put out a proof of concept track and pod without committing to building the full thing themselves.