google play games is still really good, it's more or less just android inside of crosvm, usually android emulators are based on virtualbox, some are based on qemu
The charm of Unix systems used to be flexibility, buy Wayland seems to be an extinction-level event for traditional window management. Nothing fills the gap of FVWM or WindowMaker. But gosh, I can get 92 flavours of tiling compositor and windows that ripple when dragged.
I think this is "temporarily" true as we get more kits that make wayland development trivial I think it wont be so bad, right now wayland is still very immature, and will be for a long time.
for many people YES! Both wayland and x11 can work very nicely when nested. For many people wayland will be remain unusable for a very long time, and for many other they are finding that now x11 is unusable for them.
It's not a great situation, but with xwayland and running wayland compositors nested (really wish we had an "way11" too, but per app cage works for me) many people's usecase will remain to be covered
can you report your issues to the waydroid github or check on the fedora forums? the matrix and telegram chats are always open to help too if you have a bit of patience.
AOSP doesn't have that much bloat, it's far lighter then your typical linux distro, It's vendors that bloat it up, Custom roms are extremely light, This is BlissOS running on 2Gb of ram https://files.catbox.moe/4n17z3.mp4.
It's far more responsive then many linux distros would be since android and it's applications are optimized around low ram and low system resource in general
this is not really quite true, we have always been able to run androidx86/BlissOS in qemu which works about "as well" but with less integration, IE no "native like" windows
most android apps are architecure agnostic "java, kotlin etc" and even apps that are often ship "Universal binaries" which include x86, or split builds for arm and x86
some android kernels are, but AOSP itself can run perfectly happy on a vanilla kernel, just make sure your kernel was compilled with BINDER enabled, which yes, is upstream
Chromium browsers have a lot of issues, and so does firefox, but ram usage is not one of chromes weaknesses, Chromium regularly preforms better for me then firefox does under low ram scenarios, Both in terms of chrome being responsive, and in terms of chrome not crippling everything else around it.
then install it using paru -S --rebuild cosmic-applibrary-git cosmic-bg-git cosmic-comp-git cosmic-edit-git cosmic-files-git cosmic-greeter-git cosmic-icons-git cosmic-launcher-git cosmic-notifications-git cosmic-osd-git cosmic-panel-git cosmic-randr-git cosmic-screenshot-git cosmic-session-git cosmic-settings-daemon-git cosmic-settings-git cosmic-store-git cosmic-term-git cosmic-workspaces-epoch-git xdg-desktop-portal-cosmic-git
you will also need cosmic-applets-git I need to patch mine to disable LTO=fat with LTO=thin in cargo toml so it's not part of the above command. Note I haven't done a clean build on these, but they should mostly work. if you run into any issues lemme know and I can try and fix them.
cosmic-greeter can be enabled with cosmic-greeter.service I think you need to manually install greetd im not sure I have added it to deps. using cosmic-greeter isn't necessary however.
EDIT: it is somewhat likely that I may have messed something up, but as it stands i'm currently actively using cosmic comp right now
google play games is still really good, it's more or less just android inside of crosvm, usually android emulators are based on virtualbox, some are based on qemu