Microsoft decides IE 10 has had its fun: Termination set for Jan 2020
IE as a browser does suck, no argument there. However, I (and I'm sure many other Windows devs too) find the .NET WebBrowser control very useful - it's a easy drop-in control that's part of the .NET framework. It shares a lot with with IE codebase, so if IE gets killed off, would that include the control? It certainly would no longer be updated.I've looked in depth at the embedded Chromium project, but there's simply TOO much baggage with that making it total overkill when all you want to do is render some HTML in a line-of-business application.