151–160 of 177 posts
"These javascript frameworks are all trying to do this, but none of them do it easily and they’re always being redesigned."
Things are being redesigned because there are flaws and limitations. Making something, and stamping it as "HTML6" doesn't automatically make it perfect. It would simply hinder the development further.
Earlier quoted context omitted.
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,…
Earlier quoted context omitted.
And today you can use that markup and shim the transition you want with js - and still gracefully downgrade.
But wouldn't having it in the HTML mean you don't need the js? And then it wouldn't need to downgrade in modern browsers at all.
This 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 :)
Lots and lots of very bad ideas here -- backwards-incompatibility with previous versions of HTML is always a good litmus test that a proposal hasn't been thought through, as is "hey let's restructure everything around this one currently-fashionable design pattern". (I kind of love how he just casually embeds a SQL interpreter in the browser, too, that's a nice finishing touch.) But the main thing is that this doesn't…
This is definitely not the site I'd have in my signature when talking about the emerging trend of single-page apps and proposing a new standard. It's such a non-standard site, and feels clunky and clumsy.
These single-page apps are becoming pervasive but they are also fundamentally breaking the internet. Here are some common ways in which they are broken: 1. History is screwed up. You wanted a back button that took you back to the content you were looking at? Sucks to be you. The content you were looking at was dynamically loaded after ten different buttons you clicked, and now that the page is loaded fresh those butt…
1 & 2 are a basic feature of JS MVC frameworks. I get that some people still probably mess this up, but there's no excuse to do so at this point. 3. Irrelevant/FUD? No normal user 'saves' web-pages, unless it's something like a receipt, which any sane dev would make a separate html page and not part of the app. 4. is totally false as screen-readers support JavaScript. 5. is false/strawman as any half-sane SPA developer still authenticates using a regular back-end framework and I've no idea what 'If you app loads content from a server that isn't yours' has to do with single-page apps.
Earlier quoted context omitted.
, 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,…
There's nothing wrong with font tags on HN. You might not realize that the pages served on this site are machine-generated!
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?
This is interesting, but like others I think HTML should be kept strictly for templating, and this adds an unnecessary amount of logic. It might be tempting to see this as removing complication, but in actuality it will probably add to it by reducing separation of concerns. I think it would be good for less ambitious projects, but in the end it would cripple the building of more ambitious ones. If we already have Ang…
HTML does not do templating, either.
https://html.spec.whatwg.org/multipage/scripting.html#the-te...
Earlier quoted context omitted.
Isn't "good" just as subjective as "things I think are true"?
The problem isn't subjectivity, it's groupthink. "Good but wrong" posts are better than "bad but correct".