Starting with the year 1995, the internet was commercialized. Graphical user interfaces (aka browsers) made information and services from servers accessible also for non technicians. A lot of money could be made through installation, support, third party licensing and custom feature implementation for those servers and browsers. With increasing popularity and user accesses advertisement in the browser became a source of revenue as well.1, 2
"We aimed to provide a “glue language” for the Web designers and part time programmers who were building Web content from components such as images, plugins, and Java applets. We saw Java as the “component language” used by higher-priced programmers, where the glue programmers — the Web page designers — would assemble components and automate their interactions using JS."3
At the top we have a player who thinks he is winning. He develops non standard language features on purpose, as he thinks that this adds cool features and increases the vendor lock-in, which hardens its market position. But then he realises clockwise, that users become frustrated due to many different user experiences. In addition developing becomes more and more frustrating and expensive due to the many different non compatible features. Therefore all competitors agree to work together on some standards, provisioned by the W3C and the ECMA organization. Yet making a standard is a slow process. Implementing some of the standards before finalization and adding cool features on top, promises a competitive advantage. Sounds smart but leads back to the top of the circle. Luckily on each circle also some cool finalized and agreed on standardized features manage the jump out of the circle.
"If WASM+WASI existed in 2008, we wouldn't have needed to created Docker. That's how important it is." 6
Always bet on JS
- First they said JS couldn't be useful for building "rich Internet apps"
- Then they said it couldn't be fast
- Then they said it couldn't be fixed
- Then it couldn't do multicore/GPU
- Wrong everytime!
- My advice: always bet on JS
- "eBusiness a complete text" by Colin J Holcombe 2016, chapter 2.4
- https://www.quora.com/How-did-Netscape-Navigator-make-money, accessed on December 2020
- "LEARNING Node.js" snd edition by Marc Wandschneider 2017, page 2 ff
- Brendan Eich at dotJS conference 2017, recorded at https://www.youtube.com/watch?v=aX3ZABCdC38