I started writing CSS at around the them when you were still asked to write Hacks for IE5/5.5/6 -- and it was truly horrific -- but it made a lot of sense when

I started writing CSS at around the them when you were still asked to write Hacks for IE5/5.5/6 -- and it was truly horrific -- but it made a lot of sense when you looked at the market shares. Yes, please be good and build accessible websites, just because its actually not hard to do on a rudimentary level and your probably sucks if you don't anyway. But actually working on CSS compatibility is such a waste of time considering how "good enough" all of the widely available options are. Yeah, you probably do not want to use the latest in web tech if you are doing a reasonably sized web project that loses actual money for every % of users that can not use the app/site. So what? Just don't. Unless it's a vanity project pick a reasonable cut off point, go with it for that project (or that iteration of the product) and then you reevaluate for the next one. You can obviously use auto prefixer and the sorts to widen the margin -- everything you can automate, you don't have to think about, by all means, go for it. But the mental overhead you are creating by doing shit like "height: 500px; height: 100vw;" is insanity in a reasonably large project with multiple developers. I forbid you to do it. By the time the next project comes, you can probably already set the cut off somewhere else. People are actually (being forced to) update their computer, and really enjoy throwing out their mobile devices every other year (thanks apple, I guess). I gladly reap those benefits.