|
|
|
|
|
by kalleboo
1922 days ago
|
|
The biggest problem with Java was that it sucked. Java took too long (and too much RAM) to initialize, was too slow to add features, and had too poor developer tools to become the runtime for the web. Instead Flash took that spot! Only because Flash eventually also ended up sucking too bad (on mobile) did we get the Javascript revolution. If Java sucked less and developed at the same pace as Flash did, but was open enough that the browsers could implement their own <applet> runtime replacements (for instance if Java was more important for the web than for the server, Google may have bought Sun instead of Oracle), we would probably live in a very different world today. |
|
If "mobile" means the Apple iPhone release in 2007 not supporting Flash, I disagree.
The Javascript revolution for serious apps was arguably started by ~2000 Microsoft's XMLHttpRequest() api which other other browsers like Netscape immediately copied. This started the AJAX dynamic web page era ~7 years before 2007. When retrieving new data for a webpage is no longer tied to a user refreshing with F5 key or a HTML form submit() button, it enables a more desktop-like paradigm of apps such as:
- 2000 MS Outlook for Web
- 2004 Google Maps, Google GMail
- 2005/2006 Google Docs & Google Sheets (acquisitions)
These were the type of groundbreaking Javascript apps that convinced many that the often-dismissed "toy language" was viable for complex work. The later innovations such as 2009 Node.js runtime on the server side and 2008 V8 performance optimized js engine in Chrome just further cemented Javascript's domination. The Javascript mindshare momentum was already unstoppable long before Steve Job's declared that Flash sucked.