Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)J
Posts
0
Comments
81
Joined
3 yr. ago

  • All the supported IDEs in bluefin are brew packages and tailscale is included.

    No idea on the selinux stuff though.

    My thesis is essentially that we’re creating too many package package managers with too many compromises.

    Your issues appear to be config/documentation related. What apps am I missing out on by not using system package managers?

    package managers, you can do essentially anything.

    Yeah, like break your computer, no thanks. :)

  • No they would brew install neovim. System-level package management goes away entirely, that's the point.

    What new package managers? homebrew has been around for years. What problems are you describing? If you mean read only root that has been around since the 1980s. The problem as you describe it has been removed, you move on from package based entropy to image based systems.

    This isn't a trend, modern linux is this way, it's just the desktop that has been behind until now.

  • Bluefin maintainer here, you've described how Bluefin works except it's ~/.local/bin.

    I am pretty sure we have not been developing package managers lol.

  • You're doing it the correct way, usually the people who are confused are used to their existing linux ways. You only have to learn this way and that will not only be best practice but works on any linux distro.

  • The immutable gimmick that’s currently going on right now is still way too flavor of the month for new users who are trying to learn from a ground set of nothing.

    New users aren't going to administer their computers either. there's no "flavor of the month" it's just teaching new users how to administer linux systems properly. And of course directions on the internet are going to be incorrect, the only correct solution is to follow the documentation, not random guides on the internet.

  • It's an image, there's no such thing as "left all over the place". Source: I'm one of the maintainers.

  • All of the affected files are in the user's home directory, not on the system.

  • The dotfiles between GNOME and KDE are the same, the base image doesn't matter, if you try to switch DE's on old distros you have the same problem.

  • Bluefin comaintainer here. The metrics are flathub and app developer donations, not the base image. You spread the love when you install a flatpak or buy a linux game and make those numbers go up.

    The idea that the base OS is important isn't a thing, the only way to fix the economics of the linux desktop is to focus on applications, not distros.

  • back to a normal Linux.

    What's normal linux?

  • What's stopping you from turning updates off?

  • Bazzite contributor here, there's no reason to care about this. This term just confuses people you can safely ignore it.

  • The Bazzite team doesn't control the wikipedia page, just the official documentation. Someone made up the term "immutable design", that's not a thing it's just a container. There's no need to confuse people just call it bazzite or a container. Atomic is a fedora brand name, it's not a thing to classify things under.

    As you can see from the comments in the thread all this does is confuse people.

    Source: I work on bazzite

  • lol you're confusing me, bazzite isn't immutable. Do you mean to say "Bazzite is growing for other reasons?"

  • Convince me to switch!

    Why? If your computer is working fine there's no reason to mess with it. bootc images are for people who do not want to use whatever you mean by 'normal' Fedora.

  • I mean yeah sure, if you're not a developer you can just use it like a chromebook. :D

  • ?

  • Bluefin/Aurora adoption takes a bit longer because developers have to adjust their workflows, and there’s still this odd stigma around atomics.

    Bluefin maintainer here, our target audience are container people, not people who want to adjust their workflows. The people we cater to don't have an opinion on "atomics" because no one's ever heard of that term. They've heard of docker or podman though.