I've stopped caring about people on ie or some super outdated browser version.
None of my projects have an audience that includes 90 years olds using ie6 on windows xp.
I assume my users are on some chrome derivative that is fairly up to date.
I'm not going to use this until it's well supported, but I'll have no qualms going so.
I certainly am not worried about anything I've used flex or grid for... they've been out for quite awhile now.
I'm not sure why we are all trained to think that anything we build has to be compatible with old browsers that essentially no one is using.
For most projects, I don't see a point unless you have some really specific requirements.
> anything we build has to be compatible with old browsers that essentially no one is using
I think similarly, with the caveat that anything that might be useful to me at work (current or future day jobs) needs to consider IE11 because there are a lot of people out there stuck using that (we work with banks a lot, while it is increasingly common for recent-ish Chrome to be available too it is not close enough to ubiquity for comfort). This includes anything that I might want to log into myself from a client's site, where I might not be able to use my own device, not just that I might expect/want them to use.
> I assume my users are on some chrome derivative that is fairly up to date
Be careful just testing in Chrom{e|ium}. We are in danger of heading into what is effectively another period of browser mono-culture, especially now MS have thrown in the towel. I'd at least support "recent Chrome/Chrome-ish and recent Firefox". While chants of "the next IE6" are a bit hyperbolic, if a mono-culture, or something close to one, forms it will create future issues no matter how good are the intentions of the controller of the "winner".
I'd like to support Safari too but unless Apple provides a way of running that locally without having to buy their hardware or buy their OS then fight to get it running in a VM that isn't going to happen outside of commercial projects where someone else is paying for the resources to allow it to happen.
I was not talking about "outdated" versions of IE (although IE9 supports HTML5 and CSS3 to some degree so it is not so outdated as one might think). Also, it is a built-in browser.
I meant Webkit-based browsers and Firefoxes that are over 3-5 years old. What about Android phones with firmware without updates? What about smart TVs?
> I'm not sure why we are all trained to think that anything we build has to be compatible with old browsers
Because compatibility was one of the ideas behind HTML. Because there are less developers than users so it is easier to solve compatibility problems at their side.
None of my projects have an audience that includes 90 years olds using ie6 on windows xp. I assume my users are on some chrome derivative that is fairly up to date.
I'm not going to use this until it's well supported, but I'll have no qualms going so.
I certainly am not worried about anything I've used flex or grid for... they've been out for quite awhile now.
I'm not sure why we are all trained to think that anything we build has to be compatible with old browsers that essentially no one is using.
For most projects, I don't see a point unless you have some really specific requirements.