Has anyone looked at the source of his site? www.futureclaw.com
Man, serioulsy? This is the worst site I've seen in a while!
HTML6 proposal for single-page apps without JavaScript
131–140 of 177 posts
Re: HTML6 proposal for single-page apps without JavaScript
#132Nice, now it only needs some scripting language. I am sure you could invite something in a few days....
WTF?? Please please, just start over!
Re: HTML6 proposal for single-page apps without JavaScript
#133Re: HTML6 proposal for single-page apps without JavaScript
#134This proposal is trying to take a common web design pattern, MVC, and make it part of the official spec. HTML is a _markup language_, it's ridiculous to use it as anything but a semantic language. Here's my HTML6 proposal: There’s a standard design pattern emerging via cascading style sheets, where content is styled directly via CSS. Everyone’s into it because the layout looks so much nicer. Since this is so common n…
> HTML is a _markup language_ It might have been designed as a language for web based documents. Though this is not what the web is used for today, consumers want applications not documents. And we are already hacking away on top of those documents to give them that (despite the web not being intended as such).
Consumers are given applications not documents.
Re: HTML6 proposal for single-page apps without JavaScript
#135Earlier quoted context omitted.
XSLT is still good to learn -- I think it's conceptually sound, but its implementations are often terrible. I think the big pain points for most people are how finicky XML is in general, but also that any libs you use to generate your XML and translate it require an absurd amount of configuration. Years ago, I saw all the weaknesses in mixed PHP/html for building pages, but all the server-side templating languages lo…
XSLT is conceptually sound indeed, a transformation of tree structures. But the requirements and real-world usage cases thrown at it are often terribly suited for it. Real applications just don't fall neatly into tree transformations. I inherited a financial reporting web app using XSLT as the rendering mechanism. Requirements included things like running totals (state!), suppressing leading values when repeated betw…
Just in case you're using XSL still, you could use to let you quickly do subtotals by summing the node set of items that match whatever grouping level you're on when you emit the last item in the group.
...snip...
Re: HTML6 proposal for single-page apps without JavaScript
#136This proposal is trying to take a common web design pattern, MVC, and make it part of the official spec. HTML is a _markup language_, it's ridiculous to use it as anything but a semantic language. Here's my HTML6 proposal: There’s a standard design pattern emerging via cascading style sheets, where content is styled directly via CSS. Everyone’s into it because the layout looks so much nicer. Since this is so common n…
Don't speak ill of people with or infatuation as HN is built on these tags. At the time of writing this comment, there's around 300 tags on the page and over 100 ones
So, basically watch what you say buddy :)
Re: HTML6 proposal for single-page apps without JavaScript
#137Earlier quoted context omitted.
Or make one app with an isomorphic base which gets progressively enhanced when JavaScript runs on the client.
Yes, but if you're doing a true "SPA" then "progressive enhancement" really does just mean having two versions of everything.
Not any more - once you can prerender the "SPA" on the server and use the same codebase to rehydrate it on the client and take over - which you can do today with React and soon with Ember - then with the right setup the "progressive enhancement" bit can be "am I on the client now? let's do some extra stuff" implemented as part of the same component.
e.g. here's a form that uses the same React component to render on the server, to handle regular form submissions and render redisplay when invalid and to progressively enhance with live validation and ajax form submission when JavaScript is available on the client: https://isomorphic-lab.herokuapp.com/add-thing
Re: HTML6 proposal for single-page apps without JavaScript
#138What is this moonspeak?
Modern web apps do so much more than what this proposal is trying to solve.
React + Relay/GraphQL is much more likely to be the next real big step forward on the horizon of web/app development.
Re: HTML6 proposal for single-page apps without JavaScript
#139This proposal is trying to take a common web design pattern, MVC, and make it part of the official spec. HTML is a _markup language_, it's ridiculous to use it as anything but a semantic language. Here's my HTML6 proposal: There’s a standard design pattern emerging via cascading style sheets, where content is styled directly via CSS. Everyone’s into it because the layout looks so much nicer. Since this is so common n…
Don't speak ill of people with or infatuation as HN is built on these tags. At the time of writing this comment, there's around 300 tags on the page and over 100 ones So, basically watch what you say buddy :)
, I don't think there's an excuse. we know for sure that it is not out of incompetence but it was probably easier to write at the time and nobody bothered to fix it because it doesn't really matter.
For the , it is probably not the case here as this is just a text based site but sometimes it is easier to center an image by that tag when your site is partitioned in many margins it is not as easy to center some stuff, or you might just prefer to add a tag.
I also like
, it really makes more sense to me and easier to write. It doesn't really break anything either.
I wonder how many there are, like me, think that and
are actually really nice things to have?
Re: HTML6 proposal for single-page apps without JavaScript
#140What happened to web components ? isn't supposed to solve these issues ?
I wonder the same. Isn't that the quasi standard way of doing this?