3 ms·
> Like why wasn't SurfaceFlinger got adapted for both IIRC SurfaceFlinger is tightly tied to Binder which is an Android only kernel IPC, didn't work with the s
by ChocolateGod 1y ago
> Like why wasn't SurfaceFlinger got adapted for both
IIRC SurfaceFlinger is tightly tied to Binder which is an Android only kernel IPC, didn't work with the standard Mesa stack and wasn't designed for multiple windows with multiple displays.
Wouldn't be surprised though if eventually Android swaps to Wayland as Google wants to merge it with ChromeOS. Since talking to the compositor is abstracted away to the platform APIs, I don't see it as big of a hurdle as X11 to Wayland was.
- gf000 1y agoFair enough. Though I would be happy if merging of work would happen in either direction.
- ahartmetz 1y agoIt doesn't seem like Android devices have much to offer to fill desktop computing functionality gaps in Wayland.
- ChocolateGod 1y agoAdopting SurfaceFlinger on the desktop would certainly be a step backwards, OEMs effectively fork it each time and change it for functionality on their devices. Google sometimes tries to add these features (e.g. split screen, multiple windows etc) into the base code but can take time for OEMs to adopt them on their skins.
- m-p-3 1y agoI'm curious to see what Google did for their Desktop Mode / DeX-like implementation in Android 16.