Comment by Dylan16807
2 hours ago
> Not really.
Are you saying that the percent it'll be in six months isn't relevant to you, or something? You'll probably be working on most of the same projects, even. If you do care about the future then yes caniuse is missing that point.
> Anything below ~90ish% is no go, unless i have a fallback strategy of some sort.
Once a few more versions of chrome roll through it'll jump up to almost 80%, and you can have a fallback easily.
> Are you saying that the percent it'll be in six months isn't relevant to you, or something?
It absolutely is relevant.. but only in about 6 months :)
Suppose the obvious case, i have some resizing pipeline for images. Would i include support today in my resizing pipeline today and pay a few extra cycles and storage for someone that my clients can't read?
It would be cool to have a subscribed alert for when the tech crosses a certain % threshold adoption so i can look at it again, otherwise it just relies on my brain's flawed long term cron job
> Suppose the obvious case, i have some resizing pipeline for images. Would i include support today in my resizing pipeline today and pay a few extra cycles and storage for someone that my clients can't read?
Yes, this is literally what the <picture> element is for.
Your hypothetical pipeline would be able to convert <img> elements into <picture> elements with multiple <source> elements for different user resolutions and format supports.