Wow, this is progressing much faster than I expected. I bought a Pixel on discount a few months ago with the intention to set up my dev environment (Docker, Java, Node, IDEs, etc) when hardware acceleration and Docker were working. Time for me to get cracking!
Hopefully this will allow applications like VS Code (Electron) to use straight Wayland rather than the slower XWayland as they do now. Of course, it's pretty amusing to have an embedded Chromium app running in a container inside a Chromium OS.
I just set it all up, got VS Code and IntelliJ running, and of the two, VS Code looks the best. It's the only app I've seen that integrates the menu bar items into the ChromeOS menu bar, which saves a lot of space and looks way better.
It's really an XWayland application, i.e. it uses X, whose protocol is forwarded to Wayland. That's why in this article you need to pass -X to Sommelier:
That post also highlights how, because it's not a Wayland native app, VSCode will still look crummy when e.g. you use it on monitors with varying DPI. Real Wayland apps have multiple, per-screen DPI settings:
"Multi DPI intends to allow clients to seamlessly move around on a display with multiple monitors connected, where each monitor may have very different DPIs, thus different scales, without any sudden size changes or glitches, while at the same time allowing clients to switch between different scaling factors."
