4 ms·

Thanks for this it makes it a bit more clear, but I'm now never going to touch web again lol. It sounds like hell to me. However, what you describe above soun

by tyfon 7y ago

Thanks for this it makes it a bit more clear, but I'm now never going to touch web again lol. It sounds like hell to me. However, what you describe above sounds like what you need to write a full blown application. Why does one need this to display simple information like a blog or news? Tasks that I used the HTML tables stuff for. Nowadays I can enter a personal blog with maybe 100 lines of actual text but it still pulls several megabytes of javascript. I just can't wrap my head around why all this is necessary when all you want is to display information that could be equally served by a text or html file.

grayed-down 7y ago
I feel your disdain! I'm an old-timer and remember complaining about using those new-fangled cascading style sheets instead of just putting everything in html tag attributes. And don't get me started about having been forced to use div's for layouts instead of tables. In fact, I still don't understand why the html table construct couldn't have been evolved to accommodate a layout role.
- wruza 7y ago
  What is funny, both grid and flex still fail at some use cases. For one, grid is unaware of “media print” and cannot paginate itself (that was a big facepalm after an hour of preparing). It is also 10k rows/cols max by definition, 1k max by a common implementation. Can’t style gaps too. Otoh, flex is non-tabular, so you cannot simulate both with just one. I also met some trouble with inner flex scrolling (“overflow-xy” hierarchy forwarding issues), but these details I forget as fast as I meet them. The entire css thing is overly situational. In a generalized model, any problem is solved by a finite set of building blocks. In css, any problem except few premodelled ones is a pile of hacks and worms that never get back into a can.

4 ms·

Thanks for this it makes it a bit more clear, but I'm now never going to touch web again lol. It sounds like hell to me. However, what you describe above soun

by tyfon 7y ago

grayed-down 7y ago
I feel your disdain! I'm an old-timer and remember complaining about using those new-fangled cascading style sheets instead of just putting everything in html tag attributes. And don't get me started about having been forced to use div's for layouts instead of tables. In fact, I still don't understand why the html table construct couldn't have been evolved to accommodate a layout role.
- wruza 7y ago
  What is funny, both grid and flex still fail at some use cases. For one, grid is unaware of “media print” and cannot paginate itself (that was a big facepalm after an hour of preparing). It is also 10k rows/cols max by definition, 1k max by a common implementation. Can’t style gaps too. Otoh, flex is non-tabular, so you cannot simulate both with just one. I also met some trouble with inner flex scrolling (“overflow-xy” hierarchy forwarding issues), but these details I forget as fast as I meet them. The entire css thing is overly situational. In a generalized model, any problem is solved by a finite set of building blocks. In css, any problem except few premodelled ones is a pile of hacks and worms that never get back into a can.