3 ms·
That line of reasoning suggests progress isn't being made and we are just reliving the past.
by rsj_hn 7y ago
That line of reasoning suggests progress isn't being made and we are just reliving the past.
- throwanem 7y agoIt's also not a surprise to see a similar process of stabilization play out at a higher layer of the stack, as it previously did at a lower one. Neither is it cause for regret; this is how lasting foundations get built, especially in so young a field of endeavor as ours. "History doesn't repeat itself, but it often rhymes."
- _jal 7y agoThere are multiple reasons for this failure mode, only some of them subject to social learning. Part of the problem is a learning process, and indeed, I think the Javascript world should have learned some lessons - a lot of the mess was predictable, and predicted. Maybe next time. But part of the problem is that we pick winners through competition. If we had a functional magic 8-ball, we'd know which [ecosystem/language/distro/OS/anything else] to back and save all the time, money and effort wasted on marketplace sorting. But unless you prefer a command economy, this is how something wins. "We" "picked" Linux this way, and it took a while.