> 80% of what made us useful was the way we knew all the quirks and intracries of the browsers. Guess what? Those are all gone.
If you don't experience browser-dependent bugs or quirky undefined behaviour, then you're only doing trivial stuff.
If you're just building a blog you won't bump into them of course, but in a way with all the new API's that constantly are being added, it's getting more difficult to work your way around the minefield of problems. It doesn't help that browsers are extremely lagging in fixing well-reported, well-reproducable bugs.
A handful of examples off the top of my head: there's the bug where Chrome taxes the GPU 100% whenever a CSS animation happens (draining battery for a rotating font-awesome icon), there's the unpredictable nondeterministic behaviour of Safari's Flash blocker, there's the bug where GPU layers get different AA applied and whose width is calculated differently causing the layout to jump and the fonts to thinnen whenever an animation happens, there's the bug where Chrome's background images disappear, there's the bug where an inset box-shadow disappears when you're using mask at the same time, there's the difference between Firefox' flexbox behaviour and all the other browsers, there's the only partial LocalStorage API support in certain browsers, etc...
Those are a few of the handful I bumped into the last 6 months and I'm not even a webdesigner.
I worked as a front end dev for a very large company/codebase. Sounds to me like you are writing pretty shoddy CSS and using things you aren't supposed to be using yet. For example Flexbox.
If you don't experience browser-dependent bugs or quirky undefined behaviour, then you're only doing trivial stuff.
If you're just building a blog you won't bump into them of course, but in a way with all the new API's that constantly are being added, it's getting more difficult to work your way around the minefield of problems. It doesn't help that browsers are extremely lagging in fixing well-reported, well-reproducable bugs.
A handful of examples off the top of my head: there's the bug where Chrome taxes the GPU 100% whenever a CSS animation happens (draining battery for a rotating font-awesome icon), there's the unpredictable nondeterministic behaviour of Safari's Flash blocker, there's the bug where GPU layers get different AA applied and whose width is calculated differently causing the layout to jump and the fonts to thinnen whenever an animation happens, there's the bug where Chrome's background images disappear, there's the bug where an inset box-shadow disappears when you're using mask at the same time, there's the difference between Firefox' flexbox behaviour and all the other browsers, there's the only partial LocalStorage API support in certain browsers, etc...
Those are a few of the handful I bumped into the last 6 months and I'm not even a webdesigner.