In any event, thank you Mozilla for supporting this platform. I hope Microsoft puts some more serious weight behind it.
Unfortunately, Microsoft will not likely reenter this arena or support phones with Windows in any official capacity, the current direction from Satya appears to be to retreat from every competitive market and cede all standards to El Goog. Microsoft promotes Android, is building a browser based on Chromium, and is abandoning Cortana. Best hope for this would be a third party building an ultraportable themselves and writing their own phone support.
It seems like they're focusing on the enterprise element of their business, which is what's making more money, has fewer players to work with, etc.
I'd imagine they see their future closer to HP than Apple.
And bear in mind, HP is a hardware company, they aren't worried about what platform is running on their hardware. Microsoft is a software company, which is a very different ball game.
It is all about AWS or Azure.
https://twitter.com/NTAuthority/status/1115339802503786496
Of course this is a hack, not a usable product, but I wouldn't be surprised if docking would be possible eventually, maybe someone even could hack the Windows 10 Mobile UI to run when undocked… (or design a new mobile UI)
It'd be a great use case to have such a thing for NT-on-ARM, but I don't see this as much more than quick hacks to waste some time, especially with the 855 and 8cx SoCs diverging again so that the brief peak of binary driver sharing being possible is pretty much gone again...
At this point I just want X11 back. At least that worked.
Qualcomm and Mediatek are the ones with shitty out of tree Board Support Packages, preventing Android updates and blocking accelerated X11/Wayland from running.
In comparison if I use (classic) edge to browse and read on my tablet, it's totally fine. Firefox is relatively okay as well (similar issues though, because it just doesn't get much testing).
Having two monitors of different DPIs makes it especially obvious how bad most apps are at DPI. The good ones stand out to a dramatic extent. DPI is a difficult thing to implement, but Win9x has had tooling and support for it since Windows 10 and they improve it with every release. When I implement support in my apps it really doesn't take that much effort, just forethought.
For one example: Chrome's scrollbars and other widgets are utterly atrocious on touch (even on Android it's kind of bad). The standard Win32 scrollbars and other widgets can have all their sizes manually adjusted in the registry, and by default many of them will automatically adjust when you're in touch mode. I was easily able to make scrollbars bigger across literally everything except Chrome.
I don't think so. Microsoft should make easier to develop for tablet mode if they want adoption, the DPI issues happen also in Microsoft applications! The Win32 APIs are a legacy mess and Microsoft has a long tradition in delivering lot of frameworks which ends in failure (WPF, Silverlight, etc).
BTW, Google Docs copy & paste in tablet mode doesn't work in Firefox either.