Live data from Hacker News

HTML6 proposal for single-page apps without JavaScript

lists.w3.org

31–40 of 177 posts

Re: HTML6 proposal for single-page apps without JavaScript

#31
post #28

Instead, why don't we eliminate the need for Apps in a browser to require HTML. Right now, our large scale app has one div inside the . It's just an anchor for our SPA built in React js. We should push for browsers that can launch from a .js file, rather than requiring html. Have a base UI.kit that can even keep css, or use javascript to stylize. I'd like the 'base' UI to be as skeleton and simple as possible. We can…

> Instead, why don't we eliminate the need for Apps in a browser to require HTML. Accessibility.

A canvas accessibility api would be great.

Re: HTML6 proposal for single-page apps without JavaScript

#34
post #28

Instead, why don't we eliminate the need for Apps in a browser to require HTML. Right now, our large scale app has one div inside the . It's just an anchor for our SPA built in React js. We should push for browsers that can launch from a .js file, rather than requiring html. Have a base UI.kit that can even keep css, or use javascript to stylize. I'd like the 'base' UI to be as skeleton and simple as possible. We can…

> Instead, why don't we eliminate the need for Apps in a browser to require HTML. Accessibility.

Touche, love the user name. Yes, right now it would seem impossible and browsers would have to support backwards compatibility. What I'm saying is let browsers still support regular html sites. In addition though, be able to specify a 'javascript app'. I see no limiting reason in modern browsers why this would be an issue. At some point, the web has to move forward and say, 'sorry, if you are not running JS, we can't really support you'. Yes, I know the backlash that would come, but we've got to move forward, maybe there is a better way? I'm not sure.

(My project does not require supporting anything below IE 11, it's the greatest blessing, ever.)

Re: HTML6 proposal for single-page apps without JavaScript

#35

Am I mistaken, but this kinda looks like XForms. Why not just use XForms? Edit: Obviously I understand that XForms isn't a viable option these days, but that is kinda my point. Why isn't XForms an option? Those reasons appear to apply to this proposal too...

Because XHTML was killed, when it could have become the XAML of the web, so the circle comes back to "another day another hack".

Re: HTML6 proposal for single-page apps without JavaScript

#38
post #10

I'm not necessarily opposed to something along these lines, except that it's basically already been tried: XSLT was essentially the inverse of this, where data endpoints were annotated with some static rendering descriptors. To me the XSLT approach seems cleaner, in that the URLs the browser is visiting are for the raw data itself, the URL scheme between machine and human is identical, and so on. XSLT also encouraged…

Yep. I used to love XSLT -- working in it finally forced me to understand recursion at, like, a deep cellular level -- but the whole time I was using it I knew it was a doomed language (because most people don't want to have to understand recursion at a deep cellular level just to be able to lay out a damn web page.)

Yet, alongside XHTML it would allow to move HTML to a proper layout engine like most native GUIs have, instead of the hack-a-mole we have to deal with.

Re: HTML6 proposal for single-page apps without JavaScript

#39
This is why you don't let "Editor-In-Chief" do web development. Sounds to me like someone's too lazy to learn JavaScript. When will people stop trying to make HTML into an all-in-one product? It was built to be simple, to provide markup and that's it. That's the magic behind the troika of HTML-JS-CSS. They all deal with individual, meaningful functions to make a site work. Blending function with markup is just bad coding. Thumbs down.

Re: HTML6 proposal for single-page apps without JavaScript

#40
post #28

Instead, why don't we eliminate the need for Apps in a browser to require HTML. Right now, our large scale app has one div inside the . It's just an anchor for our SPA built in React js. We should push for browsers that can launch from a .js file, rather than requiring html. Have a base UI.kit that can even keep css, or use javascript to stylize. I'd like the 'base' UI to be as skeleton and simple as possible. We can…

> Instead, why don't we eliminate the need for Apps in a browser to require HTML. Accessibility.

All major native UI toolkits support accessibility as required by many governments.
Post reply on HN