• 0 Posts
  • 39 Comments
Joined 1 year ago
cake
Cake day: July 20th, 2023

help-circle










  • Quack Doc@lemmy.worldtoLemmy Shitpost@lemmy.worldFF Evangelists
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    8 months ago

    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.





  • First impressions is I’m shocked by just how fast it is, Aside from the first boot which for some reason doesn’t propagate apps and needs a reboot, it’s extremely fast, Gnome software and Discover aren’t even within the same league of responsiveness and speed. I didn’t showcase Discover since I don’t know where the cache files are to delete them.

    Touchscreen for sure I wish was handled better. you can see I accidentally clicked an app in the last video instead of scrolling, but thats something that I assume will be fixed with time.



  • Quack Doc@lemmy.worldtoLinux@lemmy.mlOn "Wasting disk space"
    link
    fedilink
    arrow-up
    9
    arrow-down
    1
    ·
    11 months ago

    The issue with flat packs is the more you use it, the higher the chance that you get less shared runtimes and the higher the chance of the duplication. And at some points it really does get to awfully ridiculous levels.

    A while back, I had run everything I possibly could with Flatpak to the point I’d even make my own Flatpak to try and see how well it would work. Instead of using the AUR. And it worked great for the first little while. I’d installed all of my apps and it was fine, but as I kept using the system, kept installing new apps and not uninstalled the old ones, it really started to build up awfully quick, especially with older apps.

    I feel like the usefulness of flatpaks is the inverse parabola, where it’s extremely useful in the center use, but when you go to either side of it, it becomes less and less useful.

    Apologies for any incoherentcy this was written with a speech 2 text.



  • crostini is pretty damn great but it’s important to know what it IS and it’s actually really simple. Crostini is two things combined into one

    Firstly A VMM

    Crostini uses the crosvm VMM which is can be thought of kinda like an inhouse version of qemu but designed to explicitly run natively integrated and high performance VMs safely instead of being a swiss army knife (KVM acceleration, virtio peripherals etc) (PS. it’s written in rust too) They use it for chromeOS to integrate android support (on select newer devices) and linux. It runs a supervisor distro which can run containers inside of it.

    ChromeOS calls the VM termina. Im not sure what distro is running in the VM, or if its a specialized one. I forget

    Next is the containerization

    It is a lot like distrobox, It can run a myriad of distros but the key part of it is sommelier. A wayland compositor designed to render windows through virtio-wayland, an extension of virtio-gpu. In practice very similar waypipe which rendering wayland windows to a remote wayland client using network/sockets (Yes, it does support AV_VSOCK so it can work with qemu.)

    Sommelier is run in the containerized Distro, running on the TerminaVM. Using termina provides excelent security and performance, and then using LXD inside of termina provides excellent flexibility

    The guts of “crostini” crosvm, virtio-wayland, sommelieris all open source, you can actually (with some degree of hassle) set this up entirely yourself, or do what I do, and run qemu + waypipe for a similar experience. Waypipe is much easier to setup however it comes at a preformance detriment since qemu virtio-gpu perf is worse then crosvm (no vulkan support in qemu yet still)

    EDIT: s/Architecturally/in practice/ I have no idea why I said Architecturally. they are quite different things. I must have had a brain fart