I am into FOSS stuff. I am also into programming.

  • 6 Posts
  • 38 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle
  • The program itself isn’t really bigger, what makes the difference is that it won’t use the dependencies installed by your native package manager, it will download them, it also will download various runtimes if needed for the program, these runtimes are not really supposed to be ran if you compile the package yourself for your distribution, but if you use Flatpak, it is going to run all these runtimes for the program to work, these runtimes will use more RAM than the native build, if the runtime is not optimised, then it will also contribute to higher use of CPU and everything else in general.

    It will differ from program to program, but I’ll let you know that I have natively compiled EasyEffects (real-time audio manipulation) and also have tried the Flatpak build. The native version hardly uses more than 5% CPU, and is also lightweight in terms of RAM. But the Flatpak build took significantly more RAM usage and my CPU went 80% whenever I played music with the same preset that I tested on the native build. Flatpak also had to download 700-900 MB worth of internet (no idea how much space it took after installation) for the program to run.





  • I was ignoring the 92% percent part of it in my original comment when I said “not even open-source” because I think pretty much all privacy advocates know that it is built on top of Chromium.

    I am not sure what your true source is, but mine is this from where I am quoting:

    We don’t publish it under an open-source license and only release obfuscated versions of it. The obfuscation is partly there to improve performance, but it also very much is the first line of defense, to prevent other parties from taking the code and building an equivalent browser (essentially a fork) too easily.

    While they release the source code of the UI elements, it seems that they only release a obfuscated version of the UI source code, which I am afraid won’t go well If I want to easily “audit and go through”. Though it’s possible they have now changed their minds and my news sources are outdated.









  • myxi@feddit.nltoTechnology@lemmy.worldIs Flatpaks the future for Linux?
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    3
    ·
    edit-2
    1 year ago

    Flatpak just sucks for us with potato level hardware. It is much slower and crashes. Some things just didn’t work until I got mine built from source using AUR scripts. I had checked the memory usage, the flatpak version of EasyEffects took much more memory than the native one. I don’t want Linux to become Windows with this Flatpak nonsense that wastes my desktop’s resources more than it should. Whenever I played music with EasyEffects flatpak, my CPU usage went up literally 80%, but with the native build, EE now does not go beyond like 5% CPU.

    Any package that will force me to use Flatpak, I simply won’t use it at all, or find some workaround. I will not donate a single penny to the project itself, but I will to the one who found the workaround.












  • myxi@feddit.nlOPtoUnixporn@lemmy.mlKDE Plasma
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    I wonder what is its main selling point as a distro now though

    I wanted to experience Arch and wanted something simple and quick (I was busy those days, so DIY Arch wasn’t a choice). I tried EndeavourOS, but it wasn’t simple: they made many configurations to the system, which ruined the vanilla experience of all the WMs and DEs. I started looking for alternatives, and I found Crystal to be attractive and well-maintained, so I went for it. I think its selling point is being as simple, friendly, and vanilla as possible.