We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Can MicroOS Desktop Be Your "Daily Driver"?

Formale Metadaten

Titel
Can MicroOS Desktop Be Your "Daily Driver"?
Untertitel
SPOILER ALERT: Probably YES!
Serientitel
Anzahl der Teile
45
Autor
Mitwirkende
N. N.
Lizenz
CC-Namensnennung 3.0 Unported:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen.
Identifikatoren
Herausgeber
Erscheinungsjahr
Sprache

Inhaltliche Metadaten

Fachgebiet
Genre
Abstract
Well, I do not know. What do I know, though, is that it has been my "daily driver" for a couple of months now. And it still is, and I am pretty happy about it! But let's make a step back. I have almost always used rolling distribution as I --entirely out of personal taste-- can't live without updated (bleeding-edge?) software. So I'm use to the occasional breakage that comes with them. It's kind of a challenge, and I'm up for it. It goes without saying that, when starting to use openSUSE, I went for Tumbleweed. But Tumbleweed does not break! And, yeah, that is awesome, I'm not saying it's not... But it, at the same time, means that I needed a new challenge. So, how about starting using something, as my main desktop, an immutable OS like MicroOS, and doing that without knowing much about podman and containers, and knowing absolutely nothing about Flatpaks? Wow, that sounds fun! So I did that, and this talk will be a report of such experience. The issues that I found. The things that I learned. In summary, how it is going for me using such a solution as my main OS, on the workstation that I use both for work and for personal computing. In fact, after (trying to!) describe what MicroOS is and what it is aiming at as a project (and also giving a little bit of details about the technology that makes it possible for it do look like it looks like and do what it does) I will cover things like how I got involved in the project, how I use it for my daily development work, especially focusing on the kind of special role that toolbox has in that, what are the major issues that I have found and how I overcame or worked-around them and what are the things that I think are working best and that I am most happy with. Sure, some aspects of all that are quite specific of my own workflow and of my own use-case. But I believe that the talk would still be able to offer a sensible and hopefully generic enough overview of the status of the project, the efforts that are necessary to get started with using it, the kind of user experience that one should expect if considering switching and some tips and tricks on how to avoid some of the issues that are still there.