News for hackers. Stuff that matters.
Re:Introducing a new HTML element – welcome <clippy> by reallydude on Thursday June 13, 2019 @12:26PM (#20176382)
> Devs old enough to recall the halcyon days of IE know it was quite different...

I'm old enough. People sharing your view, are agreeing with a broad assumption that isn't based in reality. Ironically, the Chrome has had to adopt from the other direction (webasm) and hasn't created much whole-cloth that other browsers have had to adopt...and developer's certainly aren't hambstringed by these small additions that make Chrome a delight (for now). From a business perspective, the popularity monopoly is not the same as how IE was made "popular". It's VERY different from the old days in terms of quality and the state of the industry.

Re:Introducing a new HTML element – welcome <clippy> by giancarlostoro on Thursday June 13, 2019 @12:51PM (#20176606)
It's not just developers, just like Microsoft made web applications that only worked on IE (think Outlook.com and the introduction of AJAX) we've seen it here on HN all the time, they announce new products that are only known to work on Chrome initially. Some have even changed the user agent and it works on Firefox, so there's some old school Embrace Extend Extinguish nonsense going on from Google's end when they introduce new products.
Re:Introducing a new HTML element – welcome <clippy> by reallydude on Saturday June 15, 2019 @06:03AM (#20189237)
> they announce new products that are only known to work on Chrome initially.

Can you show any examples of these "features" that are forcing the hand of other browsers?

> think Outlook.com and the introduction of AJAX

https://www.sitepoint.com/xmlhttprequest-vs-the-fetch-api-wh...

I remember that every browser had an AJAX API, where IE had a specific API that was more straightforward. The AJAX capability was a forgone conclusion rather than a technical leapfrog. You could always had access to an HTML request and timers to code AJAX as a final backup.