Riho insinuated that since some things are more complex than others, bad performance is inevitable, or even if you optimize something slow frameworks are the default, or something. Argument by vague trend, noncentral. J asked straightforward questions that weren't really answered
-
Once you remove JS from the browser, now the Web is no longer based on an error-prone slow programming language, so it's a lot more natural for people to choose higher-quality languages (as opposed to hacks on top of JS like TypeScript).
just chewed his lip on “I don’t get why that’s hard” which translated “I don’t get it”
Then once you have real programming languages, why do you have all this DOM stuff and wtf is CSS for anyway, just let peoples' code lay out the text, and get rid of all that junk.
-
-
There will of course be common libraries for doing this, so that people don't have to write it themselves. But the difference is, when it's just user-level code doing the layout, you have the power to change it. When it is built into the browser, you do not, and instead
-
have to engage in endless hacks that almost but don't quite solve the problem, like everyone does today.
- Show replies
New conversation -
-
-
“Wtf is CSS for” just about sums this up
-
If you don’t understand how awful and embarrassing CSS is, it’s going to be very difficult for me to figure out anything else to say. I can just refer you to:
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.