3 ms·
Because over a decade ago the Apple devs poo-poo’d all over the premise of this API when it was first proposed. I’m referring to its earlier incantation that we
by darinf 5y ago
Because over a decade ago the Apple devs poo-poo’d all over the premise of this API when it was first proposed. I’m referring to its earlier incantation that we added to WebKit and shipped in Chrome but could never get Apple devs to support. I’m delighted to see it supported now. I just think of all the lost time for the web and what could have been.
- JimDabell 5y agoWho is the “we” you are referring to? > I just think of all the lost time for the web and what could have been. This doesn’t seem like it enables anything new though? It’s a convenience.
- jefftk 5y ago> Who is the “we” you are referring to? Darin used to be something like my boss's boss's boss's boss when I worked in Chrome.
- dmitriid 5y ago> Because over a decade ago the Apple devs poo-poo’d all over the premise of this API when it was first proposed. What I read is: Apple devs came back with a list of problems and issues as long as Jupiter's equator, Chrome said "we don't care" and shipped it? > I just think of all the lost time for the web and what could have been. With Chrome not rushing it's own broken insecure implementations of internal APIs, not pretending they are standards and not gaslighting other browser vendors? Oh, the Web would be a much, much better place.