Originally posted by pal666
View Post
Announcement
Collapse
No announcement yet.
Flatpak 1.8 Released For This Leading Linux App Sandboxing / Distribution Tech
Collapse
X
-
Originally posted by atomsymbol
My statement wasn't about the relative size of flatpak vs native Linux. It was about the size of native Linux hello world as such (which was wrongly claimed to be above 0.5 GB), without comparing it with flatpak hello world.
As for myself, I understand the analogy that you are using. Here's my "back in the old days" experience with "saving space":
Way back when I needed a simple utility in DOS (as in DOS on a PC) to send a formfeed signal to the attached printer.
I first tried to write it in Turbo C, but that ended up being a coding mess for a simple task along with including a large (for those days) standard C library in the output binary EXE.
Then I wrote it in Turbo Pascal, but that ended up with a binary that was like 3KB (smaller than the Turbo C binary EXE), but it's the early 1990s folks and "size mattered" back then. The default standard Pascal unit was the bulk of the binary EXE.
Then I pulled out my IBM PC BIOS reference manual and a my rarely used IBM PC assembly language programming book. I figured if I focused on exactly what I needed to do, then the final binary should be a "COM" file and not an "EXE" file.
For those old enough to know the IBM PC memory loading differences between "COM" and "EXE", no explanation is necessary. For those that learned programming in school but never learned this interesting little distinction, get a refund on your degree(s).
The final result, written in pure IBM PC assembly language using standard IBM PC BIOS calls, was then compiled & linked. The output was an executable binary "COM" file that was less than 100 BYTES in size that loaded very fast (for those days) and did EXACTLY what I needed (send a FF to the printer port and attached printer).
Perhaps a simple redirect of some ASCII code to the printer port might have done the same thing, but I wanted a simple binary program that would certainly not mess up the batch files that drove the application.
- Likes 8
Comment
-
Originally posted by uid313 View PostYou write a Hello World program and it is 45 bytes, then you package it with Snap or Flatpak and then it is half a gigabyte.
Code:$ flatpak list -d | grep Podcasts Podcasts Podcast app for GNOME org.gnome.Podcasts 0.4.7 stable x86_64 flathub system org.gnome.Podcasts/x86_64/stable acbd5375f3fe - 11,8 MB system,current
- Likes 4
Comment
-
Originally posted by NotMine999 View PostFor those old enough to know the IBM PC memory loading differences between "COM" and "EXE", no explanation is necessary. For those that learned programming in school but never learned this interesting little distinction, get a refund on your degree(s).
I want my money back because nobody teached me about even the existence of lisp not to mention the functionality history or anything about it. Also nobody even mentioned Emacs or Vim, I of course knew that they exist because I use linux for >20 years including before college, but especially Emacs is hard to get, it get's advertised as text editor which is like saying a House is a bed, nobody told me that it's a operating system.
Would loved to find that gem earlier in my live, and not waste 99.9% productivity by using garbage software outside of emacs.
- Likes 4
Comment
-
Originally posted by moonlite View Post
I don't know anything about snaps so won't comment on that, but for flatpak that statement just isn't true. See here:
Code:$ flatpak list -d | grep Podcasts Podcasts Podcast app for GNOME org.gnome.Podcasts 0.4.7 stable x86_64 flathub system org.gnome.Podcasts/x86_64/stable acbd5375f3fe - 11,8 MB system,current
Code:$ flatpak list -d … … … Version Branch Arch Origin Installation Ref Active commit Latest commit Installed size … … … 19.08 x86_64 flathub user org.freedesktop.Platform.GL.default/x86_64/19.08 393b8b73a7ed - 243,1 MB … … … … 1.6 x86_64 flathub user org.freedesktop.Platform.VAAPI.Intel/x86_64/1.6 82006efc71d3 - 8,7 MB … … … 19.08 x86_64 flathub user org.freedesktop.Platform.VAAPI.Intel/x86_64/19.08 c315ea075c13 - 37,0 MB … … … … 1.6 x86_64 flathub user org.freedesktop.Platform.ffmpeg/x86_64/1.6 d757f762489e - 7,7 MB … … … … 2.1.0 2.0 x86_64 flathub user org.freedesktop.Platform.openh264/x86_64/2.0 73f998362a6f - 778,2 kB … … … … 1.6 x86_64 flathub user org.freedesktop.Sdk.Extension.rust-stable/x86_64/1.6 635baaf8e4fe - 481,7 MB … … … 18.08 x86_64 flathub user org.freedesktop.Sdk.Extension.rust-stable/x86_64/18.08 4e8ef3c492cc - 686,3 MB … … … 19.08 x86_64 flathub user org.freedesktop.Sdk.Extension.rust-stable/x86_64/19.08 c0761410a856 - 505,8 MB … … … stable x86_64 flathub user org.gnome.Fractal.Locale/x86_64/stable 3253dbbd5b1e - 512 bytes … … … … 3.22 x86_64 gnome user org.gnome.Platform/x86_64/3.22 d44159b609a6 - 681,1 MB … … … … 3.26 x86_64 gnome user org.gnome.Platform/x86_64/3.26 1b78d7195d9c 552cd113ef7e 938,1 MB … … … … 3.28 x86_64 flathub user org.gnome.Platform/x86_64/3.28 6d1d0ebbd724 - 1,3 GB … … … … 3.34 x86_64 flathub user org.gnome.Platform/x86_64/3.34 8d75da77300d - 919,7 MB … … … … 3.22 x86_64 gnome user org.gnome.Sdk/x86_64/3.22 dd0de2810a73 7ec9b226b95c 1,5 GB … … … … 3.26 x86_64 gnome user org.gnome.Sdk/x86_64/3.26 d7758a43d75e e05fa500f556 1,6 GB … … … … 3.28 x86_64 flathub user org.gnome.Sdk/x86_64/3.28 31af0c10f8e4 - 2,2 GB … … … … 3.34 x86_64 flathub user org.gnome.Sdk/x86_64/3.34 d1513a628521 - 1,9 GB … … … 3.26 x86_64 gnome user org.gnome.Sdk.Docs/x86_64/3.26 1df8797de6da 5822c7bb0da9 141,6 MB … … … 3.28 x86_64 flathub user org.gnome.Sdk.Docs/x86_64/3.28 3d5283cbaa32 - 141,9 MB … … … stable x86_64 flathub user org.gnome.design.Palette.Locale/x86_64/stable 861ff6f7d38e - 512 bytes … … … … 3.22 x86_64 flathub user org.gtk.Gtk3theme.Arc/x86_64/3.22 62abe9abf900 - 513,0 kB …
- Likes 3
Comment
-
Originally posted by uid313 View PostYou write a Hello World program and it is 45 bytes, then you package it with Snap or Flatpak and then it is half a gigabyte.
- Likes 4
Comment
-
Originally posted by dragon321 View Post
Then you package it using traditional methods and realize it won't work on other distributions or break after update because dependencies are different.
b) if your software isn't maintained anymore, then it must be worth nothing
At least I haven't seen or been using any software, that requires ancient libraries
AND
The frequency in how many distributions change versioning means - people keep updating their systems for the sake of updating, not for the sake of using old software.
AND
Nobody knows how long flatpaks guarantees you a running runtime on newer linux installations.
So at the end flatpak is just another saussage that is hanging in the air - trying to convince people with the "security" and/or "breaking dependencies" kind of garbage, that no one really gives a flying shit for. Its just all a compendium of meaningless words - trying to catch those, who try to believe.
- Likes 1
Comment
-
Originally posted by Templar82 View PostThis attitude is one of the worst things in the software community at the moment.Last edited by arokh; 25 June 2020, 01:27 PM.
- Likes 3
Comment
-
Originally posted by Candy View Post
a) you shouldn't be using abandoned software in first place
b) if your software isn't maintained anymore, then it must be worth nothing
At least I haven't seen or been using any software, that requires ancient libraries
AND
The frequency in how many distributions change versioning means - people keep updating their systems for the sake of updating, not for the sake of using old software.
AND
Nobody knows how long flatpaks guarantees you a running runtime on newer linux installations.
So at the end flatpak is just another saussage that is hanging in the air - trying to convince people with the "security" and/or "breaking dependencies" kind of garbage, that no one really gives a flying shit for. Its just all a compendium of meaningless words - trying to catch those, who try to believe.
Not all developer wanna deal with tons of different distributions, and at the end of the day they will either
a) only care some random LTS version of Ubuntu and treat other distros as non-existing;
b) bundle all libraries it's using, and becomes another flatpak minus shared runtime and security updates.
by the way manylinux is effectively b), and it seems all ignorant ones in this thread are fine about it.Last edited by zxy_thf; 24 June 2020, 05:53 PM.
- Likes 4
Comment
Comment