31–40 of 49 posts
> What doesn’t work: > Persistence after page reload That's not an app. TL;DR: Use styled checkboxes in a form.
Yes, you can create certain interactions with CSS alone but doing so purely for the sake of not using JS is pointless and at worst harmful.
I was doing something similar the other day with toying around trying to come up with an HTML/CSS only game. I ended up with this: https://codepen.io/billnreed/full/boXrVr
Is this a joke?
In doing this, you break HTML semantic relationships. Each to-do is a child of the previous to-do. That hurts. I applaud the work in making something sans JS for the kicks of it, but if your going to do it, at least don't break HTML.
The semantic Web is, unfortunately, quite dead. Hopefully a JavaScript-free Web can still happen.
The phone you're reading this post on has nearly as many CPU cycles available to run code as the web server that generated the html. Why on earth would you not want to distribute the overall application load.
Earlier quoted context omitted.
The semantic Web is, unfortunately, quite dead. Hopefully a JavaScript-free Web can still happen.
"Hopefully a JavaScript-free Web can still happen." The phone you're reading this post on has nearly as many CPU cycles available to run code as the web server that generated the html. Why on earth would you not want to distribute the overall application load.
Maybe because I want my phone battery to last a long time, but I don't care how much electricity the web server uses. Maybe also because the JavaScript is probably proprietary software [0], which I don't want to run on my computer.
These exercises will be a lot more fruitful to read through if the author can acknowledge the contrived nature of these attempts and provide a real-world advantageous use case of the techniques outlined
> What doesn’t work: > Persistence after page reload That's not an app. TL;DR: Use styled checkboxes in a form.
Earlier quoted context omitted.
"Hopefully a JavaScript-free Web can still happen." The phone you're reading this post on has nearly as many CPU cycles available to run code as the web server that generated the html. Why on earth would you not want to distribute the overall application load.
> Why on earth would you not want to distribute the overall application load. Maybe because I want my phone battery to last a long time, but I don't care how much electricity the web server uses. Maybe also because the JavaScript is probably proprietary software [0], which I don't want to run on my computer. [0] https://www.gnu.org/philosophy/javascript-trap.html
Uglified/minified HTML+CSS is almost as difficult to parse by humans as JS.
I'm all for free software and very supportive of the arguments, but the pro-HTML, anti-JS rhetoric never made a lot of sense to me, consistency-wise, at least in these days of CSS3.