3 ms·
Your analogy is imperfect; for MSHTML and EdgeHTML are first-party, while Electron is third-party; and it’s not just MSHTML that Microsoft are pushing people aw
by chrismorgan 9y ago
Your analogy is imperfect; for MSHTML and EdgeHTML are first-party, while Electron is third-party; and it’s not just MSHTML that Microsoft are pushing people away from, but the entire Win32 API—Microsoft’s been saying, use WinRT instead, and you can have EdgeHTML there. Notably, Microsoft has been steadily stepping back from this vision in the last few years, and EdgeHTML is expected to be exposed to Win32 apps at some point (the impression I have is that it is expected sooner rather than later).
It’s a nuisance that it isn’t already there, but it is coming.
Note also that Chromium isn’t embeddable on its own; it’s only because it’s open source that anything has been able to embed it at all. It has no stable API, so CEF has to wrap it and shed some functionality to ensure it’ll keep working across more than just a few releases of Chromium, as changes are made therein. The Electron project basically builds itself inside Chromium instead, see https://electronjs.org/blog/electron-internals-building-chromium-as-a-library https://electronjs.org/blog/electron-internals-building-chro....
But really, IE has enough things needing it that removing it outright isn’t an option yet, and won’t be for quite a few years. I can imagine in a few years’ time not installing IE by default, and making the MSHTML widget actually be EdgeHTML instead if IE’s not installed, but even that I expect would break quite a bit of software. And Microsoft cares a lot about not breaking compatibility. It’ll be interesting to see what they do about it.
(You may well know these points already, kodablah; I’m providing them as much for background for others reading as for you.)
- kodablah 9y agoSure the analogy is imperfect. I also don't have a perfect analogy for a browser vendor hobbling its newer product. But I'm just appealing to common sense wrt not addressing an extremely common use of something yet wanting that something to stop being used. I personally don't think they should implement the MSHTML/COM APIs with Edge any more than I think they should implement ActiveX on Edge. The old tech can die its slow death, so long as there is a viable replacement. Selfishly, I want this for https://github.com/zserge/webview https://github.com/zserge/webview to watch Electron adoption decrease or even an API-compat version using shared libs already on the system.
- cptskippy 9y agoIt's less about hobbling Edge and more about compelling you to not use Win32 while keeping you stuck in Windows. Win32 needs to die and Microsoft is doing everything it can to kill it while not completely pissing off those that rely upon it. Part of the problem is that if they force everyone to rewrite Win32 native apps then what's stopping them from just going to MacOS or something else? They want everyone off Win32 but still locked into Windows.
- userbinator 9y agoI'm pretty sure it's not going away, especially because the newer more bloated stuff they're trying to push is built on top of it, and that's not going to change unless MS decides to start officially documenting the native NTAPI. They day they get rid of Win32 is the day I switch completely to Linux+WINE or even ReactOS.
- cptskippy 9y agoSuch as? Products like Office have undergone significant refactoring to remove reliance on Win32. They have something like over 90% code reuse between Office apps on MacOS, OSX, Android, Win32, and Xaml. With every release of Windows 10, more and more GDI and Win32 is replaced. Part of the MinWin project was to extricate Win32 from the kernel and have a true separation.
- userbinator 9y agoFor example, .NET framework calls into Win32 CreateFile when opening a file: https://referencesource.microsoft.com/#mscorlib/microsoft/win32/win32native.cs,a049b9ef1a4c580d https://referencesource.microsoft.com/#mscorlib/microsoft/wi... Products like Office have undergone significant refactoring to remove reliance on Win32. Then what are they using instead? Whatever it is, how does it provide the basic functions? Does it call into native NT API directly? Part of the MinWin project was to extricate Win32 from the kernel and have a true separation. What? Win32 is not part of the kernel, it's a layer on top of the native NT API (or VMM32, if you remember Win9x...) https://en.wikipedia.org/wiki/Architecture_of_Windows_NT https://en.wikipedia.org/wiki/Architecture_of_Windows_NT https://en.wikibooks.org/wiki/X86_Disassembly/Microsoft_Windows https://en.wikibooks.org/wiki/X86_Disassembly/Microsoft_Wind...
- ngold 9y agoSo are you pro or anti open source? It seems both have their challenges. But only one can be addressed by outsiders.
- pjc50 9y agoThis isn't all that relevant on Windows.
- microcolonel 9y agoWell, that's true if the problems aren't with the platform's browser, though in this case you would probably just ship a CEF or WebKit2-based runtime to replace MSHTML/EdgeHTML.