Live data from Hacker News

HTML6 proposal for single-page apps without JavaScript

lists.w3.org

81–90 of 177 posts

Re: HTML6 proposal for single-page apps without JavaScript

#82
Too bad, this is already implemented as a standard (cough-cough Mozilla) as part of Web Components.

http://www.html5rocks.com/en/tutorials/webcomponents/imports...

Reading the comments I felt many people thought this is an official recommendation. It's the mailing list folks, the same place where somebody suggested to replace JavaScript with AS3 because it would solve every problem of mankind.

Re: HTML6 proposal for single-page apps without JavaScript

#83

Earlier quoted context omitted.

+1

There's an "upvote" button, just to the left of the comment above.

You shouldn't use the upvote button for agreement.

On the other hand "+1" and "I agree" and "Well said!" clutter the forum.

How do we solve this?

Re: HTML6 proposal for single-page apps without JavaScript

#84

Earlier quoted context omitted.

There's an "upvote" button, just to the left of the comment above.

You shouldn't use the upvote button for agreement. On the other hand "+1" and "I agree" and "Well said!" clutter the forum. How do we solve this?

Honest question: If not for showing agreement, what is the reason for the upvote button?

Re: HTML6 proposal for single-page apps without JavaScript

#85
post #16

The use of XMLHttpRequest to fetch JSON has come to dominate to the point that people seem to forget that it had any other use, but it is worth occasionally reminding people that the original purpose was to fetch HTML, which the browser turned into DOM nodes via its fast parsing path, which could then be added to the page via DOM manipulation. I fully realize this is not what the linked page is proposing, but it is n…

Uh, the original purpose of XMLHttpRequest was to fetch XML , as its name implies. AJAX stands for Asynchronous JavaScript And XML

I'm not able to substantiate this with links, but I believe the idea was that the "XML" in question was going to be XHTML most likely, rather than generic "XML", though it did support the generic XML use case. I could be wrong, if the original Outlook web interface this was supported for really did return XML that was not XHTML at some point.

It was a crazy time. XHTML was still "inevitable", and people were pretty sloppy with the terms.

Re: HTML6 proposal for single-page apps without JavaScript

#86

I see three problem here, none of which have anything to do with HTML as a markup language. 1. The amount of DOM manipulation required for a relatively advanced single page app is not very efficient, quick or performant. 2. Web apps don't work well without a reasonably up to date javascript engine - users may not even allow Javasacript to be run. This breaks alot of web apps. 3. There isn't an (easy) way to request p…

> Either make your web apps fallback to HTML + CSS So make two Web apps with the same functionality, basically?

Or make one app with an isomorphic base which gets progressively enhanced when JavaScript runs on the client.

Re: HTML6 proposal for single-page apps without JavaScript

#87

Earlier quoted context omitted.

There's an "upvote" button, just to the left of the comment above.

You shouldn't use the upvote button for agreement. On the other hand "+1" and "I agree" and "Well said!" clutter the forum. How do we solve this?

what's wrong with upvoting with agreement?

Re: HTML6 proposal for single-page apps without JavaScript

#89

Earlier quoted context omitted.

Unless you are using IE http://caniuse.com/#feat=history

There are quite a large number of people who still have to support Also the whole SEO issues are not something the sneeze at. I've yet to see a comprehensive approach to this that doesn't involve phantomjs running to serve up HTML to search engine bots. Maybe the bots will just get smarter and we won't have to worry about it but the jury is still out on that. Luckity once I get to stop supporting IE9 I can go to sing…

Yeah I agree the SEO issues. Anything that is dependent on search traffic should not be a single page app, as it will hurt your ranking greatly. Google actually runs JS these days, but you'll still get penalized for slow speed if you load all the content in via JS instead of just serving a flat HTML page to the bot. And that's not even considering Bing and other web bots that almost certainly do not have JS running capability. They will just see an empty page.

If you are making a dashboard or web app which is not intended to be crawled by Google, and not really dependent on search traffic though then single page is a great way to go.

Post reply on HN