I'm here to present already, just as a small outline, since I'm not the main
developer, but just a contributor, I'm just going to detail why I chose already as a daily
driver, and I'll present already, and I'll have with builds upon new gigs, and talk a
bit about early speech. As probably many of you have also done, I switched from Windows
to a new boot based distribution, some 10 years ago, I learned some valuable lessons that
fastes great, minimism, and efficiency is great, removing proprietary OS is possible.
And so when I started a few years ago to do some series, so to our development, I also learned
some other valuable lessons about the unique philosophy, how it works, how basically programs
interact with each other. Also, I learned that quite crafting your systems and optimizing
them is quite a fun task. Also, I learned that it can be take use, so I had some struggles,
I had to change computers like three times in two years, and I just learned that each time
we change, you have to do things over and over again. So at some point, I, so the flows
of these lessons, the unique philosophy is great, but it also forgets a lot about transaction
costs, which you have between the different apps you use, and you have like, when you
have to optimize everything, you do a lot of work, just making apps talking properly to each
other. As I said, life and loss happens, and it is tedious, but it doesn't have to be,
like I had some examples in the Emacs ecosystem that showed me that configuring your system
doesn't have to be that hard. And so that's why I choose new weeks and then I already
need to as a daily driver as a system, because new guy helps for translation costs. Basically,
you have one language to extend everything, and then you become more and more familiar with the
language and better and better. So life and loss happens, my answer was, I need reproducibility,
that's why I chose skis, and for the complexities of managing your configuration, that's where I
chose already as a framework, as a distribution. Just about RDE itself, maybe I just have to point
some things about geeks before to be able to present properly already, so it's already itself,
it's a developer and power user friendly geeks, sorry, the next distribution, using a building
upon geeks and it's tools. So the guy, the guy, the demon, a geeks system, and geeks home.
Maybe just to know how I have to present this, how much of you do know geeks has a package manager,
geeks has system, geeks system, and geeks home. Okay, so just geeks system itself,
it's basically what allows you to configure your system with reproducibility and declaratively
in a configuration file. And so it's basically all configuration you would have done as a route
non-functional Linux distribution, and geeks home is the same thing, but for the users, for the
management of the dot files and basically all services you would use as the user.
RDE itself can be compared to what space maps are to inax, but to do Linux, space
maps use these layers and do me max use models to basically have a handy way to configure
a system. RDE uses features for that, so features are blocks of configuration that provide
certain functionality for your user, such as setting up your image, TPGT, etc. And the tooling we rely on
are doing from geeks, just like space maps use this new package and do me max, sorry,
uses straight dot EL. The distribution itself has a few principles that can be
summarized as many many stands same. One of them is it has to be ergonomics, so we have
safety, you can buy new things, use contrast, readable fonts, buy default, it has to be
lightweight, so battery efficiency, we use first in native waiting apps, it has to work offline to
enable most workflows to work without a network, it has to be attention friendly, so we have
really more news of notifications and it has also to be to comply with standards, so we have
a policy to aggressively comply with the XDG based their specification when it's possible for
the applications we provide as features, that gives us a based on this principle a few
tools, I will not go over each one of them, but basically as a package manager and service manager,
it will build tools of geeks, so it new shape early in the new geeks, for the window manager, it's
way the terminal, it's either a liquidity of food, both are well supported by RDE and most of the
films you would do in daily life as a daily driver are from imacts, how does it looks, it's
quite minimalistic, as you can see, it's not a film you would put on a unique sport and have
like a lot of sugar and very pretty things, but it's actually quite useful, so it has good contrast
and everything, so as a daily driver I can confirm that it works well, another very important principle
is that we have to be reproducible and as the place as possible, so we are building a new geeks or
any setup or configuration can be easily replicated because we use the rollback tools that
do geeks provides, and so if you break any configuration you can roll back to the back in time
if you want and that's a huge guarantee for further system crafting if you want to be more
minimal, if you want to explore the limits of your system, for the reproducibility and the rollback
is perfect, we have tools to make state, so directly explicit and single ball or temporary,
we're still working on it, but there are already useful tools for that,
basically the logic is to help yourself avoid losing your data, if you choose that has this goal
that has this goal, or he itself tries to be very likable, we use new guys and these APIs,
we do not have any information on extensibility, so it's easy to throw out, modify or extend
an impart of a setup you want, it is opinionated but as base maxis and as doony maxis you can't
like provide the reason for a very simple way for use to configure your system and not be
opinionated, but it is composable and flexible enough to allow various language development,
science, it's a me and developed, so basically most of what you can think about and feel
as long as you stay in the first steps where LVE is able to have a compressed feature around that,
now just to enter a bit in order to just explain a bit how it works,
the user provides a list of features, or features that have options, so it's a very simple list
maybe I can try to show you if they're quickly
well I will when you when you question the right, and on the, so basically the user provides a list of
features, and the goal of the configuration, the goal of RE is to be able to provide a proper
profile for each system and for each own, and then to have a lifting of the reproducibility,
the profiles and everything is done by each system and by each own, the RE, so the configuration itself
does a few things, the features will calculate values, will provide values that are able to
use by other features, and that's why we can do a very easy cross configuration between the
features, because one feature can say to other features page, I'm here, you can conditionally
depend on me for some blocks of configuration, and that's very convenient, based on that, you just
see that a feature itself is actually quite easy to understand what we will put in it, so basically
we have to take the features and their options, we do some type checking on the options,
in the end we return values, values themselves are used in a geek system, a services system
gather, and in a home system gather, and then based on that RE, they both provide both to
profiles and everything works well, and based on this, once you understand this, it's actually
quite easy to write your own features, this is an non-exceptive list of features, I do not have the
time to go through them directly, but we have very neat email features, also when those management
features programming features and everything about the next two, just as said, a cross configuration
is very, is a value added to me, above weeks that already provide, so it basically enables when
they're turned to answer to this question, very simply, what if I want a piece of conflict
in software error, if and only if software be is present, to me, but maybe that's not true,
it's very difficult to do this kind of thing in new bits, and it's very simple to do that in RDE,
another value added is to have serializers to define services more easily,
so we have some serializers to basically define your config in a new guide, then the serializers
pass it to CSS or JSON or list depending on what the configuration of the app expect, and based on
that we can define this or own system services in a more flexible way than what is done in
weeks today, just a word about all these future, it's quite major and it has been usable for
years, there are a lot of working progress not to go around all that, but it has a good dynamic
along with the whole guide ecosystem actually, friendly community and like in Geeks every user
benefit from contributions from other contributors, if you want to support the project there is
an open collective page, as I said, it's a small but very welcoming community, we will be happy
with Andrew to also help you get along with the system if you're interested, so don't hesitate to
get in touch, and I'm done, I'm happy to take questions.
Thank you, it's a geeks world, right? Yeah, and the project leader is amazing and we're
dropping the project, yes, please have questions today if you can set up if you want, and then
also it's going to be a messy because we're back to back, but please try to squeeze in, right? All right,
go ahead, who wants how easy is it to set up a party in like in a family environment, like a
VM or like a family or shell or something, just try it out? There is a make script in the main repo
that she has a VM, a VM or VM something object, and based on that you can actually just
pwn the VM and try it yourself, it does it with a minimal configuration but it is enough to just try it.
Sorry?
Any more questions? Any more questions? Yeah, you'll see it on your
How often do changes in the geeks break, are you going to get your questions?
Um, maybe. So the question was how often does changes in geeks break already?
Not that often, I would say something like one, once every two months, something like that,
but it's usually quickly fixed because I add a geeks often and all year often and once it's
once it breaks, I fix this basically.
Other questions? Yeah, well, maybe both about a screening, RDD to geeks or a factor of RDD,
yeah, and so RDD was actually was actually originally the home of geeks home of the geeks home
and as I presented, the difficulty was upstream in RDD to geeks is that it is updated and it
it makes choices that I think would be hard to merge in geeks upstream.
As I said, we have friendly relation, we probably contribute to geeks or Andrew like me.
But I'm not sure it's doable. I think the part where we upstream the most most of what was
doable was when geeks were merged in geeks. Thank you, Niklas.