Re:HTML is the Web
by AnIdiotOnTheNet on Wednesday June 26, 2019 @07:49AM
(#20284010)
I agree. If we want an application platform, let's have something designed first and foremost to be an application platform instead of the garbage fire we've bolted to the skeleton of HTML.
Here's how you do it: create the new platform and its spec. Include an open 'document rendering engine' to replace that portion of the web. For backwards compatibility, go ahead and port a web browser to the new platform. For forwards compatibility, port the new platform to the current web.
Ok, but that isn't "the web."
You are completely free to write and launch a new app that does this today. Just don't try and shoehorn it into my web browser.
> Ok, but that isn't "the web."
It's "the sandboxed, browser agnostic web".
Re:HTML is the Web
by BlueTemplar on Wednesday June 26, 2019 @05:30PM
(#20289406)
I'm not sure that it can be called "the Web" if it doesn't have directly accessible pages linked by hypertext, instead having a single page/app for instance (even if it runs on the top of the HyperText Protocol...)
We're getting into non-Web Internet territory here...
All the HTML+CSS+JS stuff only makes browsers difficult to secure, and also causes bloat and performance issues when they are not needed.
Furthermore, all these hairy web specifications cause compatibility issues, and are a barrier to entry for new browser makers.
If people want HTML or CSS or JS, then they should implement these inside the sandbox. In practice, this would mean that developers would simply include one of the standard libs for rendering HTML, etc., and these standard libraries can be cached by the browser, so their use does not cause performance/bandwidth penalties.