• 1 Post
  • 22 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle


  • The buzz word is not aimed at the regular gaming nerd. It is aimed at gaming nerds who are also developers. Universal blue, the project behind Bazzite, Bluefin, and Aurora, aims to market to developers to use their systems first, on the basis of the tech backend. So then they make the cool FOSS things that the nerd public can use. Cloud native just means that something is engineered and made to make use of the container based devops pipeline.

    For example, an atomic immutable OS that is meant to be developed and distributed via the container infrastructure (this is what Universal Blue is). So, instead of working on making an OS the regular way, collecting packages and manually connecting and tidying up absolutely every puzzle piece so it fits together, then pushing it through the installer packaging wizard, etc. This OSs are made by taking an already existing distribution, in this case Fedora atomic distros (but this is by no means mandatory), then customizing some things. Like installing libraries, applications, firmware, kernels and drivers. Then putting it all into a container image, like you would do with a docker or a podman server image. This way, on the user side, they don’t need to install the OS, instead they already have the minimal atomic system handling framework and just copy and boot into that OS image. This automates a lot of the efforts required for bundling and distributing an OS, and it makes new spins on existing distros really fast and efficient to make. It also means that users don’t need to be tech savvy about stuff like directory hierarchies or package management, and updates, installs, upgrades can all be automated to the point of the user barely even noticing them.

    On a similar note, these distros, as development workstations, are usually pre-configured to make use of a container based dev pipeline. Everything is flatpacks and development is handled all via docker, pods, etc. Keeping the system clean from the usual development clutter that sediments over time on a traditional development cycle. As a happy coincidence, this makes the dreaded “works on my machine” issue less prevalent, making support of software a tad easier.












  • If you bothered to read the article, you’d notice that the charger was chosen by the manufacturers a decade ago in a summons by the European commission. If Apple had complied to do what they agreed to do back then, this law wouldn’t exist. But they got whiny and litigious. So, instead of an at will standardization program, the EU decided to make it mandatory by law, to shut Apple up, and anyone else who wanted to forcibly refuse to comply. The cool thing about European law is that nothing is written in stone. Not even constitutions are considered sacred, unlike in the Americas, and can be changed at any point or amended as long as proper procedures are followed. There’s nothing, ever, preventing the EU from calling another commission of tech companies to choose a new charger, if a better one ever shows up.



  • dustyData@lemmy.worldtoLinux@lemmy.mlLinux suggestion
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    13 days ago

    Try Aurora DX (it means the developer edition). It’s KDE but with a Fedora base and immutability. It means that even if an update breaks something (unlikely but still) you will always have a working system available to fall back to. It does mean that development is meant to be done via containers, but I find this solution to be way cleaner and easier to work with than traditional package conflicts madness. Give it a go.





  • Unless we invent cold fusion between the next 5 years, they will never be economical. They are the most energy inefficient thing ever invented by humanity and all prediction models state that it will cost more energy, not less, to keep making them better. They will never be energy efficient nor economical in their current state, and most companies are out of ideas on how to shake it up. Even the people who created generative models agree that they have just been brute forcing by making the models larger with more energy consumption. When you try to make them smaller or more energy efficient, they fall off the performance cliff and only produce garbage. I’m sure there are researchers doing cool stuff, but it is neither economical nor efficient.