2 ms·

Should be, perhaps. Much like Java should be standard and identical everywhere. Differences are inevitable, priorities depend a lot more on real world constrain

Should be, perhaps. Much like Java should be standard and identical everywhere. Differences are inevitable, priorities depend a lot more on real world constraints than fleeting desires. Those proprietary standards exist because the web continues to be rather terrible if your problem's not easily explicated in javascript. The Javascript monoculture that exemplifies the modern web is perhaps the greatest thing holding back good cross-platform development. There's no way to experiment with other languages on equal footing, there's no way to easily extend browsers to provide hooks to native libraries and functionality in a reasonable manner. If the web is the only cross platform environment, then give me my walled gardens, because they're gonna be the only place open enough to actually get things done. The web's a greenhouse, with only the illusion of freedom until you get next to the glass walls.

Mordak 10y ago
> The Javascript monoculture that exemplifies the modern web is perhaps the greatest thing holding back good cross-platform development. I dunno, there was a time when javascript wasn't the only game in town, and it sucked. ActiveX controls for hooking into native libraries, Java applets that assumed you had a JVM installed, subtle differences between javascript and jscript, VBS in the browser.. It was terrible, and the web is better now that they are largely a thing of the past. I'm not a superfan of javascript, but building cross platform stuff in the browser seems easier now that you can count on its ubiquity and everyone is generally on board. Getting things done might be easier in walled gardens, but those gardens aren't usually cross platform.