4 ms·

From an engineering standpoint there are surely some valid points here but I have to say that I don't think things are all that bad. HTML,CSS, and Javascript s

by oblib 9y ago

From an engineering standpoint there are surely some valid points here but I have to say that I don't think things are all that bad. HTML,CSS, and Javascript separate the layers of a web app fairly nicely. It's all free for the learning and using and even distributing, and it comes with a huge community to lean on for support where many, if not most, of any questions you might have are already answered. Those parts work pretty well and have a huge user and developer base. You don't just toss that out and tell everyone they need to start over. To even imagine that you first have to ignore the real value of it, which is truly immense. So much so that in reality you cannot ignore it so whatever you do has to be compatible with it, or at least accommodate it. I have to admit this leaves me curious about what "Part 2" will offer.

jiggunjer 9y ago
> HTML,CSS, and Javascript separate the layers of a web app fairly nicely. Except they don't. Most devs aren't even aware of what divs they are using for pure styling vs semantically correct ones. They think all the html they write is by definition semantic. Then there are the less frequent but even more insidious cases where css is used for content.
- oblib 9y ago
  Does that really make a difference? Seems to me that's a feature that's generally described as "more than one way to do it" and the goal is getting the app working and shipped not to appease some outside critic's sense of semantics.
  - jiggunjer 9y ago
    Styling separable from content is the direction W3 wants to go. So being aware and adhering as much as possible should improve performance and long-term maintenance burden. I agree the tradeoff probably isn't worth the extra time needed to carefully structure your html and do css acrobatics. I just get triggered when someone claims the holy trinity idea works good with html/css/js. It doesn't, but that's OK.

by oblib 9y ago

jiggunjer 9y ago

> HTML,CSS, and Javascript separate the layers of a web app fairly nicely. Except they don't. Most devs aren't even aware of what divs they are using for pure styling vs semantically correct ones. They think all the html they write is by definition semantic. Then there are the less frequent but even more insidious cases where css is used for content.

oblib 9y ago
Does that really make a difference? Seems to me that's a feature that's generally described as "more than one way to do it" and the goal is getting the app working and shipped not to appease some outside critic's sense of semantics.
- jiggunjer 9y ago
  Styling separable from content is the direction W3 wants to go. So being aware and adhering as much as possible should improve performance and long-term maintenance burden. I agree the tradeoff probably isn't worth the extra time needed to carefully structure your html and do css acrobatics. I just get triggered when someone claims the holy trinity idea works good with html/css/js. It doesn't, but that's OK.