3 ms·
> I also literally can't use safari if I don't have a Mac. You should embrace this; this is how the web should be. I don't mean you need to buy a Mac. Instead
by the_other 4y ago
> I also literally can't use safari if I don't have a Mac.
You should embrace this; this is how the web should be.
I don't mean you need to buy a Mac. Instead, I mean that the web standards effort originally came up out of supporting diversity. There was a wider range of possible clients, on a wider range of "popular" platforms. As developers we had to cater to support diverging capabilities. Progress on API development was slower, but it was more evenly spread out. Today, Chrome lurches ahead of everyone else in terms of API feature count, mostly supporting Google's business aims, and many vocal developers seem to think they should only support one set of capabilities. The slower, broader, way was better, in my opinion.
- kitsunesoba 4y agoYes, exactly. Use APIs that are broadly supported and somewhat settled and agreed upon. There is seldom an actual need to use whatever new thing that just became supported or is only implemented by Chrome… 95%+ of sites and web apps are doing the same old CRUD things that sites and web apps have been doing for decades and work fine with "boring" APIs.