News for hackers. Stuff that matters.
Re:Web frameworks are transforming from runtime libraries in... by nostrademons on Monday September 11, 2017 @01:06PM (#15220114)
Somewhat relatedly - when a new technology wave gets started, it's usually proprietary, because there are big competitive advantages that can be had by being the only one with possession of a new technology. As details leak out and enterprising independent hackers get interested, commodity or open-source clones emerge, and they get much wider distribution simply because they're cheap or free. The original innovator is caught flat-footed, loses mindshare, and eventually has to adopt the open-source solution when it becomes dominant in the open-source world.

Altair -> Apple -> IBM -> Dell & clones. UNIX -> System V -> BSD -> Linux. MapReduce -> Hadoop. GMail -> Closure Compiler -> Traceur -> Babel. Google datacenters -> AWS -> Docker -> Kubernetes.

Re:Web frameworks are transforming from runtime libraries in... by bsimpson on Tuesday September 12, 2017 @02:38AM (#15225259)
This is a very strange example. Gmail, Closure, and Traceur are all Google products.
Re:Web frameworks are transforming from runtime libraries in... by Ajedi32 on Tuesday September 12, 2017 @10:46AM (#15227662)
And Closure and Traceur are both open source.
Re:Web frameworks are transforming from runtime libraries in... by nostrademons on Tuesday September 12, 2017 @01:23PM (#15229253)
And Babel's the one people actually use.

Within the progression, each new generation is decreasingly tied to a proprietary, revenue-generating product, and increasingly intended for outside consumption. So GMail was completely proprietary and closed off from the outside world. The JS library, compiler, and optimizer from GMail was spun off into Closure, which was widely used across Google products and finally open-sourced 5ish years later, but never got widespread external use because it's very tightly tied to the style of JS development within Google. The idea of JS transpilation was proven by Closure, and Traceur was developed from the outset to be open-sourced and not tied to Google products - but it was developed by a member of the Chrome team, and so the developer perspective was that of how internal Google engineers think, and the development process wasn't really inclusive of outside engineers. Finally, Babel was developed entirely outside Google, based on ideas that had been proven out and were widely disseminated, but it was developed from the start with an open community process.