this post was submitted on 07 Jul 2025
708 points (92.5% liked)

Linux

56538 readers
530 users here now

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.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS
(page 4) 50 comments
sorted by: hot top controversial new old
[–] kadaverin0@lemmy.dbzer0.com 4 points 1 week ago (2 children)

I'm relatively new to Linux. I honestly don't see what the problem is.

load more comments (2 replies)
[–] ter_maxima@jlai.lu 4 points 1 week ago (2 children)

I've heard Flatpaks aren't great at CLI tools, is that true ?

As a Nix user, I'm glad Flatpaks exist for other people, but I only ever use them when a package is not available from Nix directly. Seeing as Nix is literally the biggest package manager out there, it's a pretty rare occurrence.

[–] trevor@lemmy.blahaj.zone 3 points 1 week ago* (last edited 1 week ago)

I posted this in another thread, but reposting here because a lot of people, including myself up until very recently, were under that impression:

I've packaged a CLI that I made as a flatpak. It works just fine. Nothing weird was required to make it work.

The only thing is that if you want to use a CLI flatpak, you probably want to set an alias in your shell to make running it easier.

I'm not sure why more CLIs aren't offered as flatpaks. Maybe because static linking them is so easy? I know people focus on flatpak sandboxing as a primary benefit, but I can't help but think that if static linking was easier for bigger applications, it wouldn't be needed as much.

load more comments (1 replies)
[–] pineapple@lemmy.ml 4 points 1 week ago* (last edited 1 week ago)

I am definitely a fan. A lot of people say that flatpaks are bad because of sandboxing but I haven't seemed to have any issues with it.

Although I do try to use dnf when a dnf package is available (I use fedora)

[–] grimaferve@fedia.io 4 points 1 week ago

Honestly? I'm a fan of Flatpaks where they make sense. I'm also okay with Appimages. Native is pretty cool. Whatever gets the thing to run really.

I like to use the terminal to update my applications, it's just faster. I have an alias to run an update for native packages and flatpaks. You can use your GUI of choice. Or not, it's up to you. It's that sort of freedom that I love about using Linux.

In some cases, Flatpak actually helps, as in my case, with Prism Launcher. Some of my system libraries cause issues with a handful of mods, but the libraries distributed with the Flatpak get that working. Hopefully that's not foreshadowing more future library-related issues.

Just another tool in the toolbox. Use it or not, up to the user. I've even seen Slackware users who say they use Flatpak to ward off dependency rabbit holes.

[–] HexesofVexes@lemmy.world 3 points 1 week ago

Honestly, I am a little scarred from snap.

Otherwise I'm agnostic on flatpaks - I've used a couple and they're ok? They just remind me of old windows games that dump all their libraries in a folder with them.

On a modern system the extra space and loss of optimisation is ok, but on older hardware or when you're really trying to push your system to run something it technically shouldn't, I can see it being an issue.

[–] buwho@lemmy.ml 3 points 2 weeks ago

theyre whatever, they have their place in my system, but inprefer installing debs from the repo

[–] csolisr@hub.azkware.net 3 points 2 weeks ago (3 children)

That reminds me, is Flatpak packaging CLI tools already?

[–] trevor@lemmy.blahaj.zone 3 points 1 week ago

I've packaged a CLI that I made as a flatpak. It works just fine. Nothing weird was required to make it work.

The only thing is that if you want to use a CLI flatpak, you probably want to set an alias in your shell to make running it easier.

I'm not sure why more CLIs aren't offered as flatpaks. Maybe because static linking them is so easy? I know people focus on flatpak sandboxing as a primary benefit, but I can't help but think of static linking was easier for bigger applications, it wouldn't be needed as much.

[–] rfr_Foglia@feddit.it 3 points 1 week ago

Looks like it does? Or at least could?

https://unix.stackexchange.com/questions/740712/does-flatpak-support-command-line-applications

I've never seen one so far though

[–] NotProLemmy@lemmy.ml 3 points 2 weeks ago (1 children)
load more comments (1 replies)
[–] jabeez@lemmy.today 3 points 1 week ago

Is that supposed to be Ed Norton, or just an uncanny coincidence?

[–] HugeNerd@lemmy.ca 3 points 1 week ago

Furniture? Integrated circuit packaging?

[–] Horse@lemmygrad.ml 3 points 2 weeks ago (2 children)

there's a gui for flatpaks?

load more comments (2 replies)
load more comments
view more: ‹ prev next ›