3 ms·

Mobile was really based on an entirely different Windows system architecture than the "legacy" desktop people all know and love. In addition to that, making han

Mobile was really based on an entirely different Windows system architecture than the "legacy" desktop people all know and love. In addition to that, making handset UX from scratch has shown to cause a lot of fun bad experiences as seen with the (much more mainstream-appealing) open Linux handset attempts. 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...

swiley 8y ago
> In addition to that, making handset UX from scratch has shown to cause a lot of fun bad experiences as seen with the (much more mainstream-appealing) open Linux handset attempts. At this point I just want X11 back. At least that worked.
- metildaa 8y ago
  X11 and Wayland works just fine on Allwinner A series & H series chips as the community has added nearly complete blobless support for everything from the HDMI phy to the Gigabit ethernet controller to the oddball WiFi chips some boards use. Qualcomm and Mediatek are the ones with shitty out of tree Board Support Packages, preventing Android updates and blocking accelerated X11/Wayland from running.
floatboth 8y ago
Wasn't 10 Mobile rewritten to have much more in common with desktop than before?