3 ms·
Eh, I think things were a lot worse during the heyday of Flash and Java applets. Sites have been delivering this kind of content since WebRunner in 1997. At lea
by pcwalton 11y ago
Eh, I think things were a lot worse during the heyday of Flash and Java applets. Sites have been delivering this kind of content since WebRunner in 1997. At least now we have an open, vendor-neutral, consensus-based standards process and a commitment to multiple major open source implementations, which is something we never had with Java or, worse, Flash.
- vmorgulis 11y ago> ... which is something we never had with Java or, worse, Flash. I liked a lot Java Applets. It was fantastic to be able to draw pixels or use a toolkit in a web browser at that time. I gave up Java near after the dispute between Sun and Microsoft about J++. Java was far less interesting for me without that feature.
- lmm 11y agoI had a thought a couple of days ago: what if Mozilla (or anyone) made a web-native runtime for Java applets to replace the plugin, in the same way that Mozilla made a web-native PDF renderer to replace that plugin? That would give us the good of Java applets - a well-specified, mature, backward-compatible bytecode with a built-in security model - without the bad of performance, poor UX, and your programs being trapped in a rectangle that the browser knew nothing about.
- pcwalton 11y agojs2me: https://github.com/szatkus/js2me https://github.com/szatkus/js2me It didn't get much traction because nobody really wants to program in Java on the client if there are alternatives.
- lmm 11y agoJava ME is not Java. Compatibility with existing applets would require implementing more. Java is not the best (though it's better than JavaScript, and android contradicts your claim), but JVM bytecode as a target is great.
- Silhouette 11y agoI think you and I must be looking at different 2016 Webs. In the one I see, content is increasingly locked up in closed, proprietary and/or centralised systems. In the one I see, standards don't matter much any more because there are no usefully stable browsers anyway. In the one I see, one browser is rapidly becoming so dominant that the existence of several others that were formerly influential and competitive is all but irrelevant for many web development projects, just as happened in the days of the IE vs. Netscape browser wars. We all know how this story ended last time. And yet, here we are watching it all over again and most of us are powerless to do much about it. For all the superficial openness of the modern Web, the reality is that it is now utterly controlled by a small group of browser developers, a small group of centralised content hosts, and a small group of curators, several of which overlap with each other but almost none of which have goals that necessarily align with those of either the average web surfer or the average small content producer.
- vmorgulis 11y ago> ... it is now utterly controlled by a small group of browser developers ... If the group is small, it's mainly because the job is very difficult. All browsers are a big mess and it takes time to be productive. The idea of asm.js is one of Alon Zakai. He explains on his blog all the experiments he made before concluding with that. A quote from the oldest post I know about emscripten: "I want the speed of native code on the web - because I want to run things like game engines there - but I don't want Java, or NaCl, or some plugin. I want to use standard, platform-agnostic web technologies." http://mozakai.blogspot.fr/2010/07/experiments-with-static-javascript-as.html http://mozakai.blogspot.fr/2010/07/experiments-with-static-j...
- bobajeff 11y agoYes there are few full implementations of the Web. I hope eventually a more modular layout engine comes into being that allows for others to create their own implementations of things without having to wrestle with a large codebase.
- vmorgulis 11y ago> I hope eventually a more modular layout engine comes into being that allows for others to create their own implementations of things without having to wrestle with a large codebase. Maybe Servo? The more comprehensible browser codebase I know is Dillo. http://www.dillo.org/dw/html/annotated.html http://www.dillo.org/dw/html/annotated.html http://www.dillo.org/ http://www.dillo.org/
- Sanddancer 11y agoAs a counterexample, I will bring up Flash. The file format's open, and the scripting language is...ECMAscript. So an open vendor neutral consensus based standards process doesn't mean that the implementations themselves are going to be any good.
- comex 11y agoThe file format became partially open in 2008... long after Flash Player became ubiquitous, long after the format was developed and stabilized, without a standards process (excluding ECMAScript), and without any serious attempts to write competing players (after all, Flash was already on the way out by then, plus it would have been harder to take on Flash Player's monopoly of... Flash players, than IE in its heyday). WebAssembly will have several actual competing implementations, not to mention that it's a drastically smaller addition to the existing Web platform.