Hacker News new | comments | show | ask | jobs | submit login

The problems with browsers compared to web apps are well described by the OP, but I just don't understand the author's solution. Have everyone do their own thing? Make me download an app for every website I visit?

This seems like the worst possible outcome:

> Why do all browsers have to support the same standards? This only limits their innovation, and limits web developers.

Shouldn't the solution instead be a new, more powerful standard? (Ignoring how pie-in-the-sky this is.) As in, not band-aids like AJAX and Flash, but a from-the-ground-up standard? After all, 99% of iPad apps have the same basic capabilities; there's no reason you couldn't have a standard which replaces HTML which could fully cover those apps. Then, if you have a need for a really specialized service, you can create a dedicated app.




Ah yes, the new more powerful standard. Agreed by Google, Microsoft, Apple, Oracle, etc, etc, etc, etc.

Standards are for lowest common denominator and almost by design are never, ever simple enough - see e.g. SOAP vs REST, XML vs JSON (Dave Winer be damned).


I'm not sure what your point is. REST [1] has beaten SOAP as the de facto API standard, and JSON has beaten XML as the de facto standard for portable data structure.

[1] Notwithstanding: http://news.ycombinator.com/item?id=1304244


I think the point is the "winners" have something in common and this is no accident.

XML and SOAP came out of "let's invent new formats and protocols"-type standardization, while REST and JSON were products of (essentially) one guy looking at a simple, existing, well-known concept (HTTP and js object literals, respectively) and putting a new frame around it.


I understand what you're saying and broadly agree with you; though I'd point out that Roy Fielding, the guy who articulated REST, was one of the principal authors of the HTTP specification.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: