#Poedit chromebook install#

It ran just fine, because all of the libraries it uses are backwards compatible.įlatpak wants to download 3D drivers, patented video codecs, themes, locales, Qt 5, KDE 5, GTK 3, ICU, LLVM, ffmpeg, Python, and everything else in, all to run a calculator.

#Poedit chromebook install#

I just ran the kcalc binary straight out of its Flatpak install path unsandboxed and let it use my native libraries. The rest is all redundant libraries that are already on my system. Note that the app package itself is only 4.4 MB. You’re looking at a nearly 900 MB download to get your first runtime. So how big are these runtimes? On a fresh machine, install KCalc from Flathub.

Your app metadata specifies what runtime it wants to use and a service downloads it and runs your app against it. Other solutions like Flatpak or Steam download the runtime separately. Suppose you want to make a simple calculator app. The point of this response is to reduce the amount of misinformation and misunderstanding that the article might have caused, as I have seen (and still see) many users post this article very frequently, without having a proper understanding of the subject.

I want to go over some of the author's arguments and explain some of the misunderstanding and claims.ĭo keep in mind that I have nothing against the author’s opinion. Late last year, this interesting article “ Flatpak Is Not the Future” was published to the public, and very quickly grabbed the Linux community’s attention.