Re:The CSS at w3.org is gone
by bl4ckm0r3 on Wednesday January 25, 2023 @07:12AM
(#34517319)
This no-js-no-css trend is gaining traction
[ Parent
| on HN ]
What's not to like! 0K CSS, responsive, works in desktop, mobile and tablets, and not to mention blazing fast load speed.
Responsive? I have to scroll past the left column ("Site Navigation") to read anything. That's the opposite of responsive (e.g. 2 columns on wider screens, 1 in mobile).
Re:The CSS at w3.org is gone
by deafpolygon on Wednesday January 25, 2023 @07:35AM
(#34517507)
It looks exactly as it does on mobile!
Re:The CSS at w3.org is gone
by capableweb on Wednesday January 25, 2023 @07:33AM
(#34517486)
If 2kb of CSS makes the difference between "blazing fast" and not "blazing fast", I think that's on you :)
NoJS I was aware of (and support where it makes sense, which is most of the time), but NoCSS? When did that start, and why?
I'd assume it's a joke.
Re:The CSS at w3.org is gone
by internetter on Wednesday January 25, 2023 @07:46AM
(#34517589)
But also...
I'd hardly call it a trend because It's been a thing for as long as I've used the web; but some 'classic' style programmers seem to opt out of CSS for their personal sites. One such example is Dan Luu [0], who wrote in a post [1] that styling decreased his viewership.
Additionally, it can emphasize good structure that was concealed with CSS
Anyone who uses the abominable table border design from HTML1 needs some special kind of punishment.
Re:The CSS at w3.org is gone
by dredmorbius on Wednesday January 25, 2023 @01:03PM
(#34521825)
There's ... something ... to be said for a site with minimal markup which works in text-mode browsers.
Though direct usage of those is probably a sliver of a fraction of all online usage, this also means that automated tools can work with a website. Scraping has both dark and light patterns and use-cases.
Now I can read it in Emacs
Eww :) Pun intended!
By the way, has anyone used the eaf-browser? I use the other eaf applications like PDF viewer, but for some reason, the eaf-browser seems to eat up a lot of resources.
That's because eaf-browser just uses chrome in a docker container, does screencaps -> ocr, then runs spellcheck, plus chatgpt on top for sanity checks, then copies it all back from an aws instance.