Disheartening to see Safari lagging so terribly behind; there are some standardized web APIs that are a decade old that Safari still hasn't implemented. Because of this my new shiny web app [0] doesn't support Safari at all (!!!) which disturbs the hell out of me (if anyone has a reliable workaround for setPointerCapture, I'd love to hear about it).

It's further disheartening to see them implementing hardly any of the features mentioned in this talk, which means these APIs are unavailable to all developers since their OS's are so ubiquitous.

It surely isn't a capital constraint issue; Apple is the most well-funded among browser vendors, so it begs the question as to why they are letting their browser fall behind. It will be interesting to see if they decide to start lending more resources towards the browser or continue to deliver a subpar experience; which seems quite contrary to their core competencies.

Cheers for Microsoft under Satya for taking the hard stance and determining they did not want to devote the resources to Edge and ceding in a way that will ultimately deliver a good experience for Windows users under a chromium based browser. Although I'm concerned about the openness of the web; as a developer my foremost concern is that I can deliver a good experience to my users and their decision allows me to deliver on that front.

[0] www.blendful.com