From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
I like it but I would prefer it to be more restrictive out of the box. Such as have apps declare a list of urls the are permitted to contact , a browser could have * .
I'd like a more granular filesystem list too more akin to apparmors were each file path needed is explicitly defined, in some cases you would need a wildcard or a directory but for most apps this could be done.
I love the idea and the philosophy behind ! I have no trouble with them for now, one click install perfect.
However I’ll never use it for programming and I don’t understand why people use vs code flatpak or other coding app, because the app is contained and cannot interact with your system.
the app is contained and cannot interact with your system.
It can. Think of it like allowing a phone app to interact with your stored files.
https://docs.flatpak.org/en/latest/sandbox-permissions.html#
@Shareni@programming.dev @CeeBee@lemmy.world thanks for the resources I did not know. I was pretty confused it was not possible to do it and here you are thx ! :)
The sandbox can be very cumbersome when there is not a way to break out. I'm thinking specifically of command line tools for developers. You can poke holes in the sandbox to access the filesystem, but the moment you want to run an executable it won't let you.
Flathub doesn't accept CLI tools (unlike the Snap store)
Regarding modifying Sandboxes, try Flatseal
Flatpaks aren't meant for command line utilities.
Right. I mean something like an embedded terminal in an IDE that has full shell access to the host environment.
I think Flatpaks are great for applications like Firefox, Steam, etc. where dependencies or delay in package distribution due to building multiple versions can be a problem.
However, there are many situations where Flatpak's sandbox can be more detriment than helpful, if the application wasn't developed with that in mind. It's not a silver bullet for everything.
I never ever will use a flatpak or snap or whatever "application". I'm using good old .deb package.
I like it, it's good for desktop apps but I LOVEEEEEE nix, if there was a graphical box distro I think it would beat everything else out of the water. Full reproducible builds is not something to sneeze at
It's alright
What's not to Ike? These systems' development has been long overdue.
The picture is too big.
Where's that Chris Pratt meme? --
I don't know what that is and at this point I'm afraid to ask
Flatpak is a project trying to fix many things at once