Mayayana wrote:

Finally, Microsoft is officially saying IE shouldn't
be used:

https://techcommunity.microsoft.com/...er/ba-p/331732

As with most Microsoft writing, it's poorly written, in a
conversational but quasi-technical style with clunky,
made-up terms thrown in.

It wasn't obvious to you that this was a *blog*? It is not a
journalistic report nor an official announcement. You think your posts
here would stand up to your same scrutiny?

For example, "technical debt" means existing reasons you
need to use IE. "Endpoints" means websites. I wish MS
would provide basic English classes for their employees.

As for "endpoints", IE is obviously a web browser that requires
networking and the hosts in a connection are often called endpoints
since, ahem, the hosts are the endpoints of the connection. Just saying
hosts for a connection can be confusing even more because those could
include the hosts in the routing of the connection (called hops).

I'm not familiar with the "technical debt" term; however, I don't
participate in that community and lingo is often related to the
community wherein it is used. I was sitting at a table with a bunch of
friends that were microbiologists or neurosurgeons, yep, they'd sound
like foreigners with all the terms they would bandy that is germaine to
their expertise. I've been told that when my friends and I are talking
around others not so into computers that we sound like foreigners.

https://en.wikipedia.org/wiki/Technical_debt

Looks like Chris (Principal Program Manager in the Experiences and
Devices Group) is using terms common within programmer circles.

Even you use terminology that is peculiar to the audience you address.

The author is not pointing to the security
problems at all. He only points out that MS broke IE11
in terms of backward compatibility, paints that as a
good thing, and doesn't want you to blame MS for IE11
not working as expected. Of course, if IE11 was standards
compliant and still supported quirks mode by default, it
would be universally compatible. Instead, IE11 does neither.

Interestingly, the author never even mentions Edge.

BTW, Edge is moving to the Chromium engine.

https://www.techradar.com/news/micro...ng-to-chromium