I ended up falling into mostly frontend work because nobody else seemed interested, and the work needed to be done. I think CSS is why. Backend work seems more "pure".
Trying to make things work cross-browser isn't as bad in the old days, but it's still a hazard to watch out for. Safari is usually the biggest problem IME, despite all the jokes about supporting IE.
I'm afraid that, even if this allows you to seamlessly roll out a new type of layout rule, all this will create, ultimately, is more fragmentation in the ecosystem.
The thinking and strategy appears to be along the lines of "Just throw more JavaScript at it", which, time and again, tends to go all kinds of wrong.
CSS, like JS, is already bloated and messy, struggling to be all things to all people. Now CSS won't even be declarative in nature anymore - it'll depend on JS, and the two will fuse into a giant, hairy ball of mud.
With Web Components fusing HTML with JS, what used to be declarative, semantic markup is now unreadable gibberish - this will do the same for CSS.
The web used to be a homogenous, human-readable medium. Now every webpage will use it's own version of HTML and CSS, and no two sites will look the same.
I used to be optimistic about the web - but now, there are definitely times when I think HTML, CSS and JS are all f_cked beyond repair, and maybe we just need to start over with something much simpler that actually does what we need.
I ended up falling into mostly frontend work because nobody else seemed interested, and the work needed to be done. I think CSS is why. Backend work seems more "pure".
Trying to make things work cross-browser isn't as bad in the old days, but it's still a hazard to watch out for. Safari is usually the biggest problem IME, despite all the jokes about supporting IE.
Safari is the new Internet Explorer 😉 I am not even joking that much.
I think we will see a huge change on browser support in the future. There is a new thing called CSS Houdini, which will try remove these issues.
Houdini is actually one of my greatest CSS fears.
I'm afraid that, even if this allows you to seamlessly roll out a new type of layout rule, all this will create, ultimately, is more fragmentation in the ecosystem.
The thinking and strategy appears to be along the lines of "Just throw more JavaScript at it", which, time and again, tends to go all kinds of wrong.
CSS, like JS, is already bloated and messy, struggling to be all things to all people. Now CSS won't even be declarative in nature anymore - it'll depend on JS, and the two will fuse into a giant, hairy ball of mud.
With Web Components fusing HTML with JS, what used to be declarative, semantic markup is now unreadable gibberish - this will do the same for CSS.
The web used to be a homogenous, human-readable medium. Now every webpage will use it's own version of HTML and CSS, and no two sites will look the same.
I used to be optimistic about the web - but now, there are definitely times when I think HTML, CSS and JS are all f_cked beyond repair, and maybe we just need to start over with something much simpler that actually does what we need.
You are correct 100%. All used to be simple and uniform and clean. Now all is a big mess and super fragmented.