OCI images that you can turn into a full-fledged developer workstation shipping Devbox, Nix, Homebrew, devcontainers and DevPod with one command. Pretty swanky!

  • thelastknowngod@lemm.ee
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I have long loooooong ago given up on distro hopping because, at the end of the day, most distros are close enough to each other that it doesn’t really matter which one you choose at the end of the day. These new immutable ones though… They seem cool as hell. I need to give one a go someday.

      • thelastknowngod@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        I feel like I left arch a decade ago. 😄

        It was rough going around the time of the systemd transition and needed something more consistently reliable. I’ve been on Mint ever since.

    • 9488fcea02a9@sh.itjust.works
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      Distro hopping always leads back to debian

      99% of the time, whatever drew you to a shiny new distro could be achieved in debian with minimal effort

      • KISSmyOS@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Yep, distro-hopping ended for me when I learned how not to break Debian Sid.
        (Basically, install apt-listchanges and if an update wants to remove stuff you need without replacing it with newer versions, or throws an error, wait a day and try again)

  • Prunebutt@feddit.de
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Can someone ELI5 why this is so great? I watched the video and I hardly get it. (Linux user for 18 years)

    • worldofgeese@lemmy.worldOP
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      Because it uses OCI images, it auto-updates like a Chromebook, and you can switch between modes, like say a gaming mode that’s a full SteamOS replacement, to a mode that gives you an entire development environment without needing to install and configure these layers or stacks of capabilities yourself.

      That’s very powerful. For cloud native developers like myself who are used to working with container images as the deliverable artifact, this makes that workflow very easy. Podman is included. You can create entire development environments at will that are totally “pure”: no side effects because everything you need is in the container. That’s a Dev Container.

      • sfcl33t@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        I’m still having a hard time grasping this, probably because I don’t understand OCI images. How would this be different than say using fedora with docker to spin up containers with stuff I need?

        • worldofgeese@lemmy.worldOP
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          1 year ago

          Hmm, well Fedora on its own (so no Silverblue) is very much your classic way of shipping a distro. That tends to mean that, over time, “cruft” accumulates as you upgrade your system, uninstall/reinstall packages, etc. They leave bits of themselves behind that can cause unwanted behavior.

          Fedora Silverblue, that Bluefin is based on, treats the entire system layer as “immutable”. Basically, it ensures consistency so that upgrades and package upgrades don’t leave the system in an inconsistent state.

          What Bluefin adds on top of this is a set of opinionated, pre-configured layers suited for getting particular groups of tasks done. Those layers are also immutable and tested as a whole, which makes shipping those layers at velocity easy (faster upgrades, less wonky behavior on upgrade) and easy to swap between, so you can go from gaming to developer mode without worrying about an accumulation of cruft.

          Is that helpful at all? There’s also this announcement blog post, which I found very helpful in understanding the value proposition.

  • vrighter@discuss.tchncs.de
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    “the next generation cloud-native”

    that’s as far as I got. Cloud native is an immediate, non-negotiable red flag for me

    • Antiochus@lemmy.one
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      They need to work on their branding. “Cloud Native” triggers images of subscription services and data mining. But the idea here is that the whole OS and its components are all sort of containerized, so you can just pull pre-configured “cloud” images that are guaranteed to work out of the box to your machine.

      • RickyRigatoni@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        That is one of the dumbest ways I’ve ever seen someone try to connect their product to the cloud buzzword. By that logic all stable linux distros are cloud since you pull the packages with preconfigured sane defaults from the repos.

        • Antiochus@lemmy.one
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          It’s hard to explain until you’ve used it, but in my experience I think this is much different than a traditional Linux distro. Every other distro I’ve tried has (to some extent) dependencies that can get out of whack, configuration drift that makes it hard to get things to work sometimes, random codecs or drivers or other things you need to install to get a system working as it should, etc. In the “cloud native” model, all the packages, drivers, etc. are built and tested in the cloud. So when they arrive on your machine, they “just work” and updates are handled automatically - it’s great. Maybe not great for tinkerers, but great for regular users who just want to use their computer.

          • vrighter@discuss.tchncs.de
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            the cloud is just someone else’s pc. if it can work in my machine, it can work there. The hard part of cloud stuff is the stuff outside your image. setting mount points, port redirections etc. When stuff doesn’t work, you usually don’t fix it in the image, but probably some configuration of the container.