Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)DR
Posts
0
Comments
465
Joined
2 yr. ago

  • I'm not defending x11, both wayland and x11 are trash, it's just whichever trash pile you find yourself most comfortable in.

    On x11, fractional scaling is more or less just handled by the gui toolkit. It does suck that you need to set an env var for it, but IMO that isn't too bad.

    the multi monitor stuff does suck for sure. It's not an issue for me personally. One thing that is a massive issue for me is x11's terrible handling of touch, I use touch screens daily so that's a massive issue for me, wayland compositors are also typically quite a bit faster then x11 + wms on low end systems now too (not to be confused with total resource usage/lightness).

    Wayland has a lot of things going for it, but it also has a lot going against it. Both are terrible. Arcan save us (oh how a man can dream)

  • for one, it's missing a good chunk of A11y stuff, activity watch requires something to monitor the active window, there is a PR for that, still not merged, this has been an issue for years

    It's missing protocols that will let applications request to be a privileged application, which is necessary for applications to use other functionality.

    Missing protocols to control always-on-top / layers, which is needed for OSKs to function, and a couple other A11y things off the top of my head.

    It's not just a11y either, Window positioning still isn't merged, which means if your app opens two "windows", you cannot currently select where to open them, or to even bind two windows together (Android emulator does this for instance).

    There is a LOT wayland is missing, it IS getting better, just at a snails pace.

  • Among the other things that have been said, Android auto often makes use of some tricks too. Things like hibernation that phones typically do not do (Probably the biggest one right here), Animations to hide loading time, loading some critical, but not latency sensitive services until after the boot. and some other misc service management stuff.

  • in general, an application can allow you to log in to do things like like and comment, but most applications choose to instead. Comments might be a bit more tricky, but applications like smart tube next support liking and disliking.

    It could also be possible to do what grayjay does, and simply open a webview for the video in question

  • AOSP has no default PDF viewer, many GAAPS (official roms, custom roms with full gapps etc.) roms do have a pdf viewer by default.

    There are many available PDF viewers around making a good pdf viewer is actually pretty hard, I reccomend just trying a bunch on fdroid and seeing what sticks out to you.

  • what are your system specs? at a low effort you should be getting a lot more FPS, what cli command are you using? but I guess it would be best for you to export to /tmp given enough ram and then go from there

    EDIT: for context, when encoding libjxl I would do -distance 0 -effort 2 for lossless output