There are console browsers that support CSS.
Web Design Philosophy: Pure HTML versus CSS
I wrote: precompiled
I clearly understood but I still think it's overcomplicating the problem
fuck off
It's good you autist. Otherwise people would start designing there website that way because it's "the latest hype"
now that's sad
Couldn't have said it better.
Also: as soon as you say "but has acquired the semantics of emphasis anyway," you literally agree that creation of " was a good idea.
No, you didn't and don't understand. You compared precompiled LESS (server-side) with jQuery (client-side).
I don't really follow that subdiscussion, but now I'm looking it up, I see that that Less thing can be interpreted client-side too, and likewise I think there is nothing inherently impossible about a script that would translate jQuery-written scripts to vanilla JavaScript for reuse elsewhere.
You wouldn't deploy to production with the interpreter, but it's definitely useful while debugging. Propping up a poor use case as reason for denigrating the technology itself is a strawman fallacy.
Why on Earth would you do this? It doesn't eliminate client-side JavaScripting like precompiled LESS does?
>literally agree that creation of " was a good idea
No I don't it's redundant and reduces compatibility.
Precompiled always means server side and I just wanted to say it's horrible by comparing it to JQuery.
Abstracting the abstracts things imaginable is fucking autism. I'm not sure you'll actually save computation on user created content when you have to recompile the css after each post.
Seems like a backpedal, unless you literally just use jQuery as an arbitrary point of reference for anything that's shitty. As far as LESS use cases, you wouldn't want to use it on every project. Here's a website that uses LESS:
www.uverse.com (I was on the dev team there)
The little tiles representing video content have to appear consistent on many different pages, in many different containers, all of which have their own styling rules. Using LESS let's you do this pretty easily. With pure CSS, it would be a nightmare, with a shitload of duplicate code (and weird rules/workarounds which would stress the browser and cause performance issues).
I don't dislike Less. Calling it "thing" didn't mean disrespect, but my unfamiliarity with it. I was just pointing out it's similar to jQuery.
Yes, but it could still remove framework overhead. Don't read too much into that post; I was just stating those tools' likeness.
According to your "reasoning," literally any innovation, for instance, introduced to increase usability and reduce ambiguity as in case of b -> em, "reduces compatibility" because of lack of adoption of the updated version at first. Better start campaigning for termination of all software development on that basis.
Fair enough, sorry if things are a little heated lol