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/)MA
Posts
11
Comments
427
Joined
2 yr. ago

  • I’ve tested them all and they all launch fairly immediately.

    I discuss some of the other feature differences here:

    https://mark.stosberg.com/rofi-alternatives-for-wayland/

    I think for most people, Fuzzel will be the best choice, but compeitors offer unique features like Rofi-compatibility, HTML formatting support or the most important one: being written in Rust.

  • The support for running apps in the Linux container feels fairly normal. I had a family member using LibreOffice and other apps that way for years and it worked fine. We bought a more powerful Chromebook and performance was fine. One family member is using ChromeOS on the Framework laptop. Performance there is great.

    FydeOS is a de-Googled ChromeOS based in China.

    https://www.aboutchromebooks.com/news/fydeos-vs-chromeos-flex-which-is-right-for-you/

    Unattended upgrades is for updates in the Linux container. Sometimes it’s used primarily for security updates. The whole thing is so locked down and containerized, I don’t think security updates in the container are as important.

    It’s true that Chrome always installed, but you can put whatever icons in your launcher.

    I’m not sure about changing the default browser.

  • Regarding ChromeOS being corporate, it is nearly all open source. You have to login with a Google Account, but once in, you don’t have to use any Google products.

    You can use Firefox, Fastmail, whatever you like.

  • I tried older relatives on Ubuntu and ChomeOS and for the less technical ones, ChromeOS was best.

    For ones with confidence and a growth mindset to learn new things, Ubuntu was fine.

    If in doubt, I would recommend ChromeOS.

  • No matter where you install from, you have to trust the source. Indeed, you have to trust every step in the supply chain.

    If you are getting your code straight from the author, you are eliminating an exploit that’s introduced by a compromised account of a packager.

    Carry on.