101–110 of 133 posts
Earlier quoted context omitted.
This is what us older people would like to believe. Meanwhile the young webdevs are having a blast ignoring us and building the apps of the future.
Yeah and then they all jump around React as some amazing achievement, having rediscovereed how 90's native UI do event handling.
What do CSS linters have to say about it?
On one hand I think this is really neat. On the other this is why I have never taken front end development seriously enough to spend any real time learning it [0]. From the get go it always seemed like the rules were arbitrary and involved lots of guessing to get things right. I know this isn't actually true but it felt true enough early on to poison my mind to it. [0] Not something I'm proud of and I know front end…
" I know this isn't actually true " It's true. A confluence of vague definitions, poor implementations, bad documentation ... and this is the web we have. It's the tip of the iceberg, and the painful life of anyone doing html5 work, it's 'not fun' for anyone who's been exposed to regular programming because the problems you spend your day solving mostly should not be problems to begin with.
Earlier quoted context omitted.
This is what us older people would like to believe. Meanwhile the young webdevs are having a blast ignoring us and building the apps of the future.
Yeah and then they all jump around React as some amazing achievement, having rediscovereed how 90's native UI do event handling.
Earlier quoted context omitted.
Yeah and then they all jump around React as some amazing achievement, having rediscovereed how 90's native UI do event handling.
Event handling isn't special in React. One-way data flow and UI-as-a-function-of-state are. Which 90s native UI toolkits do that?
Earlier quoted context omitted.
Yes. But are you going to to use 3 to 5 or mote C++ compilers on a given project? The worst part of these frontend issues is, ultimately, the UX can become inconsistent, if not mess. Given that nearly everyone interfaces via the visual UI, you'd think we'd have this sorted out by now.
If your project is a library, I'd expect that people are gonna use it with, like, maybe not 5 but probably 2 or 3 different compilers, and they're gonna be less diligent about upgrading their compiler versions than mainstream browser users.
That said, the browser's impact on UX is essential. A lot more people use browsers than compilers. You'd think the UX would matter by now.
Earlier quoted context omitted.
Doesn't work unless you have an extra container div.
Sure, because "vertically centered" means relative to what?
Just like works, but vertically. You don't need content for horizontal centering. I consider it a layering violation to have to do that nesting.
Earlier quoted context omitted.
Doesn't work unless you have an extra container div.
This is true, but every 'modern' DOM that I've seen has loads of extra container divs precisely to allow post hoc layout.
And here's what it looks like in Servo: https://i.imgur.com/lv3xRhi.png
I was 50/50 on whether this would be a legitimate rendering or a cheeky screencap of a panic message. :P