3 ms·
Well, what would you have replace it? Like most things that become very popular, the web is becoming an os-like platform because it solves a problem. Putting y
by chuckdries 9y ago
Well, what would you have replace it?
Like most things that become very popular, the web is becoming an os-like platform because it solves a problem. Putting your application at a URL is hugely more accessible than asking someone to download something. Maybe not to us HN readers, but to my mom, who's skeptical to a fault of anything that says download, it's huge.
HTML+CSS+JS is everywhere and complete in a way that literally nothing else is. Yeah C is everywhere but (before nowish) you couldn't write a C application once and have it run the same pretty much everywhere.
But chuck, you say, HTML has notoriously bad compatibility and working with it is frustrating. I propose to you that HTML and CSS have so many compatibility problems because of how pervasive it is and has been for so long, and how many different implementations of it exist. Anything is bound to develop compatibility issues when it gets as large as the web.
But you're right, it's suboptimal and other tech has tried to be everywhere. Java and Flash did try, but have you ever used a java applet? They're fine I guess, but they're stuck in a square on the page. You can make a java or flash object take up the whole page and completely control the website but then you run into accessibility issues and complexity on your part.
Javascript has grown organically over the past decades for a reason, and it's being used in this fucked up way because, all things considered, it's the best platform for the job right now
- xtrapolate 9y agoAppreciate your insights. I don't really have an answer to your question. I respect the popularity factor, I just can't help but think that we've had (and still currently have) competing technologies which are far more mature and capable. Not saying WASM won't end up on top in the future. There are plenty of applications today that build on parallelisation, synchronisation primitives, IO, IPC... all of which are already perfectly possible today over the JRE/JVM (as an example), but the same can't be said about browsers today (no doubt that with enough work, it can all change sometime in the future). Just feels like reinventing the wheel.