3 ms·

HTML/CSS sites will outlive it all. Because they're actually the text, images, layout all in static things that can live forever without being touched and witho

HTML/CSS sites will outlive it all. Because they're actually the text, images, layout all in static things that can live forever without being touched and without any need for complicated execution of code or mantaining of obscure rapidly changing pseudo-standards. (*1) If you want to make sites and have a skillset that last, learn how to make progressively enhanced HTML websites. Anything like Web Components (where you invent useless non-defined HTML-elements-with-hyphens and then define them after executing a bunch of Javascript), Javascript frameworks (where you don't even pretend to involve HTML) will last only a handful of years. (1*: at least until HTTP/1.1 support is removed from browsers)

mdhb 3y ago
What part of web components don’t meet the definition of progressively enhanced?
- superkuh 3y ago
  You might be able to do progressive enhancement with web components but the vast majority, every web components site I've ever encountered, just end up with blank gray areas when the JS is not run to define them. That is far from progressive enhancement. It's a bit like "communism". You can say web components can be great or whatever, but everyone's every experience with it is very bad.
jakelazaroff 3y ago
Did you see what I used them for, though? How would you make a tutorial article with interactive demos without JavaScript?
- superkuh 3y ago
  I didn't see it. All I see is "JavaScript is required to run this demo." but the rest of your text is visible and that's pretty exceptional for a web components site. Usually even the text doesn't exist unless javascript is run. So thanks. To address your point: the vast majority of web sites are text and images, not executable applications. Interactive tutorials are niche. Cool, but not something I'd base my entire web design ethos around.
  - jakelazaroff 3y ago
    I mean, I feel like you can see from my website that I’m not basing my entire web design ethos around it. Other than the interactive demos that literally could not function otherwise, the whole thing works perfectly fine without JavaScript. That’s not an accident!

mdhb 3y ago

What part of web components don’t meet the definition of progressively enhanced?

superkuh 3y ago
You might be able to do progressive enhancement with web components but the vast majority, every web components site I've ever encountered, just end up with blank gray areas when the JS is not run to define them. That is far from progressive enhancement. It's a bit like "communism". You can say web components can be great or whatever, but everyone's every experience with it is very bad.

jakelazaroff 3y ago

Did you see what I used them for, though? How would you make a tutorial article with interactive demos without JavaScript?

superkuh 3y ago
I didn't see it. All I see is "JavaScript is required to run this demo." but the rest of your text is visible and that's pretty exceptional for a web components site. Usually even the text doesn't exist unless javascript is run. So thanks. To address your point: the vast majority of web sites are text and images, not executable applications. Interactive tutorials are niche. Cool, but not something I'd base my entire web design ethos around.
- jakelazaroff 3y ago
  I mean, I feel like you can see from my website that I’m not basing my entire web design ethos around it. Other than the interactive demos that literally could not function otherwise, the whole thing works perfectly fine without JavaScript. That’s not an accident!