WEBVTT

00:00:00.000 --> 00:00:02.839
Two questions. Yeah. Do you have a rule like,

00:00:02.960 --> 00:00:05.440
okay, so I'm going to update this year or this

00:00:05.440 --> 00:00:09.380
month every year or every few years? And what

00:00:09.380 --> 00:00:11.880
are your thoughts on automatic security updates?

00:00:12.380 --> 00:00:16.120
Yeah, basically what you see on my screen right

00:00:16.120 --> 00:00:20.640
now are two same things. So this is the same

00:00:20.640 --> 00:00:24.179
as this. Okay. Just a modern version of this.

00:00:24.440 --> 00:00:28.640
I really thought that Arch... should be the perfect

00:00:28.640 --> 00:00:31.739
distribution for my needs at the time, which

00:00:31.739 --> 00:00:35.200
is giving me the latest software. And for a time,

00:00:35.219 --> 00:00:38.640
it really felt like I did a really good decision.

00:00:38.899 --> 00:00:41.619
The first time that I pulled something from Arch

00:00:41.619 --> 00:00:43.979
user repository was day one when I installed

00:00:43.979 --> 00:00:47.320
Arch. Then I thought, like, what did I just do?

00:00:47.439 --> 00:00:50.179
I don't know. Let's reinstall the operating system

00:00:50.179 --> 00:00:52.380
because I have no... It's not that I broke anything.

00:00:52.539 --> 00:00:54.600
It's just that I don't know what I just pulled.

00:00:54.600 --> 00:00:57.049
You didn't trust it. Yeah. And then something

00:00:57.049 --> 00:01:00.469
else broke later on. And then I downloaded the

00:01:00.469 --> 00:01:03.549
FlatHub version of that. After a while, I ended

00:01:03.549 --> 00:01:06.530
up with a lot of Flatpak software. Instead of

00:01:06.530 --> 00:01:10.329
using Arch software, Arch Linux told me, no,

00:01:10.530 --> 00:01:14.609
you're not recording. Not today, OBS is now not

00:01:14.609 --> 00:01:19.650
working. And imagine a cartoon character turning

00:01:19.650 --> 00:01:22.349
from pink color of the face to the red color

00:01:22.349 --> 00:01:24.769
of the face in Steam. Now, I have a question

00:01:24.769 --> 00:01:28.010
for you. Because the Nix users have been very

00:01:28.010 --> 00:01:30.709
quiet in chat. I'm not sure if my chat doesn't

00:01:30.709 --> 00:01:33.569
work, but they must be like now going through

00:01:33.569 --> 00:01:38.170
a lot of feelings. As for systemd, that's for

00:01:38.170 --> 00:01:43.329
kids. A lot of people like the Unix philosophy,

00:01:43.709 --> 00:01:48.349
which says do one thing only and do it the best

00:01:48.349 --> 00:01:54.200
possible way. That's hardly a good example, but...

00:01:54.200 --> 00:01:58.359
Yeah, but... If you're listening to this as a

00:01:58.359 --> 00:02:00.500
podcast, remember that it was originally recorded

00:02:00.500 --> 00:02:02.579
as a video. If you're not following along, you

00:02:02.579 --> 00:02:04.359
can go to my YouTube channel. My username is

00:02:04.359 --> 00:02:06.379
Linkarsu. And if you want to support me to keep

00:02:06.379 --> 00:02:08.639
this podcast going, you can donate in Ko -fi.

00:02:08.759 --> 00:02:10.099
I'm going to leave a link in the description.

00:02:10.419 --> 00:02:12.280
All right? So let's get started with this chapter

00:02:12.280 --> 00:02:18.759
then. Now, is Darth your name? It will remain

00:02:18.759 --> 00:02:25.879
my name for foreseeable future. I'm still thinking

00:02:25.879 --> 00:02:29.379
about using the real one. I know that all of

00:02:29.379 --> 00:02:33.740
you guys on Linux and free software fans are

00:02:33.740 --> 00:02:37.300
using your real name. It's just, I don't know,

00:02:37.340 --> 00:02:40.000
I haven't decided yet. It is what it is. People

00:02:40.000 --> 00:02:43.500
learn to call me just Linux Renaissance, whatever.

00:02:44.199 --> 00:02:48.449
It's fine. Yeah, I don't use my real name either.

00:02:48.610 --> 00:02:50.990
It's Link, the one that I use. So you can call

00:02:50.990 --> 00:02:53.949
me Link if you want or whatever is easier for

00:02:53.949 --> 00:02:57.710
you. We can get started if you want. I think

00:02:57.710 --> 00:03:02.509
we already did. Yeah. But yeah, you do your stuff.

00:03:03.030 --> 00:03:10.349
Yeah. So we didn't plan this at all. And someone

00:03:10.349 --> 00:03:13.710
in Discord actually shared your channel. And

00:03:13.710 --> 00:03:17.129
I said, yeah, there's a guy that switched over

00:03:17.129 --> 00:03:21.650
from Arch to Debian. And I was like, okay. And

00:03:21.650 --> 00:03:24.090
I opened the link, saw your channel. Yeah, I

00:03:24.090 --> 00:03:26.050
watched the video and I was like, ah, pretty

00:03:26.050 --> 00:03:29.669
interesting. And I remember seeing your hat somewhere.

00:03:29.930 --> 00:03:32.909
And I was like, I think I've seen this guy. And

00:03:32.909 --> 00:03:35.110
I think I saw you in a video in which you said,

00:03:35.189 --> 00:03:37.590
don't use Discord or something, right? Yeah,

00:03:37.629 --> 00:03:40.699
yeah, yeah. That's one of mine, yeah. Okay. I

00:03:40.699 --> 00:03:43.520
looked it up then in your channel and it was

00:03:43.520 --> 00:03:47.599
like, yeah, I remember this guy. Yeah. So, Tart,

00:03:47.680 --> 00:03:50.240
welcome. Thanks for sharing it with us. How's

00:03:50.240 --> 00:03:54.939
it going? Good. Good. I mean, this was quite

00:03:54.939 --> 00:03:59.099
an interesting way to meet up because I have

00:03:59.099 --> 00:04:02.979
honestly haven't heard of you until before I

00:04:02.979 --> 00:04:07.629
went to bed last night and we are now live. Yeah,

00:04:07.629 --> 00:04:14.509
crazy. As one of my guys, Iceblade, said, what

00:04:14.509 --> 00:04:16.829
did he say, like a quick turnout or something?

00:04:17.670 --> 00:04:22.230
Yeah, less than 24 hours of planning, of meeting

00:04:22.230 --> 00:04:24.970
us, you know, and yeah, it just happened. Plus

00:04:24.970 --> 00:04:27.250
sleeping and going to work included, you know.

00:04:27.490 --> 00:04:32.110
Yeah, yeah, pretty fast planning. I told my wife,

00:04:32.189 --> 00:04:38.050
actually, do you recognize this hat because and

00:04:38.050 --> 00:04:41.689
i was expecting to her to tell me like yeah from

00:04:41.689 --> 00:04:44.589
one of the linux things that you talk about or

00:04:44.589 --> 00:04:47.750
something and she said yeah from kid rock and

00:04:47.750 --> 00:04:53.290
i'm like have you have you seen him no usually

00:04:53.290 --> 00:04:56.810
people remember the hat if nothing else yeah

00:04:56.810 --> 00:05:00.610
it's a pretty good pretty good prop is it oh

00:05:00.610 --> 00:05:03.670
of course it's red hat related but what's your

00:05:04.410 --> 00:05:09.709
deal with Red Hat? No deal whatsoever. I don't

00:05:09.709 --> 00:05:16.329
even use Fedora as the Linux distro. I tried

00:05:16.329 --> 00:05:19.689
but didn't quite work out for me. The whole idea

00:05:19.689 --> 00:05:23.389
was basically I started my YouTube channel three

00:05:23.389 --> 00:05:26.750
years ago and I made two videos. There was no

00:05:26.750 --> 00:05:30.910
Red Hat back then. I'm just gonna try to summarize

00:05:30.910 --> 00:05:39.009
it. I have used Linux before like in 1997 starting

00:05:39.009 --> 00:05:44.189
from there and after that there was a lot of

00:05:44.189 --> 00:05:48.189
windows and needed for work and stuff like that

00:05:48.189 --> 00:05:52.029
and I played a lot of video games in my life

00:05:52.029 --> 00:05:54.509
so that kind of didn't work on Linux back in

00:05:54.509 --> 00:06:01.199
the day and lately I really got very, very tired

00:06:01.199 --> 00:06:03.959
of Windows and that was years ago, not today.

00:06:04.240 --> 00:06:09.860
But slowly I transitioned fully to Linux to the

00:06:09.860 --> 00:06:12.860
point where I haven't been using Windows at all

00:06:12.860 --> 00:06:17.800
for a couple of years now that my work included.

00:06:19.139 --> 00:06:24.300
Also private life, yeah. And I started this YouTube

00:06:24.300 --> 00:06:27.399
channel and first I called it back to Linux.

00:06:28.519 --> 00:06:32.100
as it was supposed to represent my full return

00:06:32.100 --> 00:06:36.040
to Linux. That was the title. And there was no

00:06:36.040 --> 00:06:39.600
Red Hat at all. And I was with my family in London,

00:06:39.699 --> 00:06:45.160
UK. That was like two years ago or something.

00:06:45.339 --> 00:06:49.800
I kind of forgot the dates. And there was this

00:06:49.800 --> 00:06:54.009
shop with hats and they just stopped. uh at the

00:06:54.009 --> 00:06:56.410
what do you call it when you look into the shop

00:06:56.410 --> 00:07:00.410
from the street the glass part um i'm not that

00:07:00.410 --> 00:07:03.889
good with english but i manage uh there was this

00:07:03.889 --> 00:07:06.470
hat literally looking at me and telling me buy

00:07:06.470 --> 00:07:10.649
me buy me and i just went in and bought it and

00:07:10.649 --> 00:07:14.730
i i looked at the hat and told myself that yeah

00:07:14.730 --> 00:07:17.490
this this is for the channel and that's when

00:07:17.490 --> 00:07:21.319
i renamed the channel to Linux Renaissance, but

00:07:21.319 --> 00:07:25.000
there was a gap of a full year, because if you

00:07:25.000 --> 00:07:31.279
scroll down to the very latest one, you will

00:07:31.279 --> 00:07:33.399
see... Oh, the latest one. Yeah, yeah, you did

00:07:33.399 --> 00:07:36.920
good, you did good. In the history, yeah. So

00:07:36.920 --> 00:07:39.480
the first two are, you can see, I think, three

00:07:39.480 --> 00:07:43.439
years ago or something. They didn't quite work

00:07:43.439 --> 00:07:49.379
out and... There was a gap, right? And then I

00:07:49.379 --> 00:07:52.399
just do a little bit of rebranding of the channel

00:07:52.399 --> 00:07:57.620
and then I went in really hard. I guess that's

00:07:57.620 --> 00:08:02.920
a small summary of the channel. What are your

00:08:02.920 --> 00:08:05.540
thoughts on Red Hat? Have you used it as a distro

00:08:05.540 --> 00:08:08.620
or do you have any thoughts on it? No, not really.

00:08:09.000 --> 00:08:11.699
I mean, there was a Red Hat distribution back

00:08:11.699 --> 00:08:14.439
in the day. That one is actually dead. the one

00:08:14.439 --> 00:08:17.860
that used to be called Red Hat. And now we have

00:08:17.860 --> 00:08:22.740
the one called RHEL, Red Hat Enterprise Linux.

00:08:23.660 --> 00:08:28.319
That's the actual one now. This one is commercial

00:08:28.319 --> 00:08:31.120
Linux distribution for big companies and big

00:08:31.120 --> 00:08:35.919
businesses. It is good, but I'm not sure what

00:08:35.919 --> 00:08:41.019
to do with that on a personal computer. So you

00:08:41.019 --> 00:08:43.940
can use it as a workstation. I just don't have

00:08:43.940 --> 00:08:47.100
any personal feelings for using that distribution.

00:08:47.379 --> 00:08:50.559
It just doesn't give me anything that I would

00:08:50.559 --> 00:08:53.580
want from a Linux distribution. And I'm pretty

00:08:53.580 --> 00:08:57.919
sure that in this chat today, we will get to

00:08:57.919 --> 00:09:01.600
the point where we discuss how people usually

00:09:01.600 --> 00:09:04.580
pick their Linux distribution, considering we

00:09:04.580 --> 00:09:08.500
have quite a lot of them, right? So the prop

00:09:08.500 --> 00:09:12.350
itself, literally has nothing to do with red

00:09:12.350 --> 00:09:19.110
hat although it is a hat of a red color but other

00:09:19.110 --> 00:09:22.909
than that it's just nothing representing you

00:09:22.909 --> 00:09:27.490
know any of my values or you know whatever okay

00:09:27.490 --> 00:09:32.409
okay okay and i see your channel you have 289

00:09:32.409 --> 00:09:37.159
videos almost 5000 subscribers right now It's

00:09:37.159 --> 00:09:39.980
Linux related content. What else do you talk

00:09:39.980 --> 00:09:42.700
about in your channel? I saw some Emacs related

00:09:42.700 --> 00:09:46.299
stuff in there, right? Yeah, it's mostly free

00:09:46.299 --> 00:09:49.649
software. So there will be a lot of stuff that's

00:09:49.649 --> 00:09:52.610
related to free software, including Linux and

00:09:52.610 --> 00:09:58.250
FreeBSD and OpenBSD and applications that are

00:09:58.250 --> 00:10:01.049
free software. So, of course, there will be some

00:10:01.049 --> 00:10:05.350
Emacs. There will probably be some Vim as well.

00:10:05.490 --> 00:10:08.710
But it's never about... I'm not one of those

00:10:08.710 --> 00:10:10.929
Vim versus Emacs. I don't really feel anything,

00:10:11.029 --> 00:10:16.149
any of that. in that way. We'll get to the MX

00:10:16.149 --> 00:10:21.409
part soon, but what I wanted to say is that the

00:10:21.409 --> 00:10:25.490
overall theme of the channel is basically free

00:10:25.490 --> 00:10:30.230
software and well, I guess a bit of privacy,

00:10:30.450 --> 00:10:33.049
but not hardcore privacy. I'm not that kind of

00:10:33.049 --> 00:10:39.289
a channel. I can't help people to stay as private

00:10:39.289 --> 00:10:41.889
as they want. There are much better channels

00:10:41.889 --> 00:10:45.990
than mine. Most of the content that I do is what

00:10:45.990 --> 00:10:50.909
I personally do for myself. And I don't really

00:10:50.909 --> 00:10:54.350
produce content for views, if you know what I

00:10:54.350 --> 00:11:00.940
mean. I do check out my analytics, but... As

00:11:00.940 --> 00:11:03.820
time goes by, I think that's a huge waste of

00:11:03.820 --> 00:11:09.779
time. Simply because people who watch YouTube

00:11:09.779 --> 00:11:12.720
analytics for their own channel usually should

00:11:12.720 --> 00:11:16.340
be doing that in order to adapt their content

00:11:16.340 --> 00:11:20.460
to what the audience wants. However, I don't

00:11:20.460 --> 00:11:22.799
want to adapt my content to what other people

00:11:22.799 --> 00:11:26.610
want. I just produce what I do. for myself and

00:11:26.610 --> 00:11:29.950
share it with everyone so you know if it turns

00:11:29.950 --> 00:11:33.450
out well thumbs up for that if it doesn't turn

00:11:33.450 --> 00:11:36.429
out very good you know I do have a small community

00:11:36.429 --> 00:11:41.490
with whom I am really happy with and we chat

00:11:41.490 --> 00:11:44.409
pretty much every day and I just love all those

00:11:44.409 --> 00:11:47.450
people that there aren't many of them but it's

00:11:47.450 --> 00:11:51.740
you know a cozy environment and I I want it to

00:11:51.740 --> 00:11:55.620
remain as cozy as possible. So it's not that

00:11:55.620 --> 00:11:58.659
I don't want more viewers. It would be, you know,

00:11:58.659 --> 00:12:03.899
thumbs up for that. But I will not succumb to

00:12:03.899 --> 00:12:08.860
the analytics to guide me to what I need to do,

00:12:08.899 --> 00:12:14.980
you know, on YouTube. That's basically what kind

00:12:14.980 --> 00:12:19.700
of the channel this is. Okay, okay. Now... I

00:12:19.700 --> 00:12:24.320
saw there about Matrix, you know, and I was like,

00:12:24.519 --> 00:12:27.639
what is Matrix? Do you mind sharing a little

00:12:27.639 --> 00:12:30.740
bit about that? Is that IRC? Because I don't

00:12:30.740 --> 00:12:33.039
understand Matrix, to be honest, but I joined

00:12:33.039 --> 00:12:36.899
your server. Is it a server that has multiple

00:12:36.899 --> 00:12:41.159
channels? What is it? Yeah, I could try to explain

00:12:41.159 --> 00:12:43.860
it shortly. So I think a lot of viewers will

00:12:43.860 --> 00:12:46.899
be pretty familiar with Discord. So let's take

00:12:46.899 --> 00:12:51.309
that as a ground point. for comparison. So Discord

00:12:51.309 --> 00:12:56.570
is a centralized place from a certain company

00:12:56.570 --> 00:13:00.649
which produces this server and this client software

00:13:00.649 --> 00:13:04.169
and they give you a client and with this client

00:13:04.169 --> 00:13:08.509
you can create your own community space which

00:13:08.509 --> 00:13:11.769
they call server for whatever reason because

00:13:11.769 --> 00:13:14.629
it's not really a server it's just a community

00:13:14.629 --> 00:13:18.970
space and in there you can put some rooms. I

00:13:18.970 --> 00:13:22.129
think everyone knows that. So matrix kind of

00:13:22.129 --> 00:13:28.070
came out from the need as that's how I see it.

00:13:28.190 --> 00:13:32.710
They came out from the need to replace the proprietary

00:13:32.710 --> 00:13:37.080
solution which is very popular. with something

00:13:37.080 --> 00:13:40.220
that is fully free software and also decentralized

00:13:40.220 --> 00:13:45.220
and by decentralized you can think of email you

00:13:45.220 --> 00:13:47.919
know how email works email is is decentralized

00:13:47.919 --> 00:13:53.179
in a way that you have your name at the domain

00:13:53.179 --> 00:13:58.039
and usually the domain means the where your domain

00:13:58.039 --> 00:14:02.500
is hosted on some server. You can have email

00:14:02.500 --> 00:14:04.879
with Microsoft domain, you can have email with

00:14:04.879 --> 00:14:07.720
Gmail domain, but also you can host your own

00:14:07.720 --> 00:14:12.360
and your own email server and they can all interconnect

00:14:12.360 --> 00:14:15.419
because if you send email to this address, it

00:14:15.419 --> 00:14:20.179
definitely gets there. That's federation, right?

00:14:20.320 --> 00:14:22.659
And with matrix is pretty much the same because

00:14:22.659 --> 00:14:29.350
I have my own matrix server and makers of uh

00:14:29.350 --> 00:14:33.809
matrixed software uh have given us this possibility

00:14:33.809 --> 00:14:37.570
that we can download the server install it on

00:14:37.570 --> 00:14:41.450
our own server even at home mine is running in

00:14:41.450 --> 00:14:45.269
my own house not really a professional hosting

00:14:45.269 --> 00:14:48.169
service you know but if it goes down what happens

00:14:48.169 --> 00:14:52.090
your matrix i will i will explain what happens

00:14:52.090 --> 00:14:55.870
if it goes down uh but it's important to understand

00:14:55.870 --> 00:15:00.120
that you have a username on the server, which

00:15:00.120 --> 00:15:04.299
is me. I am dart at fosheadquarters .org. That's

00:15:04.299 --> 00:15:08.080
my server. And when I go into someone else's

00:15:08.080 --> 00:15:12.600
room on Matrix, which is hosted on whatever other

00:15:12.600 --> 00:15:16.220
server of Matrix, I just participate there. And

00:15:16.220 --> 00:15:20.000
the way the rooms on Matrix work is basically

00:15:20.000 --> 00:15:22.919
they copy their entire contents to all of the

00:15:22.919 --> 00:15:29.600
participating Matrix servers. Maybe it's a bit

00:15:29.600 --> 00:15:33.340
hard to grasp without drawing it but basically

00:15:33.340 --> 00:15:38.120
if my server goes down and my server hosts my

00:15:38.120 --> 00:15:44.500
rooms then everyone else who is not on my server

00:15:44.500 --> 00:15:48.039
will still be able to talk in my rooms because

00:15:48.039 --> 00:15:52.600
my room is synchronized within the matrix federation.

00:15:53.529 --> 00:15:58.090
And once I get up my server back up, then me

00:15:58.090 --> 00:16:01.590
and other people who are on my server will catch

00:16:01.590 --> 00:16:04.809
up with everyone else who have been chatting

00:16:04.809 --> 00:16:08.769
in my room that was replicated elsewhere. So

00:16:08.769 --> 00:16:14.009
it's pretty resilient in terms of some servers

00:16:14.009 --> 00:16:19.429
falling down. It's kind of a middle ground between

00:16:19.429 --> 00:16:25.789
IRC, as you say, IRC and Discord, I think. Maybe

00:16:25.789 --> 00:16:29.409
a bit closer to Discord, but I would say somewhere

00:16:29.409 --> 00:16:33.230
in the middle. Oh, so it's not IRC, right? I

00:16:33.230 --> 00:16:41.110
think both Discord and Matrix have grown out

00:16:41.110 --> 00:16:47.600
of IRC software. They both have this in their

00:16:47.600 --> 00:16:51.259
background. Not literally, but they came out

00:16:51.259 --> 00:16:56.179
of the IRC protocol. Also, Twitch chat is still

00:16:56.179 --> 00:17:00.539
IRC, like very naked IRC. Because when I have

00:17:00.539 --> 00:17:03.899
to talk to Neobim maintainers, for example, they

00:17:03.899 --> 00:17:08.259
just use Matrix, right? I have Element installed.

00:17:08.380 --> 00:17:10.859
That's the client I'm using. And I send the messages

00:17:10.859 --> 00:17:13.890
there. But I'm like, what is... What is this

00:17:13.890 --> 00:17:16.170
thing about? Like, why did they use matrix? Why

00:17:16.170 --> 00:17:20.089
don't they use Discord? So, privacy then? Is

00:17:20.089 --> 00:17:23.289
that the main thing with matrix? But isn't it

00:17:23.289 --> 00:17:26.150
hosted on someone else's server in case your

00:17:26.150 --> 00:17:29.549
goes down as well? Like, where is it? It's not

00:17:29.549 --> 00:17:33.630
that kind of privacy. It's more like ownership

00:17:33.630 --> 00:17:38.430
and not being able to be, let's say, censored.

00:17:39.320 --> 00:17:42.380
And I don't mean censored in a bad way because

00:17:42.380 --> 00:17:47.019
none of us really talk anything that would be

00:17:47.019 --> 00:17:49.559
taken down. It's just Linux technical talk. But

00:17:49.559 --> 00:17:55.519
what I mean is you own your server and if...

00:17:55.849 --> 00:17:58.549
for whatever reason, the rest of the network

00:17:58.549 --> 00:18:00.670
isn't working, you have your own server working.

00:18:01.390 --> 00:18:05.089
If for whatever reason, you don't agree with

00:18:05.089 --> 00:18:07.690
the rules of the big matrix server, the one that's

00:18:07.690 --> 00:18:11.869
called matrix .org, then you're free to install

00:18:11.869 --> 00:18:15.730
your own and be your own boss. And at the same

00:18:15.730 --> 00:18:17.950
time, you can communicate with everyone else

00:18:17.950 --> 00:18:21.329
in the whole matrix network. So it's not like

00:18:21.329 --> 00:18:25.799
it's not like it's or IRC in terms of okay if

00:18:25.799 --> 00:18:28.819
you don't like libera chat rules okay you can

00:18:28.819 --> 00:18:32.299
make your own ird server but then people need

00:18:32.299 --> 00:18:35.859
to connect to your server in order to participate

00:18:35.859 --> 00:18:39.559
you know they're not connected while they're

00:18:39.559 --> 00:18:43.119
completely separate while with matrix it's all

00:18:43.119 --> 00:18:47.619
federated you know between each other so if discord

00:18:47.619 --> 00:18:51.809
one day decides hey i'm just gonna delete linkarsu's

00:18:51.809 --> 00:18:55.069
discord server it just goes away it just vanishes

00:18:55.069 --> 00:18:59.730
with matrix that wouldn't happen correct with

00:18:59.730 --> 00:19:04.089
matrix that can't happen uh if you have your

00:19:04.089 --> 00:19:08.410
own um if you're hosting with your own server

00:19:08.410 --> 00:19:13.140
if you're hosting on matrix org then you're a

00:19:13.140 --> 00:19:16.119
part of matrix .org rules just as you're a part

00:19:16.119 --> 00:19:20.119
of discord rules because that's their server

00:19:20.119 --> 00:19:23.660
and many people do have their accounts on the

00:19:23.660 --> 00:19:26.420
main matrix server which is as I said matrix

00:19:26.420 --> 00:19:32.180
.org but it's very like advisable to get your

00:19:32.180 --> 00:19:38.900
account somewhere else simply to spread the words

00:19:38.900 --> 00:19:43.519
of how federation should work. Okay. We have

00:19:43.519 --> 00:19:46.980
a super chat here by Tony. If you guys don't

00:19:46.980 --> 00:19:49.039
know who Tony is, he creates a lot of different

00:19:49.039 --> 00:19:52.220
Nix -related videos. Go and follow him. But it

00:19:52.220 --> 00:19:55.359
says here, what is Amdocs and how are they connected

00:19:55.359 --> 00:19:59.119
to Matrix? Do you know anything about that? I

00:19:59.119 --> 00:20:02.680
have no clue what Amdocs is. I could Google it

00:20:02.680 --> 00:20:07.819
up, but I don't know. Let's see if Tony sends

00:20:07.819 --> 00:20:09.819
another message there because I have no clue

00:20:09.819 --> 00:20:13.930
what he's talking about. Now, something else

00:20:13.930 --> 00:20:18.930
that you mentioned in that video that I was watching

00:20:18.930 --> 00:20:22.869
is you shouldn't use Discord because whatever

00:20:22.869 --> 00:20:25.529
information you post there is not searchable,

00:20:25.650 --> 00:20:28.289
right? On the web. Whatever you type in there

00:20:28.289 --> 00:20:30.950
is gone. If someone has a question, they cannot

00:20:30.950 --> 00:20:34.150
reach that information unless they join the server

00:20:34.150 --> 00:20:36.750
and search, and searching there sucks, right?

00:20:36.849 --> 00:20:40.869
So what do you recommend instead of Discord?

00:20:41.680 --> 00:20:45.240
I guess Matrix is the same issue if we talk about

00:20:45.240 --> 00:20:48.500
that specifically, right? So should we use forums?

00:20:49.119 --> 00:20:53.480
Well, I'm personally a fan of forums because

00:20:53.480 --> 00:20:56.859
they are designed for this specific use case

00:20:56.859 --> 00:21:01.140
where people discuss topics, help each other

00:21:01.140 --> 00:21:04.759
in solving problems and that stays online and

00:21:04.759 --> 00:21:08.660
it's searchable and indexable by search engines.

00:21:10.059 --> 00:21:13.420
It's basically designed for this specific purpose

00:21:13.420 --> 00:21:20.019
while the chat is just for chat. There is a way

00:21:20.019 --> 00:21:25.980
that you can put bots and other kinds of software

00:21:25.980 --> 00:21:30.700
on your matrix server in order to log the chat

00:21:30.700 --> 00:21:35.259
and make it publicized on your website or something

00:21:35.259 --> 00:21:38.299
like that. I have actually been considering that

00:21:38.299 --> 00:21:43.890
because My own space on Matrix has a couple of

00:21:43.890 --> 00:21:49.369
different channels. Have you joined my space

00:21:49.369 --> 00:21:53.849
on Matrix, just as a reference, so you can understand

00:21:53.849 --> 00:21:58.250
what I'm saying? Yep, I joined your lobby. And

00:21:58.250 --> 00:22:01.490
the lobby, I don't understand how it works quite

00:22:01.490 --> 00:22:04.349
well. So I can share your screen in case that

00:22:04.349 --> 00:22:07.660
you want to... Yeah, you can do that just so

00:22:07.660 --> 00:22:11.420
I can easily explain it. Okay, okay. You ready?

00:22:11.900 --> 00:22:14.220
Yeah, yeah. I'll switch to your screen then.

00:22:14.400 --> 00:22:18.119
Okay. What's the lobby? That's the one that I

00:22:18.119 --> 00:22:22.240
reached. Yeah, so on the left side you can see

00:22:22.240 --> 00:22:24.960
there are some icons that very much resemble

00:22:24.960 --> 00:22:28.019
what Discord servers are. These are called spaces

00:22:28.019 --> 00:22:33.009
on Matrix and in here they are not. anything

00:22:33.009 --> 00:22:37.869
else other than a place for bookmarks. So for

00:22:37.869 --> 00:22:41.170
example it says that my public space has 30 members

00:22:41.170 --> 00:22:44.349
but if you go to my lobby you will see that we

00:22:44.349 --> 00:22:47.210
have 69 members. So how is that possible that

00:22:47.210 --> 00:22:49.950
the number is not the same? It's simply because

00:22:49.950 --> 00:22:53.750
not everyone joined the main space because space

00:22:53.750 --> 00:22:58.250
is just bookmarks. and in these bookmarks, I

00:22:58.250 --> 00:23:01.650
like to call them that, we have a couple of different

00:23:01.650 --> 00:23:06.430
rooms and whichever room you join you will be

00:23:06.430 --> 00:23:09.089
able to participate in that. So if you go for

00:23:09.089 --> 00:23:13.150
example to lobby that's where most of the chat

00:23:13.150 --> 00:23:17.369
is going on. It's very casual and if you go to

00:23:17.369 --> 00:23:20.230
Linux room this is where the technical stuff

00:23:20.230 --> 00:23:23.769
is going on. We also have a new BSD room but

00:23:23.769 --> 00:23:27.970
it's the same type of the room and this one I

00:23:27.970 --> 00:23:33.269
was planning to install a logging mechanism.

00:23:33.880 --> 00:23:36.859
And I can do that because it's my server and

00:23:36.859 --> 00:23:42.000
I can reach whatever I want on my server, except

00:23:42.000 --> 00:23:46.220
for private messages of people. Because private

00:23:46.220 --> 00:23:49.579
messages of people, even on my server, they are

00:23:49.579 --> 00:23:52.339
all end -to -end encrypted. So I can't really

00:23:52.339 --> 00:23:58.059
do anything with those except host them physically.

00:23:58.220 --> 00:24:03.299
But I can't see what's in there. But in the public

00:24:03.299 --> 00:24:08.740
rooms, I can see the content and I could put

00:24:08.740 --> 00:24:12.299
it on my website so it would be searchable on

00:24:12.299 --> 00:24:15.259
my website. But I was also thinking about making

00:24:15.259 --> 00:24:20.299
a forum. That's a big investment in terms of

00:24:20.299 --> 00:24:29.849
moderation. It's still in thinking phase. Okay.

00:24:29.910 --> 00:24:32.470
And that is to preserve information, basically,

00:24:32.630 --> 00:24:34.509
right? That's what you want to... Yeah, because

00:24:34.509 --> 00:24:38.509
a lot of people tend to come and ask the very

00:24:38.509 --> 00:24:43.470
same questions. And it's not that people want

00:24:43.470 --> 00:24:46.430
to be rude or anything else like this has been

00:24:46.430 --> 00:24:50.769
asked like 100 times. It's more like... When

00:24:50.769 --> 00:24:54.470
you're in a good mood to answer questions, it

00:24:54.470 --> 00:24:57.430
gets tiring after a while if you answer the same

00:24:57.430 --> 00:25:00.950
one. So it definitely is a good thing both for

00:25:00.950 --> 00:25:04.650
people who want to help and for those who need

00:25:04.650 --> 00:25:08.990
to be helped that someone can link them. Here

00:25:08.990 --> 00:25:13.460
we go. This has been discussed here. feel free

00:25:13.460 --> 00:25:17.180
to read this and add more to it if you have.

00:25:17.539 --> 00:25:22.599
So these kinds of things are good to have searchable,

00:25:22.720 --> 00:25:29.579
sortable, and remembered. Yeah, it makes sense.

00:25:29.759 --> 00:25:31.980
What is that encrypted channel? Because there's

00:25:31.980 --> 00:25:35.279
a guy in your lobby that told me to join that

00:25:35.279 --> 00:25:37.779
encrypted channel that I had to verify the users,

00:25:37.900 --> 00:25:39.720
and I was like, I don't know what this guy is

00:25:39.720 --> 00:25:47.480
talking about. Kector is like that. He really

00:25:47.480 --> 00:25:51.900
likes this channel because on matrix you can

00:25:51.900 --> 00:25:57.099
specify public rooms to be not encrypted or encrypted.

00:25:57.440 --> 00:26:00.720
Pretty much every public room is not encrypted

00:26:00.720 --> 00:26:06.460
and what this means is that as the chat propagates

00:26:06.460 --> 00:26:09.400
across the federation of matrix servers every

00:26:09.400 --> 00:26:12.000
administrator of every instance can see all of

00:26:12.000 --> 00:26:14.160
the chats in these public rooms and this is totally

00:26:14.160 --> 00:26:16.720
fine because these are designed to be public

00:26:16.720 --> 00:26:22.259
rooms but you can make a public room encrypted

00:26:22.259 --> 00:26:26.740
and this means that every member in that room

00:26:26.740 --> 00:26:30.740
will need I mean, members don't do that, their

00:26:30.740 --> 00:26:33.859
applications, the matrix clients do that. But

00:26:33.859 --> 00:26:36.599
when you post in that room, your message gets

00:26:36.599 --> 00:26:40.220
end -to -end encrypted with the public key of

00:26:40.220 --> 00:26:44.460
every other participant in that room. So it's

00:26:44.460 --> 00:26:47.140
basically like end -to -end decrypted, or how

00:26:47.140 --> 00:26:50.500
do you call it? Well, if you have, let's say,

00:26:50.539 --> 00:26:54.740
Signal, the messaging client, and if you have

00:26:54.740 --> 00:26:59.250
more than... not just you and me chat, but like

00:26:59.250 --> 00:27:01.670
a group chat. It's still end -to -end encrypted,

00:27:01.990 --> 00:27:06.589
but keys are shared between us. So it's more

00:27:06.589 --> 00:27:11.970
like an experiment room than anything else. It

00:27:11.970 --> 00:27:15.990
doesn't serve any particular purpose other than

00:27:15.990 --> 00:27:20.410
testing how encryption works. And some of the

00:27:20.410 --> 00:27:24.880
members of my community like to... to test this

00:27:24.880 --> 00:27:28.759
but it's it's a bit it's a bit harder to use

00:27:28.759 --> 00:27:31.279
this room because people need to verify each

00:27:31.279 --> 00:27:34.799
other if they want super secure let's stop there

00:27:34.799 --> 00:27:38.240
okay let's stop there it's gonna get very complicated

00:27:38.240 --> 00:27:41.299
okay yeah yeah we talked about matrix you know

00:27:41.299 --> 00:27:43.539
probably do you mind or would you like sharing

00:27:43.539 --> 00:27:47.779
about you like your background studies um what

00:27:47.779 --> 00:27:50.319
do you work on or i don't i'm not sure if that's

00:27:50.319 --> 00:27:53.720
private Or if you want to talk about it or not.

00:27:54.759 --> 00:28:00.559
Well, I can try. And you will tell me if I need

00:28:00.559 --> 00:28:03.759
to speed up or slow down, whatever it feels good

00:28:03.759 --> 00:28:08.880
for your ears. I grew up with Amiga computer.

00:28:10.859 --> 00:28:14.000
That's the beginning of my childhood. I did have

00:28:14.000 --> 00:28:16.819
contact with Commodore 64, but I didn't have

00:28:16.819 --> 00:28:22.009
one. Actually, I have Amiga right here. but I

00:28:22.009 --> 00:28:25.509
really can't lift it right now because it's wired

00:28:25.509 --> 00:28:29.369
with a lot of stuff. I still play around with

00:28:29.369 --> 00:28:36.730
that thing and from there I went to PC in I don't

00:28:36.730 --> 00:28:40.750
know what year was it like maybe 95 or something

00:28:40.750 --> 00:28:45.980
and we didn't really have internet. at the time

00:28:45.980 --> 00:28:49.619
I mean we had internet but it was like you would

00:28:49.619 --> 00:28:54.019
pay for the minute of spending online so that

00:28:54.019 --> 00:28:57.960
wasn't always cheap so I would go to the university

00:28:57.960 --> 00:29:03.940
where you could access one main university server

00:29:03.940 --> 00:29:07.799
which everyone had access to it was a Unix server

00:29:09.009 --> 00:29:12.529
and you would get access to these small terminals.

00:29:12.750 --> 00:29:16.990
They were like very dumb terminals. What we take

00:29:16.990 --> 00:29:20.970
for granted on Linux today and Mac, what we call

00:29:20.970 --> 00:29:25.390
terminal emulator, you know, console xterm or

00:29:25.390 --> 00:29:28.789
whatever it's called on Mac, gnome terminal,

00:29:29.069 --> 00:29:34.009
this little window used to be an actual box,

00:29:34.210 --> 00:29:38.019
a hardware that wasn't doing anything else than

00:29:38.019 --> 00:29:42.259
connecting to the main server and we would go

00:29:42.259 --> 00:29:45.599
physically to the university we would like a

00:29:45.599 --> 00:29:47.980
lot of us would sit next to each other each one

00:29:47.980 --> 00:29:51.039
on their own terminal that was like 80 by 25

00:29:51.039 --> 00:29:56.740
characters and we would spend time on IRC chatting

00:29:56.740 --> 00:30:01.920
reading email with you know Pine and Matt maybe

00:30:01.920 --> 00:30:07.509
playing some games like Mud, multiple users,

00:30:07.710 --> 00:30:11.190
dungeons. That's a text game. If you think I'm

00:30:11.190 --> 00:30:13.170
going crazy, like how do you play games on a

00:30:13.170 --> 00:30:17.750
terminal? It was a text game. And that's how

00:30:17.750 --> 00:30:24.210
my internet chat age started. But also I wanted

00:30:24.210 --> 00:30:28.430
to have this thing at home. And some of the older

00:30:28.430 --> 00:30:32.730
guys told me, like, you could have your own Unix

00:30:32.730 --> 00:30:37.079
at home. and there is something similar that

00:30:37.079 --> 00:30:41.920
is like fresh but it's like very good replacement

00:30:41.920 --> 00:30:44.759
for unix it's called linux and you should try

00:30:44.759 --> 00:30:51.339
it out and at the same month i saw like a computer

00:30:51.339 --> 00:30:55.079
magazine on the kiosk I don't know how they call

00:30:55.079 --> 00:30:58.480
it in English. The place where they sell newspapers.

00:30:59.299 --> 00:31:02.619
And there was this computer magazine with a CD.

00:31:02.880 --> 00:31:07.619
And the big title on the CD was Linux. And I

00:31:07.619 --> 00:31:12.599
bought that one. And it was Debian 1 .3. I do

00:31:12.599 --> 00:31:17.059
remember that. And it was yellow. And my friend

00:31:17.059 --> 00:31:21.380
and I installed Debian 1 .3 on my computer at

00:31:21.380 --> 00:31:25.099
home. It took like two days. just to get the

00:31:25.099 --> 00:31:30.259
pointer on screen because it was, you know, you're

00:31:30.259 --> 00:31:35.019
new, nothing works automatically back in the

00:31:35.019 --> 00:31:40.500
day. No documentation. Well, you could use the

00:31:40.500 --> 00:31:43.339
manual, like the man command, but the thing is

00:31:43.339 --> 00:31:47.920
back then Linux was unable to automatically recognize

00:31:47.920 --> 00:31:51.710
your hardware. and even more so it was unable

00:31:51.710 --> 00:31:56.130
to automatically load drivers because no such

00:31:56.130 --> 00:32:01.930
mechanism existed. So the way that we would make

00:32:01.930 --> 00:32:07.710
our Linux functional back then, including that

00:32:07.710 --> 00:32:11.329
day when I started, was you would install it

00:32:11.329 --> 00:32:14.509
from the CD. On the CD you would get the source

00:32:14.509 --> 00:32:18.980
for the kernel, source you would unpack, and

00:32:18.980 --> 00:32:22.640
you would go to the kernel configuration and

00:32:22.640 --> 00:32:25.500
in the kernel configuration you would select

00:32:25.500 --> 00:32:29.819
which drivers do you need for your hardware so

00:32:29.819 --> 00:32:33.279
basically you would find your modem for the internet

00:32:33.279 --> 00:32:36.900
that was one of the most the important ones and

00:32:36.900 --> 00:32:40.079
you would recompile the kernel with the support

00:32:40.079 --> 00:32:44.579
for your modem make your kernel bootable reboot

00:32:44.579 --> 00:32:47.259
the computer and now you have functional modem

00:32:47.259 --> 00:32:49.859
and now you can go online and now you can download

00:32:49.859 --> 00:32:52.779
the latest kernel now you unpack the latest kernel

00:32:52.779 --> 00:32:56.980
because on cd you didn't get it and then you

00:32:56.980 --> 00:33:00.079
reconfigure once again with the support for your

00:33:00.079 --> 00:33:02.339
graphics card with the support for your sound

00:33:02.339 --> 00:33:05.720
card with the support for anything else you might

00:33:05.720 --> 00:33:09.460
have in your system and once that's all ready

00:33:09.460 --> 00:33:12.900
then you need to install the x server that was

00:33:12.900 --> 00:33:16.319
pretty much the procedure and when you got x

00:33:16.319 --> 00:33:18.740
server installed then you would need to understand

00:33:18.740 --> 00:33:23.700
what are the mode lines of your monitor so you

00:33:23.700 --> 00:33:28.700
could insert the frequency responses in your

00:33:28.700 --> 00:33:31.480
x configuration file if it doesn't work your

00:33:31.480 --> 00:33:34.220
picture doesn't show up if you got it right then

00:33:34.220 --> 00:33:37.299
you got it right it took a little bit of trial

00:33:37.299 --> 00:33:41.599
and error And after all that effort, like two

00:33:41.599 --> 00:33:45.579
days of effort, I got a great picture with a

00:33:45.579 --> 00:33:48.539
mouse pointer and nothing else. And then it was

00:33:48.539 --> 00:33:52.960
time for installing window managers and all of

00:33:52.960 --> 00:33:55.819
the applications. That was like the starting

00:33:55.819 --> 00:34:01.480
point after 48 hours. Regarding the box that

00:34:01.480 --> 00:34:04.200
you mentioned, the terminal that you physically

00:34:04.200 --> 00:34:06.380
had to use in the past, can you share a picture

00:34:06.380 --> 00:34:09.420
of that? If I share your screen so that I can

00:34:09.420 --> 00:34:14.380
understand how it was. I'm 37 right now. I don't

00:34:14.380 --> 00:34:16.500
know if you want to share your age or not. Yeah,

00:34:16.539 --> 00:34:20.559
I'm 44. Okay, yeah, I wasn't around. I was around

00:34:20.559 --> 00:34:23.900
when Windows 95, that's the one that I started

00:34:23.900 --> 00:34:27.800
with. I didn't go back that far, so I don't know.

00:34:28.380 --> 00:34:30.400
I cannot picture it. Let me know when you're

00:34:30.400 --> 00:34:32.320
ready and I'll switch to your screen. Yeah, you

00:34:32.320 --> 00:34:38.739
can do it right now. These are the guys. So let's

00:34:38.739 --> 00:34:41.920
take this one, for example. This one, oh, it's

00:34:41.920 --> 00:34:48.559
too big. No, now it's fine. So I think this one

00:34:48.559 --> 00:34:52.400
looks the most familiar to me. It even could

00:34:52.400 --> 00:34:58.559
be VT320. I think actually that's the one. that

00:34:58.559 --> 00:35:03.360
I used but I'm not 100 % sure. Basically you

00:35:03.360 --> 00:35:07.099
get the keyboard, you get the cathode ray tube,

00:35:07.340 --> 00:35:12.719
the CRT screen and the only brain that this has

00:35:12.719 --> 00:35:19.920
is basically a card that makes a connection to

00:35:19.920 --> 00:35:24.860
the server. The server is not on this machine

00:35:24.860 --> 00:35:27.539
at all. This is just... Absolutely not, yeah.

00:35:27.619 --> 00:35:30.840
The server is somewhere else. A huge server?

00:35:31.059 --> 00:35:35.539
Is it like a supercomputer or what? No, I think

00:35:35.539 --> 00:35:37.940
the one that we had on university, the one that

00:35:37.940 --> 00:35:46.239
we all used was SunSpark from, let's say, 1990.

00:35:46.460 --> 00:35:49.480
I'm just guessing. Spark Station. I think that's

00:35:49.480 --> 00:35:52.420
something like this. oh so that was the server

00:35:52.420 --> 00:35:55.699
and from that terminal you connected to it like

00:35:55.699 --> 00:35:59.099
the ssh or was a different protocol used back

00:35:59.099 --> 00:36:03.920
then or no no no no no it it wasn't ssh it wasn't

00:36:03.920 --> 00:36:06.860
uh telnet it was more like serial connection

00:36:06.860 --> 00:36:10.500
i think oh so you physically connected physically

00:36:10.500 --> 00:36:13.619
yeah with the serial cable to the server? Well,

00:36:13.760 --> 00:36:16.539
I wasn't the one who connected it. It was all

00:36:16.539 --> 00:36:19.599
pre -connected like bunch of terminals pre -connected

00:36:19.599 --> 00:36:25.199
to the server and the fun part was you could

00:36:25.199 --> 00:36:29.420
use a command on Unix called finger. This command

00:36:29.420 --> 00:36:33.960
was made obsolete after a while because it became

00:36:33.960 --> 00:36:37.440
a security problem but basically this command

00:36:37.440 --> 00:36:40.699
was pretty popular because it would tell you

00:36:40.699 --> 00:36:45.360
where oh i mean which terminal is certain user

00:36:45.360 --> 00:36:51.139
currently using so you could look up who is logged

00:36:51.139 --> 00:36:54.420
on onto server right now and where this user

00:36:54.420 --> 00:36:57.400
is sitting at the moment so you could physically

00:36:57.400 --> 00:37:00.679
go to that user because we all knew which terminal

00:37:00.679 --> 00:37:08.429
was which one oh okay okay i see so your terminal

00:37:08.429 --> 00:37:11.690
your physical box had a keyboard and it was basically

00:37:11.690 --> 00:37:15.050
an instance like an instance of a terminal as

00:37:15.050 --> 00:37:17.429
we know right now right each one would spawn

00:37:17.429 --> 00:37:20.809
their own instance of a terminal or something

00:37:20.809 --> 00:37:25.150
like that yeah basically what you see on my screen

00:37:25.150 --> 00:37:30.710
right now are two same things so this this is

00:37:30.710 --> 00:37:34.480
the same as this okay just a modern version of

00:37:34.480 --> 00:37:39.000
this okay and that's awesome that's awesome and

00:37:39.000 --> 00:37:41.260
what did you study did you study computer science

00:37:41.260 --> 00:37:46.320
or no i was very interested in in computers obviously

00:37:46.320 --> 00:37:48.659
but there was a lot of video games as well so

00:37:48.659 --> 00:37:54.139
that kind of took you know my my cpu time but

00:37:54.139 --> 00:38:01.280
basically i ended up in a How do you say it in

00:38:01.280 --> 00:38:04.280
English? You heard of Nikola Tesla, I'm sure.

00:38:04.420 --> 00:38:09.360
My technical school was called Nikola Tesla because

00:38:09.360 --> 00:38:17.280
the guy is from around here. And we learned electronics,

00:38:17.559 --> 00:38:22.179
basically. That's how I grew up to be, I suppose.

00:38:23.079 --> 00:38:26.639
But when it got time to start actually working,

00:38:26.900 --> 00:38:30.119
my first job was actually not with electronics,

00:38:30.440 --> 00:38:36.920
but as a system administrator of Linux. So it

00:38:36.920 --> 00:38:40.159
went into that direction pretty much. Okay. And

00:38:40.159 --> 00:38:42.639
what about the presence? What do you currently

00:38:42.639 --> 00:38:46.960
work on? Systems administrator? I don't know

00:38:46.960 --> 00:38:48.360
if you want to share that or keep it private.

00:38:49.099 --> 00:38:52.320
Iceblade in chat is correct. Much better translation

00:38:52.320 --> 00:38:58.320
than I did. But yeah, currently I do have...

00:38:58.320 --> 00:39:06.860
It's a mix of a lot of stuff. But it has a lot

00:39:06.860 --> 00:39:09.780
of system administration. It has a lot of networking

00:39:09.780 --> 00:39:16.039
administration. It has... applications layer

00:39:16.039 --> 00:39:21.800
and virtualization and there is a lot of linux

00:39:21.800 --> 00:39:26.440
mostly rocky linux not by my own choice it's

00:39:26.440 --> 00:39:31.619
more like it came with the job and um because

00:39:31.619 --> 00:39:34.480
probably they were in red hat and after the acquisition

00:39:34.480 --> 00:39:38.400
they moved to rocky or something the company

00:39:38.400 --> 00:39:46.449
whose software I use professionally used to make

00:39:46.449 --> 00:39:51.429
their software available only on CentOS. And

00:39:51.429 --> 00:39:56.230
CentOS was basically killed by Red Hat, the company.

00:39:56.489 --> 00:40:01.989
And the fun part is that you can't really kill

00:40:01.989 --> 00:40:05.570
open source free software. It's not possible.

00:40:05.769 --> 00:40:10.469
Because what CentOS was, it was basically a carbon

00:40:10.469 --> 00:40:14.489
copy of Red Hat Enterprise Linux, but a completely

00:40:14.489 --> 00:40:18.130
free version. So a lot of people used that instead

00:40:18.130 --> 00:40:21.710
of the paid version of Red Hat. And Red Hat didn't

00:40:21.710 --> 00:40:25.170
like that, so they bought the whole thing and

00:40:25.170 --> 00:40:29.440
then they killed it. It's now called CentOS Stream,

00:40:29.659 --> 00:40:32.280
but that's hardly the same as it used to be.

00:40:32.820 --> 00:40:36.059
So basically it's dead. The thing that used to

00:40:36.059 --> 00:40:41.139
be CentOS, that's dead. And the fun part is the

00:40:41.139 --> 00:40:48.860
guy who was very important in making CentOS,

00:40:49.019 --> 00:40:53.000
the same guy said basically... I cannot swear,

00:40:53.179 --> 00:40:58.260
but I would like to. He made Rocky Linux, and

00:40:58.260 --> 00:41:02.400
let's go again. You can swear. I think you can

00:41:02.400 --> 00:41:05.019
swear. What happens if we swear? I have done

00:41:05.019 --> 00:41:07.099
it in the past in my videos. Nothing has happened

00:41:07.099 --> 00:41:10.079
so far. You could get demonetized, so it's not

00:41:10.079 --> 00:41:13.360
a very good idea. Oh, okay, okay. I was around

00:41:13.360 --> 00:41:16.679
when... I don't remember the CentOS version,

00:41:16.860 --> 00:41:19.489
but... People upgraded to version, I don't remember

00:41:19.489 --> 00:41:23.230
exactly what version it was. So in theory, you

00:41:23.230 --> 00:41:25.730
had three years, four years, I don't remember.

00:41:26.010 --> 00:41:29.530
But then Red Hat decided to kill it like right

00:41:29.530 --> 00:41:32.170
away, right? So people were losing their minds

00:41:32.170 --> 00:41:35.750
and seeing to what or to which distro to migrate,

00:41:35.989 --> 00:41:40.449
right? That's when Rocky Linux came around. Is

00:41:40.449 --> 00:41:44.539
that right? Yeah, yeah. But, you know, can we

00:41:44.539 --> 00:41:46.739
switch to my screen again? I just want to be

00:41:46.739 --> 00:41:51.980
sure that I got it right. So, Wiki sent us...

00:41:51.980 --> 00:41:53.659
Let me know when you're ready and I'll switch

00:41:53.659 --> 00:41:58.260
to your screen. You can switch. I don't have

00:41:58.260 --> 00:42:02.920
anything on my screen that is not supposed to

00:42:02.920 --> 00:42:07.199
be seen. So, where is the founder? I don't remember

00:42:07.199 --> 00:42:11.289
names. so let's look it up once again the founder

00:42:11.289 --> 00:42:17.150
let's try to under okay one of the centos founder

00:42:17.150 --> 00:42:20.550
gregory uh created the competing rocky linux

00:42:20.550 --> 00:42:25.070
project yes so this uh you know uh the history

00:42:25.070 --> 00:42:30.150
repeats so redhead can buy and kill as much as

00:42:30.150 --> 00:42:32.369
they like but they really can't kill the free

00:42:32.369 --> 00:42:36.519
software no matter how they try So that's how

00:42:36.519 --> 00:42:39.099
things work and this is just awesome because

00:42:39.099 --> 00:42:46.380
one of my passions is... I'm not doing it out

00:42:46.380 --> 00:42:50.039
of spite for big tech, it's just that I love

00:42:50.039 --> 00:42:56.329
being a user of software. that is fully independent

00:42:56.329 --> 00:43:00.369
from big tech companies and basically it's mine.

00:43:00.530 --> 00:43:04.530
And when I say mine, it's not that I made it,

00:43:04.630 --> 00:43:08.329
it's mine in a way that this is my laptop and

00:43:08.329 --> 00:43:13.369
whatever is on my laptop basically does my bidding.

00:43:13.750 --> 00:43:18.210
My laptop does exactly what I want it to do because

00:43:18.210 --> 00:43:22.110
I am the one who has installed the software on

00:43:22.110 --> 00:43:26.719
it. starting from scratch by choosing the operating

00:43:26.719 --> 00:43:31.380
system, choosing the software and there is no

00:43:31.380 --> 00:43:34.019
telemetry, there is no company behind it, there

00:43:34.019 --> 00:43:36.860
is nothing. It's just open source free software

00:43:36.860 --> 00:43:41.659
and is absolutely mine to use as I please and

00:43:41.659 --> 00:43:49.619
this is quite liberating and this is not a dig

00:43:49.619 --> 00:43:56.360
at users who use Mac or Windows as prime examples

00:43:56.360 --> 00:44:01.780
of proprietary software. It's more like a finger

00:44:01.780 --> 00:44:06.219
towards these companies that they really can't

00:44:06.219 --> 00:44:12.579
have me as a user because I said so. That's what

00:44:12.579 --> 00:44:17.699
it comes down to. So I try as much as I can.

00:44:18.519 --> 00:44:24.119
with my channel on YouTube and PeerTube and Odyssey

00:44:24.119 --> 00:44:31.559
to help anyone who is interested in learning

00:44:31.559 --> 00:44:35.219
more about the alternatives. And it's always

00:44:35.219 --> 00:44:38.739
up to them, the users who come and watch my content,

00:44:38.860 --> 00:44:41.619
to decide on their own. I never tell them you

00:44:41.619 --> 00:44:44.860
have to switch to Linux. That's hardly productive.

00:44:45.869 --> 00:44:50.010
But if you come to my channel and ask for guidance

00:44:50.010 --> 00:44:53.690
or help or to my matrix chat or whatever, I will

00:44:53.690 --> 00:44:56.610
provide it because I love doing that. So if you're

00:44:56.610 --> 00:45:01.829
the one asking for help, I want to help. If you

00:45:01.829 --> 00:45:05.750
don't want help, then I don't want to be a part

00:45:05.750 --> 00:45:10.539
of... The group of people who you talk negatively

00:45:10.539 --> 00:45:13.699
about, you know, these guys trying to force me

00:45:13.699 --> 00:45:16.980
to do something that I don't want. You're a free

00:45:16.980 --> 00:45:20.840
person in a free world. You are absolutely free

00:45:20.840 --> 00:45:23.800
to choose if you want Windows, if you want Mac,

00:45:23.880 --> 00:45:26.400
if you want Linux, if you want BSD operating

00:45:26.400 --> 00:45:30.739
systems. Anything is at your disposal, you know.

00:45:30.880 --> 00:45:35.250
It's just that me personally, I... really enjoy

00:45:35.250 --> 00:45:40.409
using my computer in this way because I have

00:45:40.409 --> 00:45:43.190
a couple of Mac friends and I saw on your channel

00:45:43.190 --> 00:45:48.349
that yours is very customized and all my other

00:45:48.349 --> 00:45:52.889
friends just use it as is and they believe that

00:45:52.889 --> 00:45:57.260
Apple software should be used in the way that

00:45:57.260 --> 00:45:59.880
Apple has envisioned it and Apple knows best.

00:46:00.659 --> 00:46:04.519
I know it sounds funny, but it is their choice

00:46:04.519 --> 00:46:11.199
to make this decision. But then I tell them Today

00:46:11.199 --> 00:46:13.719
I have changed my window manager into something

00:46:13.719 --> 00:46:16.880
completely different from yesterday and I'm very

00:46:16.880 --> 00:46:20.500
much enjoying learning some new stuff that I

00:46:20.500 --> 00:46:23.800
can do with my desktop and I have placed these

00:46:23.800 --> 00:46:27.179
effects that make me happy. They are useless

00:46:27.179 --> 00:46:31.679
but they make me happy and they tell me like

00:46:31.679 --> 00:46:36.800
they kind of have a hard time sharing my happy

00:46:36.800 --> 00:46:40.619
feelings because they tell themselves that they

00:46:40.619 --> 00:46:43.300
don't need that. Oh, yeah. Yeah, yeah, yeah,

00:46:43.300 --> 00:46:46.599
yeah, yeah. Let me touch on that for a little

00:46:46.599 --> 00:46:48.719
while. I'm sorry to interrupt there. Yeah, yeah.

00:46:49.199 --> 00:46:53.039
I did use the Mac the way that Apple designed

00:46:53.039 --> 00:46:57.019
it, you know, no window manager. Well, there's

00:46:57.019 --> 00:47:00.199
a few basic window managers, right? You manage

00:47:00.199 --> 00:47:02.699
your windows, you put them in different desktops,

00:47:02.739 --> 00:47:05.679
you scroll with your magic mouse, you switch

00:47:05.679 --> 00:47:07.460
between desktops, and you think you're really

00:47:07.460 --> 00:47:11.179
effective. After installing a window manager

00:47:11.179 --> 00:47:14.360
in macOS, I realized that window managers are

00:47:14.360 --> 00:47:16.940
a must. And I use a window manager right now.

00:47:17.039 --> 00:47:19.679
There's not a lot in macOS, there's a few, but

00:47:19.679 --> 00:47:22.400
they make a whole difference. I keep a single

00:47:22.400 --> 00:47:25.480
application on the screen at a time, always in

00:47:25.480 --> 00:47:31.019
stack mode. i don't like default mac os i'm pretty

00:47:31.019 --> 00:47:34.780
ineffective i don't like binder i don't like

00:47:34.780 --> 00:47:37.780
that application at all but i'm i spend most

00:47:37.780 --> 00:47:40.119
of my day in the terminal maybe that's that's

00:47:40.119 --> 00:47:44.219
why i'm not sure but i don't like default mac

00:47:44.219 --> 00:47:49.260
os to be honest yeah well uh i do spend a lot

00:47:49.260 --> 00:47:52.980
of time in terminal as well and this is one of

00:47:52.980 --> 00:47:56.079
the reasons why the whole desktop environment

00:47:56.079 --> 00:48:00.860
doesn't make much of a difference to me but it

00:48:00.860 --> 00:48:04.860
kind of depends on what device I'm using because

00:48:04.860 --> 00:48:07.800
my laptop is you know the typical laptop size

00:48:07.800 --> 00:48:14.059
so on a 14 inch screen I prefer to have all my

00:48:14.059 --> 00:48:17.019
applications in full screen except maybe when

00:48:17.019 --> 00:48:20.659
I use two of them side by side and it's usually

00:48:20.659 --> 00:48:26.869
terminal or something but Let me give you a little

00:48:26.869 --> 00:48:31.070
bit of background which is not that far into

00:48:31.070 --> 00:48:36.610
my history. Basically, the first time I even

00:48:36.610 --> 00:48:41.949
got the desire to try tiling window managers

00:48:41.949 --> 00:48:46.110
is when Hyperland became a thing. Do you know

00:48:46.110 --> 00:48:49.079
about Hyperland? I have heard it a lot. I have

00:48:49.079 --> 00:48:50.920
interviewed a lot of people and they talk about

00:48:50.920 --> 00:48:54.880
Hyperland a lot. But I don't understand it because

00:48:54.880 --> 00:48:58.480
I'm not a Linux user. Well, it's very simple.

00:48:58.739 --> 00:49:02.139
You know how tiling window managers works. I

00:49:02.139 --> 00:49:05.639
use tiling. So basically you have manual tiling,

00:49:05.739 --> 00:49:08.039
you have automatic tiling, depending on which

00:49:08.039 --> 00:49:12.130
kind of window manager it is. Hyperland is an

00:49:12.130 --> 00:49:15.190
automatic tiling window manager that also happens

00:49:15.190 --> 00:49:20.889
to be very eye candy in terms of effects changing

00:49:20.889 --> 00:49:25.329
desktops like by default it slides around spawning

00:49:25.329 --> 00:49:31.230
windows appears into the maybe you can pull it

00:49:31.230 --> 00:49:36.010
out I think on Hyperland web page they have an

00:49:36.010 --> 00:49:40.719
animation that kind of demonstrates this. But

00:49:40.719 --> 00:49:43.900
it's pretty much eye candy and it was a lot of,

00:49:43.940 --> 00:49:46.760
yeah, somewhere here it should be. Yeah, that

00:49:46.760 --> 00:49:51.380
one. So that's actually a very old one and it's

00:49:51.380 --> 00:49:55.599
not that choppy. It was choppy like very, very

00:49:55.599 --> 00:49:59.519
long time ago, but now it's super smooth. And

00:49:59.519 --> 00:50:04.500
I got interested because it was hype. Let's be

00:50:04.500 --> 00:50:08.170
honest. And I tried it. Yeah, I tried it. I tried

00:50:08.170 --> 00:50:12.869
it, it kind of clicked with me and I used it

00:50:12.869 --> 00:50:15.210
for a while especially on a laptop because that's

00:50:15.210 --> 00:50:18.329
where it fits me more. I tried to use it on my

00:50:18.329 --> 00:50:22.690
desktop computer but on my desktop computer I'm

00:50:22.690 --> 00:50:27.150
having difficulties fitting my workflow into

00:50:27.150 --> 00:50:31.250
any kind of dialing mode and I'm still working

00:50:31.250 --> 00:50:35.000
on it. Thinking whether this could work for me

00:50:35.000 --> 00:50:37.880
or not on the big screen. And when I say big

00:50:37.880 --> 00:50:40.059
screen, I really mean it because my monitor is

00:50:40.059 --> 00:50:45.360
42 inch. So having just one application in full

00:50:45.360 --> 00:50:49.760
screen on like, which takes your entire eye view

00:50:49.760 --> 00:50:54.159
is a little bit stupid. So too much. Yeah. And

00:50:54.159 --> 00:50:58.239
by default, Hyperland, what it does is it puts

00:50:58.730 --> 00:51:01.650
either your application full screen or it splits

00:51:01.650 --> 00:51:04.929
it in half so you have right and left and already

00:51:04.929 --> 00:51:07.190
you have to go with your head left and right

00:51:07.190 --> 00:51:10.010
and usually my main content is in the middle

00:51:10.010 --> 00:51:12.590
of the screen and i just drag the stuff around

00:51:12.590 --> 00:51:17.869
which i don't need uh so yeah this is in mac

00:51:17.869 --> 00:51:20.409
os right yeah this is the window manager that

00:51:20.409 --> 00:51:24.869
i'm using on mac os but like you said the same

00:51:24.869 --> 00:51:29.460
thing i only use one one application, but I have

00:51:29.460 --> 00:51:32.780
a small screen. I have a 27 inch monitor because

00:51:32.780 --> 00:51:35.840
I used to have a 52 inch TV as a monitor. I switched

00:51:35.840 --> 00:51:39.119
to a 27 and I use full screen all the time. Yeah,

00:51:39.139 --> 00:51:44.739
it's decent for me. But for chat, for example,

00:51:44.880 --> 00:51:47.239
I use this one in tiling mode because I want

00:51:47.239 --> 00:51:50.380
to see all of them on the screen at a time. That's

00:51:50.380 --> 00:51:55.059
like actually the only case in which I use tiles.

00:51:55.199 --> 00:51:58.019
But other than that. I'm always in full screen,

00:51:58.179 --> 00:52:03.159
you know. Yeah, I get it. I like to have a lot

00:52:03.159 --> 00:52:06.039
of stuff in full screen. So for that reason,

00:52:06.139 --> 00:52:09.320
I have my chat on my second monitor, which is

00:52:09.320 --> 00:52:14.400
vertical. So right now I have like the two of

00:52:14.400 --> 00:52:17.460
us in the top part and the chat in the bottom

00:52:17.460 --> 00:52:21.280
part. And that works for me. while having my

00:52:21.280 --> 00:52:24.920
main screen completely free. That works for me

00:52:24.920 --> 00:52:27.360
even when I play video games. Sometimes I stream

00:52:27.360 --> 00:52:30.699
video games and I have to have a video game in

00:52:30.699 --> 00:52:33.420
full screen and I have to see the chat so that's

00:52:33.420 --> 00:52:36.119
on the other monitor. I just have to have two

00:52:36.119 --> 00:52:38.880
screens. It wouldn't work for me. I tried. I

00:52:38.880 --> 00:52:42.960
just can't function with just one because this

00:52:42.960 --> 00:52:48.889
extra screen gives me extra utility. It's just

00:52:48.889 --> 00:52:52.570
how it is. But with laptops, I don't really stream

00:52:52.570 --> 00:52:58.030
from a laptop. I don't actively create content

00:52:58.030 --> 00:53:02.769
on a laptop. Even when I do create a laptop content

00:53:02.769 --> 00:53:06.469
and I do a lot of that, I just plug in the laptop

00:53:06.469 --> 00:53:09.989
via HDMI into the capture card on the main PC.

00:53:12.030 --> 00:53:15.010
still create content on the main PC while the

00:53:15.010 --> 00:53:20.130
capture card is just receiving the HDMI out from

00:53:20.130 --> 00:53:23.409
the laptop. Because I have a lot of content where

00:53:23.409 --> 00:53:28.369
I reinstall Linux from scratch and people like

00:53:28.369 --> 00:53:31.550
to see how it boots up. They like to see me entering

00:53:31.550 --> 00:53:35.489
the BIOS settings. You can't really do that any

00:53:35.489 --> 00:53:39.650
other way other than having two computers. So

00:53:39.650 --> 00:53:44.099
that's how I do that. I kind of got lost how

00:53:44.099 --> 00:53:47.199
we even got to this topic. You asked about, yeah,

00:53:47.280 --> 00:53:50.460
you asked about, we got to Hyperland somehow,

00:53:50.659 --> 00:53:52.940
but I don't know how. It doesn't matter. But

00:53:52.940 --> 00:53:56.099
you touched a point and I have questions about

00:53:56.099 --> 00:54:00.760
something you mentioned. So is Hyperland, is

00:54:00.760 --> 00:54:06.639
the word Hyperland hype then? So is that why

00:54:06.639 --> 00:54:10.929
Hyperland has the hype? word in it because hyperlent

00:54:10.929 --> 00:54:14.150
is hype or not what are your thoughts as far

00:54:14.150 --> 00:54:18.989
as as far as i know uh the guy who made hyperlent

00:54:18.989 --> 00:54:23.849
first made a window manager called hyper with

00:54:23.849 --> 00:54:30.929
the r and in the end and then he learned about

00:54:30.929 --> 00:54:34.570
wayland protocol and then he made a different

00:54:34.570 --> 00:54:38.219
version of hyper that works on Wayland and just

00:54:38.219 --> 00:54:42.579
added the other part that's like a combination

00:54:42.579 --> 00:54:45.320
of Hyper and Wayland which is now Hyperland.

00:54:46.900 --> 00:54:50.739
As far as I know this is the correct order of

00:54:50.739 --> 00:54:53.219
how things happened with him, with the developer.

00:54:56.099 --> 00:54:59.820
So I don't think it has anything to do with hype.

00:54:59.920 --> 00:55:02.320
It's just a guy who made his own window manager

00:55:02.320 --> 00:55:09.679
because he wanted and It did good. Okay. What

00:55:09.679 --> 00:55:11.880
do you use? Because I'm not a Linux user, but

00:55:11.880 --> 00:55:14.380
I hear that people talk about Hyperland and the

00:55:14.380 --> 00:55:18.320
other one is X11, Xorg. I don't know. No, the

00:55:18.320 --> 00:55:25.559
Xorg is the underlying software on pretty much

00:55:25.559 --> 00:55:30.480
every Unix and Linux up until pretty much today.

00:55:31.530 --> 00:55:36.369
And Wayland is, well, Xorg is a server which

00:55:36.369 --> 00:55:42.030
does a lot of things before window managers or

00:55:42.030 --> 00:55:46.869
desktop environments even come to be. And they

00:55:46.869 --> 00:55:49.289
manage your screen, they manage your drivers

00:55:49.289 --> 00:55:51.690
and stuff like that. And then the window manager

00:55:51.690 --> 00:56:00.079
just sits on top of the, let's say, display server

00:56:00.079 --> 00:56:04.320
right and what they did it kind of became too

00:56:04.320 --> 00:56:07.820
complicated I suppose to maintain I'm not a maintainer

00:56:07.820 --> 00:56:10.380
or developer so I just take it for granted what

00:56:10.380 --> 00:56:14.820
they say but they said at one point like 10 plus

00:56:14.820 --> 00:56:17.880
years ago that it's no longer a viable solution

00:56:17.880 --> 00:56:21.900
for further development so it slowed down and

00:56:21.900 --> 00:56:24.139
they started doing something new called Wayland

00:56:24.139 --> 00:56:29.829
and Wayland is not a server Because X display

00:56:29.829 --> 00:56:33.369
server is something tangible like an executable

00:56:33.369 --> 00:56:36.289
software that actually runs on your computer.

00:56:36.570 --> 00:56:40.469
While Wayland being a replacement for this software

00:56:40.469 --> 00:56:46.809
is not software at all. It's just a PDF. It's

00:56:46.809 --> 00:56:51.809
just a bunch of rules that everyone who makes

00:56:51.809 --> 00:56:56.309
a window manager now has to implement. a display

00:56:56.309 --> 00:57:01.369
server from scratch on their own by following

00:57:01.369 --> 00:57:04.710
these rules so everyone who makes Wayland window

00:57:04.710 --> 00:57:10.170
managers should be compliant with the Wayland

00:57:10.170 --> 00:57:13.150
protocol in order for the applications to be

00:57:14.030 --> 00:57:17.530
compatible whether you use them on Hyperland.

00:57:17.610 --> 00:57:21.289
Hyperland works in Wayland mode. Whether you

00:57:21.289 --> 00:57:24.969
use KDE desktop environment which can work both

00:57:24.969 --> 00:57:28.949
on X server and in Wayland mode. Then you have

00:57:28.949 --> 00:57:31.610
GNOME desktop environment also very popular one

00:57:31.610 --> 00:57:36.130
which can work on X server but lately they are

00:57:36.130 --> 00:57:39.369
starting to cut that off and they are now fully

00:57:39.369 --> 00:57:43.739
into the Wayland mode. And then you have a lot

00:57:43.739 --> 00:57:45.840
of other window managers that you can still use

00:57:45.840 --> 00:57:51.719
on X server. But Wayland is basically just a

00:57:51.719 --> 00:57:54.739
protocol that other programmers need to implement

00:57:54.739 --> 00:57:58.199
for themselves. I'm not sure if I explained it

00:57:58.199 --> 00:58:04.659
very well for everyone, but if you have some

00:58:04.659 --> 00:58:07.599
sub questions to guide me to give you a better

00:58:07.599 --> 00:58:11.190
answer, I will. Okay. And what do you use personally?

00:58:11.309 --> 00:58:13.570
Because one of the main topics or one of the

00:58:13.570 --> 00:58:16.269
main reasons why I wanted to interview you is

00:58:16.269 --> 00:58:21.289
because you switched from Debian to Arch, but

00:58:21.289 --> 00:58:25.090
then you switched back from Arch to Debian. So

00:58:25.090 --> 00:58:27.570
what do you currently use at the moment? Do you

00:58:27.570 --> 00:58:29.690
use, I don't know, what do you use, Wayland?

00:58:29.789 --> 00:58:35.630
Do you use X or? I use Debian as an operating

00:58:35.630 --> 00:58:42.000
system, the stable one. and on it I have KDE

00:58:42.000 --> 00:58:47.340
Plasma as a desktop environment into which I

00:58:47.340 --> 00:58:52.780
log in in Wayland mode and this is now the default

00:58:52.780 --> 00:58:55.739
so if you don't really configure anything you

00:58:55.739 --> 00:58:59.760
will end up in KDE in this Wayland mode and what

00:58:59.760 --> 00:59:04.710
Wayland brings as some good things compared to

00:59:04.710 --> 00:59:07.929
the old X server. For example, you can change

00:59:07.929 --> 00:59:13.849
the resolution dynamically. It's not that X server

00:59:13.849 --> 00:59:16.670
cannot do that, but there are a lot of bad implementations

00:59:16.670 --> 00:59:22.650
of this. So often you would have to log out when

00:59:22.650 --> 00:59:25.190
you would change the resolution or maybe not

00:59:25.190 --> 00:59:27.809
the resolution, but when you change the DPI scaling

00:59:27.809 --> 00:59:30.829
in KDE, you would have to log out and log back

00:59:30.829 --> 00:59:34.340
in to see the changes. So in the Wayland implementation

00:59:34.340 --> 00:59:36.920
of KDE you can now do that fully dynamically.

00:59:37.400 --> 00:59:40.440
So that's nice. Also you can have two different

00:59:40.440 --> 00:59:44.159
or more monitors with different DPI scaling.

00:59:44.940 --> 00:59:49.659
So I have here a normal low resolution monitor

00:59:49.659 --> 00:59:54.059
which I keep at 100%. resolution. But the 4K

00:59:54.059 --> 00:59:57.920
one is too tiny if I keep it at 100%. I just

00:59:57.920 --> 01:00:02.539
can't see the text. So I keep that one at 125%.

01:00:02.539 --> 01:00:08.579
You can't do that on KDE in X11 mode. It's just

01:00:08.579 --> 01:00:12.940
not implemented. You can do that on Wayland.

01:00:13.059 --> 01:00:16.739
So it's kind of going there towards the future.

01:00:16.840 --> 01:00:21.280
If you don't care about some of these little

01:00:23.320 --> 01:00:26.900
improvements in Wayland, then there is a good

01:00:26.900 --> 01:00:30.099
chance that X server might still be a better

01:00:30.099 --> 01:00:32.480
option for you because Wayland has drawbacks

01:00:32.480 --> 01:00:36.920
as well. So it's not like all, you know, shiny

01:00:36.920 --> 01:00:41.480
rainbows, right? Because I'm just gonna draw

01:00:41.480 --> 01:00:48.800
another parallel. I grew up with a certain functionality

01:00:48.800 --> 01:00:55.900
that I used back in 1995 all the way up until

01:00:55.900 --> 01:01:01.340
today and the X server is basically a networking

01:01:01.340 --> 01:01:04.760
protocol underneath the X server there is a lot

01:01:04.760 --> 01:01:09.840
of networking code and it's very very easy to

01:01:09.840 --> 01:01:15.780
use your computer use SSH in your terminal on

01:01:15.780 --> 01:01:19.840
your computer to log into a remote server and

01:01:19.840 --> 01:01:22.619
just type one command which is export display

01:01:22.619 --> 01:01:27.119
to tell the remote server that the next command

01:01:27.119 --> 01:01:30.440
that you're going to run in the ssh session should

01:01:30.440 --> 01:01:36.880
open on your own computer so you log into a server

01:01:36.880 --> 01:01:41.530
whatever elsewhere you start firefox on the server,

01:01:41.630 --> 01:01:44.269
but Firefox loads up on your screen locally.

01:01:44.429 --> 01:01:47.349
And it works like it's completely locally. It

01:01:47.349 --> 01:01:53.789
is restricted how responsive it is, how fast

01:01:53.789 --> 01:01:57.250
your networking works. But other than that, it

01:01:57.250 --> 01:02:03.179
just feels like it's local. And I got used to

01:02:03.179 --> 01:02:06.840
doing these things, you know, I would, as I said,

01:02:06.860 --> 01:02:09.500
I'm not a programmer, but I keep trying to learn

01:02:09.500 --> 01:02:13.059
and I will keep trying to learn. And often I

01:02:13.059 --> 01:02:17.480
would go to the remote session where my server

01:02:17.480 --> 01:02:21.119
is and some of my programming stuff. And I would

01:02:21.119 --> 01:02:27.059
run X emacs on the server, but it would display

01:02:27.059 --> 01:02:30.840
locally on my computer. Why this matters is because

01:02:30.840 --> 01:02:33.500
I can just disconnect and reconnect from another

01:02:33.500 --> 01:02:37.159
computer to the same session just as you can

01:02:37.159 --> 01:02:40.300
do with the normal text mode when you SSH somewhere

01:02:40.300 --> 01:02:44.880
and use screen or TMAX you can just resume that

01:02:44.880 --> 01:02:49.260
session from wherever if you have run the terminal

01:02:49.260 --> 01:02:53.099
multiplexer on the server, right? So the same

01:02:53.099 --> 01:02:59.199
way you can just run your graphical GUI applications

01:02:59.199 --> 01:03:02.019
on the remote server, but they display locally.

01:03:02.860 --> 01:03:07.360
And you do this through X, right? Yeah, X server

01:03:07.360 --> 01:03:13.260
is what makes this possible natively. Wayland

01:03:13.260 --> 01:03:16.340
technically doesn't have this functionality.

01:03:16.460 --> 01:03:19.099
It's not even designed to do something like that.

01:03:20.090 --> 01:03:23.530
But then someone else came up with an idea to

01:03:23.530 --> 01:03:27.030
try to re -implement this and I made a video

01:03:27.030 --> 01:03:31.429
about that. It's called Waypipe. It's a software

01:03:31.429 --> 01:03:33.849
that you need to install on your local computer

01:03:33.849 --> 01:03:36.829
and on the server or whatever the remote computer

01:03:36.829 --> 01:03:40.570
is. And then you can get pretty much the same

01:03:40.570 --> 01:03:44.730
functionality, but it's not natively implemented.

01:03:44.949 --> 01:03:49.880
You'd have to... install it if you are not an

01:03:49.880 --> 01:03:52.960
administrator on the remote server you might

01:03:52.960 --> 01:03:58.340
have problems getting that functionality so and

01:03:58.340 --> 01:04:01.059
this is useful for you because you don't depend

01:04:01.059 --> 01:04:03.800
on your ssh connection right so if your connection

01:04:03.800 --> 01:04:07.280
drops it the session remains on the server yes

01:04:07.280 --> 01:04:09.980
the session remains on the server and i can just

01:04:09.980 --> 01:04:13.420
reconnect or even for example if i'm working

01:04:13.960 --> 01:04:19.300
on my desktop computer. I still don't, usually

01:04:19.300 --> 01:04:23.380
it's when I practice coding. I do it from my

01:04:23.380 --> 01:04:25.260
desktop computer because I feel like sitting

01:04:25.260 --> 01:04:30.599
here. And at one point I want to move to the

01:04:30.599 --> 01:04:33.139
living room because I don't really use my laptop

01:04:33.139 --> 01:04:35.840
actively. I use my desktop computer. And when

01:04:35.840 --> 01:04:38.980
I want to move to the living room, I just leave

01:04:38.980 --> 01:04:42.360
everything as is, open my laptop and reconnect

01:04:42.360 --> 01:04:47.019
and just hijack my server connection and you

01:04:47.019 --> 01:04:49.360
know it reroutes to the laptop and basically

01:04:49.360 --> 01:04:52.920
it disappears on on my desktop computer it works

01:04:52.920 --> 01:04:56.420
very similarly to how t -max feels what are your

01:04:56.420 --> 01:04:58.579
thoughts on t -max that was gonna be my next

01:04:58.579 --> 01:05:01.699
question do you use t -max yeah it's it's good

01:05:01.699 --> 01:05:06.619
uh i used to use screen back when I didn't GNU

01:05:06.619 --> 01:05:10.579
screen or GNU back when I didn't know about TMAX

01:05:10.579 --> 01:05:13.219
and by default TMAX looks a little bit nicer

01:05:13.219 --> 01:05:16.340
with the bar on the on the bottom and with the

01:05:16.340 --> 01:05:19.920
tabs visible because I usually have more tabs

01:05:19.920 --> 01:05:24.639
like one for for my main screen for programming

01:05:24.639 --> 01:05:28.599
another one for the checking out my code compiling

01:05:28.599 --> 01:05:34.590
a third one for earth chat usually it just runs

01:05:34.590 --> 01:05:39.349
in that same t -max session so i can just move

01:05:39.349 --> 01:05:43.809
between at least those three and i just don't

01:05:43.809 --> 01:05:47.110
care when it detaches or whatever i can just

01:05:47.110 --> 01:05:51.670
reattach it for example i don't know i lie down

01:05:51.670 --> 01:05:54.630
in bed and go to sleep and someone told me that

01:05:54.630 --> 01:05:57.010
i don't know i should check out something on

01:05:57.010 --> 01:06:00.989
irc i don't have irc software on my phone but

01:06:00.989 --> 01:06:05.369
i do have ssh program on my phone so i just from

01:06:05.369 --> 01:06:10.469
the bed i ssh into my server and tmax attach

01:06:10.469 --> 01:06:14.829
and i see my chat session there because it's

01:06:14.829 --> 01:06:21.130
still running i like these little i i'm not even

01:06:21.130 --> 01:06:25.289
sure if if i should call them hacks because it

01:06:25.289 --> 01:06:27.889
they really don't feel like any kind of hacking

01:06:27.889 --> 01:06:31.829
it's just the way how I'm used to using Unix

01:06:31.829 --> 01:06:37.530
and Linux. But for some people, it might feel

01:06:37.530 --> 01:06:43.250
a little bit intimidating. Now, regarding the

01:06:43.250 --> 01:06:46.090
other question that I had, right? I watched the

01:06:46.090 --> 01:06:51.530
video from Arch to Debian, right? So would you

01:06:51.530 --> 01:06:55.269
mind sharing with the audience why the switch

01:06:55.269 --> 01:06:58.230
back from Arch to Debian? What happened there?

01:07:01.650 --> 01:07:06.090
I used Debian for a long time and I'm really

01:07:06.090 --> 01:07:12.889
comfortable in using Debian. And I used Ubuntu

01:07:12.889 --> 01:07:15.730
for a while. That one feels pretty much the same.

01:07:16.030 --> 01:07:20.090
I tried to use a couple others like derivatives

01:07:20.090 --> 01:07:24.030
of Debian. Ubuntu is pretty much based on Debian,

01:07:24.130 --> 01:07:30.920
so that's what I meant. But At some point, I

01:07:30.920 --> 01:07:33.460
think it was pretty much when I started doing

01:07:33.460 --> 01:07:38.099
my YouTube channel, I had the need to show off

01:07:38.099 --> 01:07:42.219
a lot of new stuff. Because how else can I demonstrate

01:07:42.219 --> 01:07:46.000
something new to the audience if I cannot easily

01:07:46.000 --> 01:07:49.739
get it on my computer? And Debian is a stable

01:07:49.739 --> 01:07:53.519
distribution by default, which means that you

01:07:53.519 --> 01:07:58.420
get new software once in two years. pretty much

01:07:58.420 --> 01:08:02.800
stays on this version of software you can use

01:08:02.800 --> 01:08:07.900
a system called flatpaks which is a relatively

01:08:07.900 --> 01:08:14.360
new thing on linux which feels like another distribution

01:08:14.360 --> 01:08:19.220
of linux put on top of yours so it feels like

01:08:19.220 --> 01:08:22.739
running i don't know a google play store and

01:08:22.739 --> 01:08:25.750
just fetching some applications from somewhere

01:08:25.750 --> 01:08:29.050
else not from debian but they do kind of get

01:08:29.050 --> 01:08:32.270
installed on your debian so in that way you can

01:08:32.270 --> 01:08:39.909
get latest desktop software for a static stable

01:08:39.909 --> 01:08:43.850
distribution such as debian which is really practical

01:08:43.850 --> 01:08:48.310
but i can't show to the people the new version

01:08:48.310 --> 01:08:52.029
of KDE desktop environment because it just says

01:08:52.029 --> 01:08:56.000
that the same version until I switch to the next

01:08:56.000 --> 01:08:59.460
version of Debian in two years because these

01:08:59.460 --> 01:09:04.439
Flatpaks, this Flatpak delivery system for software

01:09:04.439 --> 01:09:07.659
is just for desktop applications and basically

01:09:07.659 --> 01:09:09.819
nothing else. So you can't really change system

01:09:09.819 --> 01:09:14.859
software with that. Arch Linux on the other hand

01:09:14.859 --> 01:09:19.060
is a rolling Linux distribution which means that

01:09:19.060 --> 01:09:24.449
they don't have releases. Or should I say they

01:09:24.449 --> 01:09:29.449
have a new release every day? Either way you

01:09:29.449 --> 01:09:31.949
want it both should be correct because every

01:09:31.949 --> 01:09:36.430
day you can just run a system update and you

01:09:36.430 --> 01:09:39.970
can expect like 50 updates every day. It's pretty

01:09:39.970 --> 01:09:42.250
normal. If you don't update for a week you will

01:09:42.250 --> 01:09:45.210
get 300 updates. It's perfectly normal on Arch

01:09:45.210 --> 01:09:50.109
Linux because everything new that comes out takes

01:09:50.109 --> 01:09:55.670
very little time to show up in Arch packages

01:09:55.670 --> 01:09:59.430
repository. Let's say two days. Something new

01:09:59.430 --> 01:10:03.010
comes out, it goes to the testing phase and in

01:10:03.010 --> 01:10:06.329
two days it's already considered stable enough

01:10:06.329 --> 01:10:12.109
for the end user. Comparably to that, Debian

01:10:12.109 --> 01:10:18.140
starts freezing their package versions roughly

01:10:18.140 --> 01:10:22.060
half a year before release so their testing phase

01:10:22.060 --> 01:10:27.060
is not two days it's 180 days until they are

01:10:27.060 --> 01:10:30.600
satisfied with the end result and then they say

01:10:30.600 --> 01:10:34.739
this is now ready for the consumer and in two

01:10:34.739 --> 01:10:38.260
years time you'll get new stuff this is good

01:10:38.260 --> 01:10:41.439
and bad at the same time I can and will elaborate

01:10:41.439 --> 01:10:47.770
but I'm on arch at the moment so I really thought

01:10:47.770 --> 01:10:51.250
that Arch should be the perfect distribution

01:10:51.250 --> 01:10:54.369
for my needs at the time which is giving me the

01:10:54.369 --> 01:10:57.869
latest software. And for a time it really felt

01:10:57.869 --> 01:11:02.590
like I did a really good decision because contrary

01:11:02.590 --> 01:11:07.090
to the popular belief or to the marketing of

01:11:07.090 --> 01:11:10.590
many Arch users, Arch is actually very easy to

01:11:10.590 --> 01:11:15.010
use. If you are capable of reading text on the

01:11:15.010 --> 01:11:19.310
screen you will definitely be able to go to Arch

01:11:19.310 --> 01:11:22.090
Wiki which is absolutely awesome and I mean it

01:11:22.090 --> 01:11:27.489
like I truly mean it. You can install Arch Linux

01:11:27.489 --> 01:11:30.090
even if you don't know anything about Linux.

01:11:30.289 --> 01:11:34.369
You only need to be able to read what the Arch

01:11:34.369 --> 01:11:37.210
Wiki tells you and it tells you pretty much everything

01:11:37.210 --> 01:11:42.430
you need to type in order to get the system working

01:11:42.430 --> 01:11:46.729
and once you get it working all of the defaults

01:11:46.729 --> 01:11:51.510
kind of just work. For example, if you want KDE

01:11:51.510 --> 01:11:53.489
desktop environment, which is the one that I

01:11:53.489 --> 01:11:58.109
like, you just fetch the package from Arch servers,

01:11:58.369 --> 01:12:04.050
which is like the main package for KDE, and this

01:12:04.050 --> 01:12:07.710
package will automatically pull everything that

01:12:07.710 --> 01:12:14.699
it depends on, including all of the drivers and

01:12:14.699 --> 01:12:21.479
software and everything that it needs to be pulled

01:12:21.479 --> 01:12:23.960
it will pull automatically so you just wait a

01:12:23.960 --> 01:12:26.439
couple of minutes after you run one command and

01:12:26.439 --> 01:12:29.659
you get a lot of stuff working out of the box

01:12:29.659 --> 01:12:33.220
and when you need something else you just fetch

01:12:33.220 --> 01:12:38.600
it if they have it in their repository. Funny

01:12:38.600 --> 01:12:43.159
enough Debian has about six to seven times more

01:12:43.159 --> 01:12:48.319
software than Arch in the repository but it depends

01:12:48.319 --> 01:12:52.119
on what your priorities are to have more software

01:12:52.119 --> 01:12:56.880
or to have the latest software which is something

01:12:56.880 --> 01:13:02.000
that Arch Linux fixes with the community effort

01:13:02.000 --> 01:13:06.859
called AUR that is Arch User Repository and what

01:13:06.859 --> 01:13:11.430
Arch User Repository is It's a gazillion of packages

01:13:11.430 --> 01:13:16.069
uploaded by anyone, literally. So I could upload

01:13:16.069 --> 01:13:19.489
malware there if I wanted? You can and people

01:13:19.489 --> 01:13:23.930
do that. You can type on the search engine Arch

01:13:23.930 --> 01:13:27.470
Linux malware and you will find at least three

01:13:27.470 --> 01:13:31.250
this year that happened, maybe more. They do

01:13:31.250 --> 01:13:34.869
take it down fairly quickly. So I'm not saying

01:13:34.869 --> 01:13:39.119
that they don't monitor it, but... the fact that

01:13:39.119 --> 01:13:44.239
anyone can upload is a certain problem on its

01:13:44.239 --> 01:13:49.199
own depending on how you want to use your computer

01:13:49.199 --> 01:13:52.479
and what do you expect from it. I am one of those

01:13:52.479 --> 01:13:59.060
people who puts effort into trusting the source

01:13:59.060 --> 01:14:05.300
of the package that I have installed and you

01:14:05.300 --> 01:14:09.130
can As I said, Arch user repository is great

01:14:09.130 --> 01:14:12.170
in terms of it provides everything that exists

01:14:12.170 --> 01:14:15.850
in the universe of Linux. Good or bad, right?

01:14:16.149 --> 01:14:21.310
Yeah, they have everything. And for example,

01:14:21.310 --> 01:14:24.750
you need this thing and you will most probably

01:14:24.750 --> 01:14:28.229
find this thing on Arch user repository. And

01:14:28.229 --> 01:14:32.229
you can look at the source code of the script

01:14:32.229 --> 01:14:37.220
that installs this thing for you and you can

01:14:37.220 --> 01:14:39.380
decide, okay, this doesn't do anything malicious.

01:14:39.619 --> 01:14:42.239
I understand this code. I will install it. However,

01:14:42.420 --> 01:14:49.319
this script will pull like 10 other scripts as

01:14:49.319 --> 01:14:52.560
dependencies from our choose repository that

01:14:52.560 --> 01:14:56.699
are uploaded by 10 other random people and many

01:14:56.699 --> 01:15:00.289
of these will pull other dependencies from more

01:15:00.289 --> 01:15:02.850
random people. I just don't have that much time

01:15:02.850 --> 01:15:06.869
to read that many scripts in order to satisfy

01:15:06.869 --> 01:15:14.850
my own sense of safety. The first time that I

01:15:14.850 --> 01:15:17.170
pulled something from Arch user repository was

01:15:17.170 --> 01:15:21.189
day one when I installed Arch. And then I thought,

01:15:21.329 --> 01:15:26.199
what did I just do? I don't know. Let's reinstall

01:15:26.199 --> 01:15:29.619
the operating system because I have no... It's

01:15:29.619 --> 01:15:32.159
not that I broke anything. It's just that I don't

01:15:32.159 --> 01:15:33.560
know what I just pulled. You didn't trust it.

01:15:33.680 --> 01:15:36.699
Yeah. And then I reinstalled the whole system

01:15:36.699 --> 01:15:40.579
and then I decided it was still day one. Then

01:15:40.579 --> 01:15:43.699
I just decided our user repository is something

01:15:43.699 --> 01:15:46.439
that I will never touch in my entire life. It's

01:15:46.439 --> 01:15:49.880
just... I will not spit on it in terms of, you

01:15:49.880 --> 01:15:52.020
know, this is bad, don't use it. It's just that

01:15:52.020 --> 01:15:56.479
I... will not use it it's not for me please don't

01:15:56.479 --> 01:15:59.840
force me to use it but then again in the arch

01:15:59.840 --> 01:16:04.199
community it's considered a bit weird if you

01:16:04.199 --> 01:16:08.359
don't use arch user repository because if you

01:16:08.359 --> 01:16:11.020
don't use arch user repository then why are you

01:16:11.020 --> 01:16:15.720
using arch and that's when it hit me like really

01:16:15.720 --> 01:16:20.520
why am i using arch i guess it's because of all

01:16:20.520 --> 01:16:25.779
of the other stuff that That's refreshed often,

01:16:25.939 --> 01:16:29.260
which is desktop environment. Like I can't get

01:16:29.260 --> 01:16:32.960
that on Debian, the new versions. What else do

01:16:32.960 --> 01:16:36.439
I get from Arch? Well, not much actually. That's

01:16:36.439 --> 01:16:39.340
when I started thinking about why am I using

01:16:39.340 --> 01:16:43.180
Arch Linux? And then I had some troubles. For

01:16:43.180 --> 01:16:46.239
example, I'm going to try to summarize it, but

01:16:46.239 --> 01:16:51.869
do you know SDL library? No. It's a very popular

01:16:51.869 --> 01:16:57.930
library that gives a hand to the developer to

01:16:57.930 --> 01:17:02.869
access sound cards, joysticks, keyboards, inputs,

01:17:03.109 --> 01:17:09.270
I don't know. It's a useful library and my favorite

01:17:09.270 --> 01:17:16.930
video editor uses this library version 2 in order

01:17:16.930 --> 01:17:21.239
to function. And it works and I installed its

01:17:21.239 --> 01:17:24.819
Kdenlive. So this software I installed from Arch

01:17:24.819 --> 01:17:27.380
Repository and it works for a while. And one

01:17:27.380 --> 01:17:31.899
day this software stopped working and I started

01:17:31.899 --> 01:17:33.819
troubleshooting why it doesn't work anymore.

01:17:34.140 --> 01:17:39.359
And then I find out that SDL version 3 came out

01:17:39.359 --> 01:17:44.100
yesterday and Arch Repository already swapped

01:17:44.100 --> 01:17:48.319
version 2 for version 3. and now Kdenlive doesn't

01:17:48.319 --> 01:17:51.939
work. So it's not really Kdenlive's fault. It

01:17:51.939 --> 01:17:55.420
remained on the version that worked yesterday

01:17:55.420 --> 01:18:00.960
but the dependency changed to the incompatible

01:18:00.960 --> 01:18:05.319
one. And then I reported this to the SDL developer

01:18:05.319 --> 01:18:08.880
and he said like we have the back compatibility

01:18:08.880 --> 01:18:13.609
layer which should satisfy your dependency and

01:18:13.609 --> 01:18:16.810
please help me to fix this and I did provide

01:18:16.810 --> 01:18:21.229
some feedback to him and eventually this was

01:18:21.229 --> 01:18:26.430
fixed not by Arch but by the SDL developer. But

01:18:26.430 --> 01:18:31.449
the story of this scenario is that Arch kind

01:18:31.449 --> 01:18:35.300
of rushes to get all of the new shiny things

01:18:35.300 --> 01:18:37.840
into the repository because that's what users

01:18:37.840 --> 01:18:40.939
expect and that's how this distribution works

01:18:40.939 --> 01:18:45.819
and sometimes things will break it's good and

01:18:45.819 --> 01:18:48.239
bad at the same time depending on how you feel

01:18:48.239 --> 01:18:52.600
and at that moment i really needed my video editor

01:18:52.600 --> 01:18:57.000
and it just didn't work so i installed the same

01:18:57.000 --> 01:19:01.560
software from the flatpak repository the main

01:19:02.079 --> 01:19:06.800
popular repository it's called flat hub and then

01:19:06.800 --> 01:19:11.420
it started working again because i installed

01:19:11.420 --> 01:19:15.079
a different version that packs the sdl version

01:19:15.079 --> 01:19:18.539
within it because it's like a container dependencies

01:19:18.539 --> 01:19:21.800
and everything yeah it's like a container uh

01:19:21.800 --> 01:19:25.760
so that works but this flat a flat pack version

01:19:25.760 --> 01:19:30.119
is literally the same source that i get on debian

01:19:30.119 --> 01:19:35.079
so Once I installed Kdenlive from FlatHub, it's

01:19:35.079 --> 01:19:40.779
literally the same on any Linux. So if this is

01:19:40.779 --> 01:19:44.020
the software that you use, then it completely

01:19:44.020 --> 01:19:48.359
doesn't matter which distribution of Linux you

01:19:48.359 --> 01:19:52.439
use. It's the same because the source is not

01:19:52.439 --> 01:19:56.300
actually Arch or Debian. It's FlatHub, which

01:19:56.300 --> 01:20:00.460
is the provider of this. binary packaging system.

01:20:01.159 --> 01:20:05.340
And then something else broke later on and then

01:20:05.340 --> 01:20:08.640
I downloaded the FlatHub version of that and

01:20:08.640 --> 01:20:12.199
after a while I ended up with a lot of Flatpak

01:20:12.199 --> 01:20:17.260
software instead of using Arch software. Arch

01:20:17.260 --> 01:20:19.920
software is latest and FlatHub is always latest

01:20:19.920 --> 01:20:24.640
but the FlatHub software is usually verified

01:20:24.640 --> 01:20:29.119
and uploaded by the developer of this application.

01:20:29.420 --> 01:20:33.439
While on Arch repository, Kdenlive is not uploaded

01:20:33.439 --> 01:20:36.699
by Kdenlive developers, but actually by Arch

01:20:36.699 --> 01:20:41.359
maintainers. So they sometimes are unable to

01:20:41.359 --> 01:20:45.340
envision all of these scenarios where this could

01:20:45.340 --> 01:20:49.920
break. And I'm not faulting them, not one bit.

01:20:50.390 --> 01:20:53.989
It's just that after a while it became apparent

01:20:53.989 --> 01:20:57.710
to me that I'm using Arch Linux in the same way

01:20:57.710 --> 01:21:01.609
I could use Debian. While Debian at the same

01:21:01.609 --> 01:21:05.090
time is much more stable and by stable I don't

01:21:05.090 --> 01:21:08.810
mean that it crashes because not Arch or Debian

01:21:08.810 --> 01:21:14.029
crashes. Crashes happen usually due to bad drivers

01:21:14.029 --> 01:21:16.930
in the kernel or stuff like that and the kernel

01:21:16.930 --> 01:21:21.000
is the same. I mean, it's still Linux. So it's

01:21:21.000 --> 01:21:25.279
not the crashes that are titled stable in Debian,

01:21:25.399 --> 01:21:29.359
but the stability of software. If you are a developer

01:21:29.359 --> 01:21:34.520
and if you put something, if you design something

01:21:34.520 --> 01:21:38.439
to work for Debian version 13, it will remain

01:21:38.439 --> 01:21:43.060
absolutely compatible with Debian version 13

01:21:43.060 --> 01:21:46.279
for the next five years. because that's how much

01:21:46.279 --> 01:21:50.539
the support period lasts. While if you design

01:21:50.539 --> 01:21:55.460
something for Arch Linux, you can't target a

01:21:55.460 --> 01:21:57.699
version of Arch Linux because it doesn't exist.

01:21:58.960 --> 01:22:05.939
At the end of the day, what brought me over the

01:22:05.939 --> 01:22:10.659
edge, like I just had enough, is the way that

01:22:10.659 --> 01:22:14.979
I make content on YouTube. Very often an idea

01:22:14.979 --> 01:22:19.100
pops while I'm driving back home, commuting from

01:22:19.100 --> 01:22:23.659
work, and as soon as I enter my home I want to

01:22:23.659 --> 01:22:26.159
hit record immediately and get it out of my head.

01:22:26.300 --> 01:22:30.800
Because I never have a script, I just do. And

01:22:30.800 --> 01:22:35.409
my microphone just stays here. And I just take

01:22:35.409 --> 01:22:37.489
it in my hand. It's already connected. My camera

01:22:37.489 --> 01:22:40.170
is already positioned. Everything is in place.

01:22:40.810 --> 01:22:43.510
Even my computer is not turned off. It's just

01:22:43.510 --> 01:22:46.569
waiting for me. I just come home and click record.

01:22:46.750 --> 01:22:52.189
And this one time, that was the last straw, Arch

01:22:52.189 --> 01:22:55.789
Linux told me, no, you're not recording. Not

01:22:55.789 --> 01:23:00.939
today. Not today. OBS is now not working. And

01:23:00.939 --> 01:23:05.260
imagine a cartoon character turning from pink

01:23:05.260 --> 01:23:07.560
color of the face to the red color of the face

01:23:07.560 --> 01:23:12.680
and steam going out of its head. And I'm like,

01:23:12.819 --> 01:23:17.600
okay, let's make a video about how I'm now going

01:23:17.600 --> 01:23:22.699
to switch to Debian back because I just can't.

01:23:23.039 --> 01:23:28.420
My computer has to work. the same as it did yesterday

01:23:28.420 --> 01:23:34.779
because it serves me and I don't really enjoy

01:23:34.779 --> 01:23:38.399
repairing it if I'm not the one who broke it.

01:23:38.760 --> 01:23:43.039
If I break it, I will be very happy to fix it

01:23:43.039 --> 01:23:47.060
because that's the learning process. But if it

01:23:47.060 --> 01:23:50.060
doesn't work the same today as it did yesterday,

01:23:50.300 --> 01:23:54.640
it really doesn't feel like something that I...

01:23:54.960 --> 01:23:58.159
that is designed for me so that's when I returned

01:23:58.159 --> 01:24:02.199
to Debian and it's been a while since then I

01:24:02.199 --> 01:24:05.159
don't know how many days weeks or months have

01:24:05.159 --> 01:24:10.100
passed but people have been telling me in the

01:24:10.100 --> 01:24:13.800
replies you will be back and I really don't feel

01:24:13.800 --> 01:24:17.859
it honestly I really don't feel it Whatever I

01:24:17.859 --> 01:24:21.100
feel like I want to test, there are other ways

01:24:21.100 --> 01:24:25.479
to test. For example, Distrobox is a software

01:24:25.479 --> 01:24:34.380
that uses containers such as Docker in a way

01:24:34.380 --> 01:24:40.159
that you can launch a Docker container that is

01:24:40.159 --> 01:24:45.880
Arch Linux, that is Fedora Linux. that is SUSE

01:24:45.880 --> 01:24:48.920
Linux and you just enter the container, install

01:24:48.920 --> 01:24:52.680
whatever you need inside that container from

01:24:52.680 --> 01:24:55.939
the Arch packages and just run it on your computer.

01:24:56.039 --> 01:24:58.619
It works. It's not emulation. It's just a container.

01:24:59.920 --> 01:25:04.119
So it basically runs full speed. And if I need

01:25:04.119 --> 01:25:06.600
something bare metal, I just install it on one

01:25:06.600 --> 01:25:12.119
of my laptops. I have two and they serve my needs.

01:25:12.670 --> 01:25:17.770
both for my mobility computing and for testing

01:25:17.770 --> 01:25:26.689
purposes. So I feel like my adventure with Arch

01:25:26.689 --> 01:25:34.029
was really necessary in order to better appreciate

01:25:34.029 --> 01:25:37.390
Debian. Okay, now I have a question for you.

01:25:38.430 --> 01:25:41.529
The Nix users have been very quiet in chat. I'm

01:25:41.529 --> 01:25:44.090
not sure if my chat doesn't work, but they must

01:25:44.090 --> 01:25:46.970
be like now going through a lot of feelings because

01:25:46.970 --> 01:25:52.350
there's another way of fixing all this situation.

01:25:52.590 --> 01:25:55.750
Because if you install Nix, I have been told

01:25:55.750 --> 01:25:57.829
that a lot of times. I don't use Nix, by the

01:25:57.829 --> 01:26:01.489
way. But if you install Nix, it's all declarative.

01:26:01.590 --> 01:26:04.710
So you declare your configuration and if something

01:26:04.710 --> 01:26:08.039
breaks, you just roll back and... Nothing ever

01:26:08.039 --> 01:26:11.819
happened. What are your thoughts on Nix? Never

01:26:11.819 --> 01:26:18.100
tried it. I don't have any driver to try it.

01:26:18.119 --> 01:26:23.079
I don't know. Maybe if my community would ask

01:26:23.079 --> 01:26:28.100
me to try it, I probably would. But from what

01:26:28.100 --> 01:26:31.020
I read about it, I don't feel like Nix would

01:26:31.020 --> 01:26:37.409
solve anything for me. Even more so, I am following

01:26:37.409 --> 01:26:42.390
the Linux cast. Oh, yeah, Matt. Matt, yeah. And

01:26:42.390 --> 01:26:46.170
he switched to Nix. And the first time that I

01:26:46.170 --> 01:26:49.989
saw him saying that something that worked yesterday

01:26:49.989 --> 01:26:53.949
is no longer working, I'm like, hell no. No,

01:26:54.090 --> 01:26:57.170
no. I watched that as well. Yeah, and I said,

01:26:57.289 --> 01:27:00.109
no, no, no. Even if you can easily roll back,

01:27:00.350 --> 01:27:03.420
I don't... When I even turned my computer off

01:27:03.420 --> 01:27:05.859
for it to work again. I'm not sure if I'm just

01:27:05.859 --> 01:27:08.079
lucky or something. I don't know what the experience

01:27:08.079 --> 01:27:10.899
is with your other friends that use Mac. But

01:27:10.899 --> 01:27:14.239
I install all my packages through Homebrew in

01:27:14.239 --> 01:27:16.920
macOS. I don't use the Apple Store. That sucks.

01:27:17.100 --> 01:27:19.579
It's horrible. It's garbage. I don't like it

01:27:19.579 --> 01:27:22.300
at all. I like to have my packages in a file.

01:27:22.560 --> 01:27:25.640
If I deploy a new Mac, I install all of the packages,

01:27:25.760 --> 01:27:28.859
you know, via Homebrew. And I just all at once.

01:27:29.279 --> 01:27:31.939
install them if i need to update them they update

01:27:31.939 --> 01:27:35.420
them but it has never broken on me you know i

01:27:35.420 --> 01:27:39.779
use obs a lot audio issues never have any audio

01:27:39.779 --> 01:27:41.920
issues i don't know if it's the way that they

01:27:41.920 --> 01:27:44.560
package things i don't know if the packages are

01:27:44.560 --> 01:27:46.920
containerized or something so that's why you

01:27:46.920 --> 01:27:50.479
don't get affected by by dependencies or something

01:27:50.479 --> 01:27:53.800
but um that's one of the things that i like about

01:27:53.800 --> 01:27:57.039
mac and like i'm saying i'm not saying mac is

01:27:57.039 --> 01:28:01.600
perfect maybe I have been lucky. Maybe that's

01:28:01.600 --> 01:28:04.260
not the case with everyone else. If someone in

01:28:04.260 --> 01:28:07.420
the comments uses Mac, let me know if that's

01:28:07.420 --> 01:28:10.000
the experience that you get as well. But do you

01:28:10.000 --> 01:28:14.180
have any thoughts on that? I think I have seen

01:28:14.180 --> 01:28:17.039
that Homebrew actually exists on Linux as well

01:28:17.039 --> 01:28:23.260
in the pretty much same form as on Mac. It's

01:28:23.260 --> 01:28:27.260
just that it kind of feels redundant for me because...

01:28:28.590 --> 01:28:31.050
That's not how I used to do things on Linux.

01:28:31.350 --> 01:28:33.489
Yeah, because you already have a package manager,

01:28:33.670 --> 01:28:36.609
right? But here in macOS, I don't, right? So

01:28:36.609 --> 01:28:39.229
I have the Apple Store, which is trash. So I

01:28:39.229 --> 01:28:42.289
need a way to install packages, which is as long

01:28:42.289 --> 01:28:46.069
as I trust the source. My Mac friends are very

01:28:46.069 --> 01:28:50.810
colorful in terms of one is a hardcore Apple

01:28:50.810 --> 01:28:55.390
user and also a programmer. Another one is a

01:28:55.390 --> 01:28:58.659
very basic. computer user and the only reason

01:28:58.659 --> 01:29:01.960
why he bought a mac in the first place is because

01:29:01.960 --> 01:29:04.979
they told him it has a good battery life and

01:29:04.979 --> 01:29:07.119
he really didn't care what operating system it

01:29:07.119 --> 01:29:10.260
is he just uses a web browser pretty much so

01:29:10.260 --> 01:29:12.520
it's a it's a web browser with a good battery

01:29:12.520 --> 01:29:17.000
for him so that's another type of user and i

01:29:17.000 --> 01:29:20.840
have a couple more in between but i think the

01:29:20.840 --> 01:29:28.449
one that is a programmer he is like my, let's

01:29:28.449 --> 01:29:35.369
say, favorite Mac user to do any kinds of comparison

01:29:35.369 --> 01:29:39.449
with or he really likes to talk these topics

01:29:39.449 --> 01:29:44.189
with me. So that gives me opportunity to talk

01:29:44.189 --> 01:29:49.529
to him. And he's one of those that don't change

01:29:49.529 --> 01:29:55.199
anything from the way Apple designed it. Except

01:29:55.199 --> 01:29:58.899
that he does use homebrew for some stuff that

01:29:58.899 --> 01:30:02.439
he needs. I just forgot what it was. He said

01:30:02.439 --> 01:30:04.920
that he uses homebrew because some things are

01:30:04.920 --> 01:30:08.619
not available in any other way. And he needs

01:30:08.619 --> 01:30:13.800
those things. But I think he's a JetBrains user

01:30:13.800 --> 01:30:18.239
or something like that. I'm not sure. He uses

01:30:18.239 --> 01:30:21.659
a lot of these very popular... commercial tools

01:30:21.659 --> 01:30:25.979
that help him to be faster and more productive

01:30:25.979 --> 01:30:31.199
and stuff like that as i said i am not a programmer

01:30:31.199 --> 01:30:36.560
i am just learning so i can't even begin to pretend

01:30:36.560 --> 01:30:42.500
that i am chasing some kind of productivity optimization

01:30:42.500 --> 01:30:47.199
or whatever i just need a text editor that can

01:30:47.760 --> 01:30:50.239
put some color on my code so that i don't miss

01:30:50.239 --> 01:30:55.340
some kind of uh um i i suck with some english

01:30:55.340 --> 01:30:59.600
words but uh parentheses you know uh so you're

01:30:59.600 --> 01:31:04.819
from croatia yeah yeah croatia okay i i have

01:31:04.819 --> 01:31:09.279
a fairly fine experience with general english

01:31:09.279 --> 01:31:12.880
language but i'd never talk in english with other

01:31:12.880 --> 01:31:16.359
programmers so some of these words are not very

01:31:16.359 --> 01:31:19.579
often coming out of my mouth so that's why i

01:31:19.579 --> 01:31:25.439
get stuck um but yeah okay do you have any thoughts

01:31:25.439 --> 01:31:28.819
on mac os have you ever used mac os or or no

01:31:28.819 --> 01:31:32.439
thoughts at all never never used it uh i know

01:31:32.439 --> 01:31:37.810
how it became I know how it came to be from you

01:31:37.810 --> 01:31:41.250
know back in the day when they fired Steve Jobs

01:31:41.250 --> 01:31:46.229
from Apple and then he made another operating

01:31:46.229 --> 01:31:51.029
system and then they practically bought his new

01:31:51.029 --> 01:31:55.579
company and integrated his operating system into

01:31:55.579 --> 01:32:00.579
what we know about Mac as a Mac today. I know

01:32:00.579 --> 01:32:04.239
it has some free BSD components in there, but

01:32:04.239 --> 01:32:14.779
other than being of Unix, how do you say... How

01:32:14.779 --> 01:32:19.140
do you say it in English? Unix certified? Not

01:32:19.140 --> 01:32:22.560
certified, but... no no no your parents and grandparents

01:32:22.560 --> 01:32:26.779
where you are coming from right uh i wanted to

01:32:26.779 --> 01:32:30.920
say this right yeah i mean it's it it's based

01:32:30.920 --> 01:32:33.640
what i meant is that it's coming from the unix

01:32:33.640 --> 01:32:37.539
family but i wanted a different word um so yeah

01:32:37.539 --> 01:32:42.439
it is coming from unix family but also it's very

01:32:42.439 --> 01:32:47.869
closed uh as much as apple is able to keep it

01:32:47.869 --> 01:32:51.550
closed i doubt that users like you would allow

01:32:51.550 --> 01:32:56.090
apple to close it like ipad os is uh because

01:32:56.090 --> 01:32:58.409
then you would be unable to do anything on it

01:32:58.409 --> 01:33:02.170
anymore i i would switch i would go to and that's

01:33:02.170 --> 01:33:07.229
yeah go on go on uh i wasn't planning to add

01:33:07.229 --> 01:33:10.090
anything meaningful but you know uh i i think

01:33:10.569 --> 01:33:14.970
the power users of Mac are those who are keeping

01:33:14.970 --> 01:33:20.390
Apple from closing it fully. So just being able

01:33:20.390 --> 01:33:24.010
to install stuff like Homebrew and whatever window

01:33:24.010 --> 01:33:28.489
managers. Yeah. So that's still a good light

01:33:28.489 --> 01:33:35.310
on the whole operating system and at least in

01:33:35.310 --> 01:33:37.949
comparison to microsoft at least apple pretends

01:33:37.949 --> 01:33:40.989
that they care about my privacy so from that

01:33:40.989 --> 01:33:46.270
perspective i can hold them to their word it

01:33:46.270 --> 01:33:50.590
although i will not give them a chance to have

01:33:50.590 --> 01:33:56.289
some of my sensitive information but in contrast

01:33:56.289 --> 01:34:01.409
to windows who just gives it out loud like we

01:34:01.409 --> 01:34:04.819
are now screenshotting everything that you do

01:34:04.819 --> 01:34:08.439
like every second and you can search for what

01:34:08.439 --> 01:34:12.899
you did like a year ago and it will tell you

01:34:12.899 --> 01:34:16.979
yeah about that website can you forget that i

01:34:16.979 --> 01:34:20.380
was on that website please you know and uh no

01:34:20.380 --> 01:34:23.319
it's it's a black market already all of that

01:34:23.319 --> 01:34:27.520
info well they do say that it's locally on your

01:34:27.520 --> 01:34:31.199
computer and it's not that I don't believe them

01:34:31.199 --> 01:34:36.319
that it's locally it's just that I have no proof

01:34:36.319 --> 01:34:40.539
for that because it's closed software proprietary

01:34:40.539 --> 01:34:44.359
software you know but more closed than proprietary

01:34:44.359 --> 01:34:48.739
and if you cannot inspect the code then how do

01:34:48.739 --> 01:34:52.569
you absolutely know that this information is

01:34:52.569 --> 01:34:58.130
not going anywhere. You can't. You can just trust

01:34:58.130 --> 01:35:03.170
them to a certain degree. And then there is another

01:35:03.170 --> 01:35:06.970
problem. Windows as the most popular desktop

01:35:06.970 --> 01:35:11.930
operating system is the most targeted by all

01:35:11.930 --> 01:35:14.689
kinds of malicious people. Let's just group them

01:35:14.689 --> 01:35:21.680
in that way. And they now know that like let's

01:35:21.680 --> 01:35:24.399
say that I'm a Windows user they now know that

01:35:24.399 --> 01:35:29.380
me as a user of Windows have this database of

01:35:29.380 --> 01:35:32.319
really really nice stuff that they should be

01:35:32.319 --> 01:35:35.659
getting their hands on and this is located in

01:35:35.659 --> 01:35:39.720
this place on my on my SSD and they know exactly

01:35:39.720 --> 01:35:41.960
what I need to take from my computer whether

01:35:41.960 --> 01:35:44.680
they will use phishing methods whether they will

01:35:44.680 --> 01:35:47.619
use some security holes that I still don't know

01:35:47.619 --> 01:35:51.550
about it doesn't really matter all that matters

01:35:51.550 --> 01:35:56.130
is that Microsoft has now made it easier for

01:35:56.130 --> 01:35:59.569
the malicious people to get their hands on something

01:35:59.569 --> 01:36:03.390
very dear to me, which is my privacy. Whether

01:36:03.390 --> 01:36:10.050
this local database contains only my password

01:36:10.050 --> 01:36:15.569
to my Google account, which matters to me because

01:36:15.569 --> 01:36:20.380
my YouTube account is on it, But, you know, there

01:36:20.380 --> 01:36:22.880
can be some other stuff that's less important.

01:36:22.979 --> 01:36:27.159
If stolen, whatever. There could be some photos

01:36:27.159 --> 01:36:30.859
of my family, which I really don't want to share

01:36:30.859 --> 01:36:34.659
around. It's mine, you know, my photos. I have

01:36:34.659 --> 01:36:39.380
my personal albums. So there could be a lot of

01:36:39.380 --> 01:36:45.180
other stuff in between. I don't like this, like

01:36:45.180 --> 01:36:51.470
Target. I don't like this red spot of the sniper

01:36:51.470 --> 01:36:56.350
on my head. Like this is where you need to target.

01:36:56.529 --> 01:37:01.890
So from that perspective, I still enjoy using

01:37:01.890 --> 01:37:07.329
free software. And yes, Linux cannot do some

01:37:07.329 --> 01:37:10.710
things. There is always this, but I need this

01:37:10.710 --> 01:37:14.300
application. Okay, fine. I'm not... telling you

01:37:14.300 --> 01:37:17.060
that you have to switch to Linux. I'm telling

01:37:17.060 --> 01:37:20.640
you that this is a choice for you. If you really

01:37:20.640 --> 01:37:22.859
need to work with that application that only

01:37:22.859 --> 01:37:28.399
works on macOS or only works on Windows, then

01:37:28.399 --> 01:37:30.979
you need to use it. Who am I to say anything

01:37:30.979 --> 01:37:36.180
else? You have to use it. I'm lucky that at work

01:37:36.180 --> 01:37:41.840
I wasn't... How do I put it? My boss never told

01:37:41.840 --> 01:37:45.140
me... Yeah, I'm not forced to use Windows. I'm

01:37:45.140 --> 01:37:49.119
only forced to be able to do my job. Okay. And

01:37:49.119 --> 01:37:51.239
my boss tells me to install whatever you want.

01:37:51.399 --> 01:37:54.420
Just be able to do your job. And I was like,

01:37:54.520 --> 01:37:58.819
yeah. And let's put Linux on my laptop. And there

01:37:58.819 --> 01:38:01.340
is one application that I really need to use.

01:38:01.460 --> 01:38:04.659
And that is Windows only. But luckily it works

01:38:04.659 --> 01:38:09.340
in Wine. And Wine is Windows compatibility layer

01:38:09.340 --> 01:38:12.500
on Linux. So from that perspective. thumbs up

01:38:12.500 --> 01:38:16.060
for me and I'm perfectly happy. A lot of other

01:38:16.060 --> 01:38:20.239
people cannot switch that easy because they rely

01:38:20.239 --> 01:38:22.939
on all kinds of software that doesn't exist.

01:38:23.220 --> 01:38:28.560
But at the same time I try to preach and live

01:38:28.560 --> 01:38:33.979
at the same time the mantra. If there are two

01:38:33.979 --> 01:38:40.899
softwares of a similar use case, like they are

01:38:40.899 --> 01:38:44.979
used for the same thing and one is proprietary

01:38:44.979 --> 01:38:47.640
and another one is free software and by free

01:38:47.640 --> 01:38:51.779
software I mean open source can be modified freely

01:38:51.779 --> 01:38:55.119
shared around that kind of free software and

01:38:55.119 --> 01:38:59.460
if this free software satisfies all my needs

01:38:59.460 --> 01:39:03.960
I will use free software rather than using what

01:39:03.960 --> 01:39:07.920
is publicly considered better software because

01:39:07.920 --> 01:39:11.260
in my eyes these softwares are the same because

01:39:11.260 --> 01:39:16.260
I do not use this extra functionality that makes

01:39:16.260 --> 01:39:20.920
this better software. So for me in case of let's

01:39:20.920 --> 01:39:23.960
say Photoshop and Gimp, Gimp is better simply

01:39:23.960 --> 01:39:27.600
because Photoshop cannot do anything that Gimp

01:39:27.600 --> 01:39:31.819
cannot do that I need. Okay, makes sense. Yeah

01:39:31.819 --> 01:39:35.270
and there are a lot of people who I know and

01:39:35.270 --> 01:39:39.489
other content creators who are primarily gamers

01:39:39.489 --> 01:39:42.770
but I don't think gaming has anything to do with

01:39:42.770 --> 01:39:46.270
it but the fact that a lot of them choose Photoshop

01:39:46.270 --> 01:39:49.109
to make their thumbnails because they know that

01:39:49.109 --> 01:39:52.449
Photoshop is the best software in the world so

01:39:52.449 --> 01:39:58.510
they want the best software and they don't really

01:39:58.510 --> 01:40:02.369
wants to be persuaded into anything other than

01:40:02.369 --> 01:40:07.310
Photoshop and this is their choice. So I can't

01:40:07.310 --> 01:40:10.770
do anything about that except wait for someone

01:40:10.770 --> 01:40:18.869
who wants to talk these topics. Okay. Now, I've

01:40:18.869 --> 01:40:22.210
been thinking about Linux because I'm on a Mac

01:40:22.210 --> 01:40:24.649
right now. That's my main machine, right? But

01:40:24.649 --> 01:40:27.859
when I'm... in calls with four guests, right?

01:40:28.000 --> 01:40:31.199
I receive all those video streams. I also receive

01:40:31.199 --> 01:40:34.539
their screens. So sometimes I receive eight video

01:40:34.539 --> 01:40:37.319
streams on the computer and that hits it really

01:40:37.319 --> 01:40:40.220
hard. And it becomes a little bit slow because

01:40:40.220 --> 01:40:42.180
it's a lot of processing that it has to do with

01:40:42.180 --> 01:40:44.579
all that video. And then it has to stream it

01:40:44.579 --> 01:40:47.840
to YouTube, Twitch, and all that. You know, pretty

01:40:47.840 --> 01:40:51.140
powerful machine. But I would like to leave it

01:40:51.140 --> 01:40:54.649
as... My streaming machine, like the brains,

01:40:54.829 --> 01:40:58.369
right? And I've been thinking about what Linux

01:40:58.369 --> 01:41:00.529
distro to use because I have another machine

01:41:00.529 --> 01:41:03.229
back there. I installed Arch, but I never logged

01:41:03.229 --> 01:41:07.170
into it. I didn't, no. I feel the same way that

01:41:07.170 --> 01:41:10.149
you do with Arch. I don't need the latest and

01:41:10.149 --> 01:41:12.670
greatest, right? So I've been thinking about

01:41:12.670 --> 01:41:14.970
Debian because I run Debian in all my different

01:41:14.970 --> 01:41:17.689
servers, right? But I don't have a desktop environment

01:41:17.689 --> 01:41:22.479
there, right? Just headless servers, BSSH. What

01:41:22.479 --> 01:41:25.899
would you do on that Linux computer? What would

01:41:25.899 --> 01:41:29.279
it be used for if Mac remains your main streaming

01:41:29.279 --> 01:41:33.800
machine? Switch OBS scenes. That would be, I

01:41:33.800 --> 01:41:37.100
would control my Mac through that machine to

01:41:37.100 --> 01:41:41.600
switch scenes in OBS. Yeah. And show my terminal,

01:41:41.779 --> 01:41:44.640
show the browser, you know, just record the videos

01:41:44.640 --> 01:41:47.439
pretty much sometimes. Some other times in the

01:41:47.439 --> 01:41:48.979
Mac. I'm not sure if I understood correctly.

01:41:49.199 --> 01:41:54.239
On Linux, you would... use OBS on Linux instead

01:41:54.239 --> 01:41:57.060
of on Mac? On the Mac, it would remain on the

01:41:57.060 --> 01:42:01.180
Mac, but you can, what is this, the API that

01:42:01.180 --> 01:42:04.039
you can expose from OBS, I would expose that

01:42:04.039 --> 01:42:07.720
in my local network, and I could control my OBS

01:42:07.720 --> 01:42:11.260
on the Mac from the Linux machine over the network,

01:42:11.479 --> 01:42:16.840
right? How would that make your Mac less sweaty?

01:42:17.720 --> 01:42:21.020
Oh, because... When I'm streaming, I have four

01:42:21.020 --> 01:42:24.880
guests, for example. I have to switch to my scene,

01:42:25.039 --> 01:42:27.720
I have to switch to my terminal, to my browser.

01:42:27.920 --> 01:42:30.479
And then, you know, with all of the other stuff

01:42:30.479 --> 01:42:32.979
that it has to do, it gets a little bit laggy,

01:42:32.979 --> 01:42:36.880
right? And it doesn't... Okay, so you would put

01:42:36.880 --> 01:42:40.680
some stuff on the other computer just to make

01:42:40.680 --> 01:42:43.000
it breathe a little bit easier. Yeah, just to

01:42:43.000 --> 01:42:45.220
make it breathe a little bit. Exactly, exactly.

01:42:46.079 --> 01:42:49.699
Well, that's hardly anything complex that needs

01:42:49.699 --> 01:42:54.039
to be discussed, I suppose. I mean, in theory,

01:42:54.180 --> 01:42:57.619
I'm not saying you should do this if you're used

01:42:57.619 --> 01:43:00.500
to doing this on the Mac, but in theory, you

01:43:00.500 --> 01:43:06.199
could put an NVIDIA card on the PC and use that

01:43:06.199 --> 01:43:10.979
one with OBS to mix a lot of streams at the same

01:43:10.979 --> 01:43:17.729
time because NVENC... It's a small machine. I

01:43:17.729 --> 01:43:20.510
cannot put graphics card. Oh, that one, okay.

01:43:20.890 --> 01:43:27.010
That one, no. That kind of solves the whole idea,

01:43:27.109 --> 01:43:32.310
yeah? Yeah. But what I meant is that with an

01:43:32.310 --> 01:43:35.810
NVIDIA card on Linux, you would be able to do

01:43:35.810 --> 01:43:38.010
pretty much the same as you would be able to

01:43:38.010 --> 01:43:41.470
do with a Mac, what they call it, like Pro Max.

01:43:42.389 --> 01:43:45.829
CPUs, you know, the higher end CPUs that have

01:43:45.829 --> 01:43:49.270
more graphics power. But the difference in cost

01:43:49.270 --> 01:43:53.270
is usually substantial if you go to that kinds

01:43:53.270 --> 01:43:57.109
of Macs. And especially if you go with high amounts

01:43:57.109 --> 01:44:01.310
of RAM, which costs like peanuts on PC, while

01:44:01.310 --> 01:44:06.569
Apple asks a lot of money for RAM and you can't

01:44:06.569 --> 01:44:10.329
upgrade them unless you're using a thick Mac.

01:44:10.960 --> 01:44:13.979
pro the big bucket on the laptop that i'm using

01:44:13.979 --> 01:44:17.159
i cannot do anything about it but what distro

01:44:17.159 --> 01:44:21.220
would you recommend for me to try there i'm thinking

01:44:21.220 --> 01:44:23.500
about debian and i'm like debian debian debian

01:44:23.500 --> 01:44:26.460
that's what my logic tells me to do right even

01:44:26.460 --> 01:44:29.699
though everyone sells says arch or try nix and

01:44:29.699 --> 01:44:34.340
i'm like no i'm not gonna learn nix no so the

01:44:34.340 --> 01:44:39.060
thing is there isn't that much truly meaningful

01:44:39.060 --> 01:44:41.800
difference between all of the Linux distributions.

01:44:42.060 --> 01:44:44.600
They are all based on the same kernel and kernel

01:44:44.600 --> 01:44:47.180
means all of the drivers. So that's like the

01:44:47.180 --> 01:44:50.680
half of the system already. Then you have your

01:44:50.680 --> 01:44:55.680
GNU utils which make up all of the basic commands

01:44:55.680 --> 01:45:02.560
like ls, watch... stuff like that. Typical terminal

01:45:02.560 --> 01:45:05.500
commands. This is all the same on pretty much

01:45:05.500 --> 01:45:09.000
every distribution and the only meaningful difference

01:45:09.000 --> 01:45:13.600
is the package manager and the package repository.

01:45:14.239 --> 01:45:20.840
So it all comes down to whether you would benefit

01:45:20.840 --> 01:45:25.960
from having your software change every day or

01:45:25.960 --> 01:45:30.180
you would benefit more from your computer working

01:45:30.180 --> 01:45:35.000
the exact same in terms of reliability as it

01:45:35.000 --> 01:45:38.140
did yesterday and the month before that and the

01:45:38.140 --> 01:45:41.300
month before that, meaning you will not experiment

01:45:41.300 --> 01:45:46.800
on it too much. That's where stable distribution

01:45:46.800 --> 01:45:52.539
shine and You know, you can use Debian, you can

01:45:52.539 --> 01:45:54.840
use Red Hat Enterprise Linux, if that's your

01:45:54.840 --> 01:45:58.939
thing, or Rocky Linux. Well, it wasn't meant

01:45:58.939 --> 01:46:04.500
to be a joke, but it is a lineup of stable distributions

01:46:04.500 --> 01:46:08.140
that tend to change when they change, you know.

01:46:08.340 --> 01:46:12.479
So you can, I don't know, there is also something

01:46:12.479 --> 01:46:16.369
that I would call like, I don't know. that makes

01:46:16.369 --> 01:46:20.229
sense but something in between rolling and stable

01:46:20.229 --> 01:46:23.149
like there is a distribution called open mandriva

01:46:23.149 --> 01:46:30.670
that one is one of the i'm missing a word independent

01:46:30.670 --> 01:46:34.930
distributions right so what i mean by independent

01:46:34.930 --> 01:46:39.449
is you have mint linux mint which is not independent

01:46:39.449 --> 01:46:44.630
it uses debian or ubuntu like like for the 99

01:46:45.609 --> 01:46:48.449
their distribution and then change it. They change

01:46:48.449 --> 01:46:56.869
it a little bit to make it minty. And what OpenMandriva

01:46:56.869 --> 01:47:00.029
is, it's an independent distribution and the

01:47:00.029 --> 01:47:03.050
reason why I mentioned it is they call it a rolling

01:47:03.050 --> 01:47:07.130
distribution but it doesn't really roll like

01:47:07.130 --> 01:47:11.890
Arch Linux, like random packages every day. Basically

01:47:12.779 --> 01:47:15.520
They have a version of OpenMandriva which is

01:47:15.520 --> 01:47:19.819
only for testing and they put new stuff every

01:47:19.819 --> 01:47:22.039
day into this testing branch which you don't

01:47:22.039 --> 01:47:26.399
use for a month and after a month a new update

01:47:26.399 --> 01:47:30.640
just drops with everything. But this everything

01:47:30.640 --> 01:47:35.560
is sort of tested. It feels like it's a new release

01:47:35.560 --> 01:47:41.359
but coming every month. So it's... It's kind

01:47:41.359 --> 01:47:45.420
of a middle ground between rolling and stable,

01:47:45.720 --> 01:47:49.720
but it updates all of the time. Meaning like

01:47:49.720 --> 01:47:52.720
once per month. And you have all kinds of different

01:47:52.720 --> 01:47:58.420
stuff like Fedora. Linux updates once every half

01:47:58.420 --> 01:48:03.920
a year. So that's fairly often. But in between,

01:48:04.039 --> 01:48:09.890
it updates the kernel every time. a new version

01:48:09.890 --> 01:48:12.689
comes out even the minor one so basically you

01:48:12.689 --> 01:48:15.970
get like kernel update every week but also we

01:48:15.970 --> 01:48:19.930
get a lot of patches and even sometimes desktop

01:48:19.930 --> 01:48:24.649
environments gets new versions so Fedora would

01:48:24.649 --> 01:48:28.189
be like they call it a stable distribution like

01:48:28.189 --> 01:48:31.449
something that changes twice per year but in

01:48:31.449 --> 01:48:34.710
reality it changes quite a lot under the hood

01:48:34.710 --> 01:48:39.869
in between these six months time So for people

01:48:39.869 --> 01:48:44.510
who are let's say gamers with AMD graphics cards

01:48:44.510 --> 01:48:50.369
sometimes they will want latest graphics drivers

01:48:50.369 --> 01:48:54.810
and you get them for AMD graphics card with the

01:48:54.810 --> 01:48:57.649
kernel with the new version of kernel because

01:48:57.649 --> 01:49:01.229
that's how AMD does their new versions of graphics

01:49:01.229 --> 01:49:05.409
drivers. They put them in the kernel and you

01:49:05.409 --> 01:49:07.649
need to install the new kernel. That's their

01:49:07.649 --> 01:49:11.090
open source drivers. NVIDIA, on the other hand,

01:49:11.170 --> 01:49:13.850
they have their proprietary drivers that you

01:49:13.850 --> 01:49:17.069
install separately, so it doesn't matter if you're

01:49:17.069 --> 01:49:19.289
on Arch or on Debian, you can have the latest

01:49:19.289 --> 01:49:22.789
version of NVIDIA drivers because they are somewhat

01:49:22.789 --> 01:49:28.010
detached from the system, at least from the package

01:49:28.010 --> 01:49:33.770
manager perspective. And you have a lot of choices.

01:49:34.069 --> 01:49:39.659
Now, I cannot pretend that I'm not biased because

01:49:39.659 --> 01:49:44.840
I love Debian and the package manager is awesome

01:49:44.840 --> 01:49:52.479
and by awesome I think it's really another word

01:49:52.479 --> 01:49:58.579
is missing in English but it is capable of maneuvering

01:49:58.579 --> 01:50:02.359
a lot of packaging scenarios. And by that I will

01:50:02.359 --> 01:50:05.619
give you one really easy example with Arch Linux

01:50:05.619 --> 01:50:09.060
that happens to me while I was using Arch Linux.

01:50:09.960 --> 01:50:14.560
Arch Linux maintainers have one day decided that...

01:50:14.560 --> 01:50:17.319
Can you bring up my screen please? Yeah, I'll

01:50:17.319 --> 01:50:23.180
switch to it. You ready? Yeah. Arch Linux. Let

01:50:23.180 --> 01:50:33.960
me show it to you. okay okay with this date so

01:50:33.960 --> 01:50:39.899
13th of june of this year we split our firmware

01:50:39.899 --> 01:50:43.539
into several vendor focused packages linux firmware

01:50:43.539 --> 01:50:46.579
is now an empty package depending on your default

01:50:46.579 --> 01:50:49.340
set of firmware unfortunately this coincided

01:50:49.340 --> 01:50:51.960
with upstream reorganizing the sim leak blah

01:50:51.960 --> 01:50:54.460
blah blah blah blah result resulting in situation

01:50:54.460 --> 01:50:58.300
that our package manager cannot handle. So we

01:50:58.300 --> 01:51:01.399
have made a change to our own operating system

01:51:01.399 --> 01:51:07.359
and made it unhandlable by our own package manager.

01:51:07.659 --> 01:51:12.319
This literally says here. So now as a user you

01:51:12.319 --> 01:51:16.140
have to, where is it, to progress first remove

01:51:16.140 --> 01:51:19.800
the firmware and then reinstall it as a part

01:51:19.800 --> 01:51:23.899
of the operating system upgrade. So these steps

01:51:23.899 --> 01:51:27.250
are easy. And I'm not saying that this is hard

01:51:27.250 --> 01:51:29.449
to do. You just have to read the Arch webpage

01:51:29.449 --> 01:51:33.569
to be introduced to these breaking changes and

01:51:33.569 --> 01:51:36.090
what is required from you as a user to continue

01:51:36.090 --> 01:51:40.529
using Arch unbroken. This is easy. What I wanted

01:51:40.529 --> 01:51:43.630
to say is that Pacman as their package manager

01:51:43.630 --> 01:51:47.989
is unable to handle their own change in the operating

01:51:47.989 --> 01:51:54.880
system. And I am 101 % sure that apt package

01:51:54.880 --> 01:52:00.180
manager in Debian can handle such changes if

01:52:00.180 --> 01:52:04.460
Debian would introduce them. And they do introduce

01:52:04.460 --> 01:52:10.039
such changes between the Debian versions. For

01:52:10.039 --> 01:52:18.199
example, there is the init system on Linux. The

01:52:18.199 --> 01:52:23.300
most popular nowadays is systemd which has a

01:52:23.300 --> 01:52:26.010
lot of love -hate relationship with a lot of

01:52:26.010 --> 01:52:29.350
users. What do you think that is? I have seen

01:52:29.350 --> 01:52:33.149
that as well. Yeah, I can try to answer that.

01:52:33.289 --> 01:52:35.930
But before that, I just wanted to say about apt

01:52:35.930 --> 01:52:39.789
package manager of Debian. Debian didn't use

01:52:39.789 --> 01:52:45.529
systemd always. In one version, they did switch

01:52:45.529 --> 01:52:50.750
to systemd from the old sysvinit system. And

01:52:50.750 --> 01:52:57.000
this is a huge change. This is a really big,

01:52:57.140 --> 01:53:00.159
big change that changes a lot of things in your

01:53:00.159 --> 01:53:02.979
system because init system is the first thing

01:53:02.979 --> 01:53:06.979
that boots after the kernel wakes up and it handles

01:53:06.979 --> 01:53:11.619
the rest of your system. And the apt package

01:53:11.619 --> 01:53:14.960
manager was... programmed in a way that when

01:53:14.960 --> 01:53:17.359
you upgrade from this version of Debian with

01:53:17.359 --> 01:53:20.439
the old init system to this version of Debian,

01:53:20.579 --> 01:53:26.199
the next one, it just transitioned. It managed

01:53:26.199 --> 01:53:28.539
to replace everything for everything new and

01:53:28.539 --> 01:53:34.140
it worked. So I think this is a high praise of

01:53:34.140 --> 01:53:37.899
this package manager which not many people appreciate.

01:53:38.970 --> 01:53:42.170
I am not saying that you should appreciate the

01:53:42.170 --> 01:53:44.689
package manager. After all, the package manager

01:53:44.689 --> 01:53:47.029
is something that should get out of your way

01:53:47.029 --> 01:53:50.470
and you shouldn't worry about it too much. And

01:53:50.470 --> 01:53:53.869
this is exactly why I'm mentioning Pac -Man here

01:53:53.869 --> 01:53:56.829
because it didn't manage to get out of my way.

01:53:57.649 --> 01:54:02.029
And so from that perspective, I think Pac -Man

01:54:02.029 --> 01:54:05.869
has a lot of food remaining to eat, to grow up

01:54:05.869 --> 01:54:12.619
and stuff like that. As for systemd, that's for

01:54:12.619 --> 01:54:20.960
kids. Arguing about systemd is for kids. And

01:54:20.960 --> 01:54:27.460
what can I say? The beauty of Linux is that if

01:54:27.460 --> 01:54:31.100
you don't like this piece of software, just don't

01:54:31.100 --> 01:54:39.340
use it. version of Linux distribution that you

01:54:39.340 --> 01:54:43.380
are used to has switched the version of software

01:54:43.380 --> 01:54:46.100
that you liked for something that you now don't

01:54:46.100 --> 01:54:51.359
like for example systemd then why would you continue

01:54:51.359 --> 01:54:54.699
using this distribution if it contains something

01:54:54.699 --> 01:54:57.640
that you don't want to use just switch to another

01:54:57.640 --> 01:55:01.760
one of the 200 distributions out there and you're

01:55:01.760 --> 01:55:09.579
fine I mean It's a bit silly. I can understand

01:55:09.579 --> 01:55:14.840
that some bigger forces are playing a role here

01:55:14.840 --> 01:55:18.100
and they are pushing systemd everywhere, starting

01:55:18.100 --> 01:55:27.309
from Red Hat. But if the community is... Guys

01:55:27.309 --> 01:55:30.430
who speak Croatian, how do you say složno in

01:55:30.430 --> 01:55:34.750
English? If you play together, like the whole

01:55:34.750 --> 01:55:38.369
Linux community, if you... Did you hear that

01:55:38.369 --> 01:55:41.909
lightning? Yeah, I did. It was very strong. Yeah,

01:55:41.949 --> 01:55:44.170
raining is about to start here, man, and it gets

01:55:44.170 --> 01:55:50.550
crazy. Go on. I'm sorry. I mean, if the community

01:55:50.550 --> 01:55:56.930
really stands together, they can... make alternatives

01:55:56.930 --> 01:56:03.350
as usable as the mainstream software in this

01:56:03.350 --> 01:56:09.369
case an init system right so you have like Gentoo

01:56:09.369 --> 01:56:15.449
which uses I think the sysrc init package init

01:56:15.449 --> 01:56:20.420
daemon that one is mostly designed by them and

01:56:20.420 --> 01:56:24.920
they are the main ones who use it. Some distributions

01:56:24.920 --> 01:56:28.960
still use the old sysv init that still comes

01:56:28.960 --> 01:56:33.600
from the Unix age. As long as these distributions

01:56:33.600 --> 01:56:37.460
keep maintaining these init systems they remain

01:56:37.460 --> 01:56:42.779
a viable way of using your Linux computer and

01:56:42.779 --> 01:56:46.640
you're not forced into using systemd if for any

01:56:46.640 --> 01:56:50.159
reason you dislike it. I mean There is a good

01:56:50.159 --> 01:56:55.520
argument against this systemd is that a lot of

01:56:55.520 --> 01:56:59.199
people like the Unix philosophy which says do

01:56:59.199 --> 01:57:04.300
one thing only and do it the best possible way.

01:57:05.560 --> 01:57:12.180
That's hardly a good example, but it's a good

01:57:12.180 --> 01:57:19.430
joke. But what sysv init system was doing, was

01:57:19.430 --> 01:57:25.630
only taking care of other demons running. It's

01:57:25.630 --> 01:57:30.310
like this demon would run first and it would

01:57:30.310 --> 01:57:33.810
lend its hands to all the other demons and help

01:57:33.810 --> 01:57:36.710
them get up on their feet to start working on

01:57:36.710 --> 01:57:40.029
your system. What SystemD is doing is helping

01:57:40.029 --> 01:57:43.270
other demons to start up, other services to start

01:57:43.270 --> 01:57:47.569
up. It also manages your login system with your

01:57:47.569 --> 01:57:51.590
graphical environment. It also manages some of

01:57:51.590 --> 01:57:54.029
your sound system. It also manages some of your

01:57:54.029 --> 01:57:58.390
drivers. It has its fingers everywhere like a

01:57:58.390 --> 01:58:01.970
huge octopus. And a lot of people think that's

01:58:01.970 --> 01:58:05.250
a very bad idea because... when something goes

01:58:05.250 --> 01:58:10.350
wrong in this Megalodon software then a lot of

01:58:10.350 --> 01:58:15.710
other fails of this octopus will cause the rest

01:58:15.710 --> 01:58:19.609
of the system to fail as well. But then you have

01:58:19.609 --> 01:58:25.090
a contra argument is that a lot of things integrate

01:58:25.090 --> 01:58:31.270
very well with systemd and it makes the systemd

01:58:31.270 --> 01:58:35.869
itself makes a lot of other programmers job easier

01:58:35.869 --> 01:58:39.270
because they can rely on systemd to do stuff

01:58:39.270 --> 01:58:45.649
for them for example if you would want let me

01:58:45.649 --> 01:58:49.829
give you a really stupid example i want to run

01:58:49.829 --> 01:58:54.649
emacs daemon automatically when i log into my

01:58:54.649 --> 01:59:01.789
computer and i just tell my user systemd part,

01:59:02.010 --> 01:59:05.850
please take care that my Emacs must be running

01:59:05.850 --> 01:59:09.350
at all times. I mean Emacs daemon. And it's very

01:59:09.350 --> 01:59:13.569
easy to configure. It's like one line. And systemd

01:59:13.569 --> 01:59:15.989
takes care that my Emacs daemon is always running.

01:59:16.390 --> 01:59:19.729
If I wouldn't have systemd, the alternative is

01:59:19.729 --> 01:59:24.210
to use the built -in daemon functionality of

01:59:24.210 --> 01:59:27.869
Emacs, which is basically run Emacs dash daemon.

01:59:29.149 --> 01:59:33.920
But If it crashes for any reason, you have to

01:59:33.920 --> 01:59:38.659
program it on your own to automatically restart.

01:59:39.159 --> 01:59:42.380
You have to make your own script for that or

01:59:42.380 --> 01:59:48.000
whatever. You have to take care of it. But with

01:59:48.000 --> 01:59:50.399
SystemD, you can just tell it, please make sure

01:59:50.399 --> 01:59:55.300
that this works. And it does. So it has its cons

01:59:55.300 --> 01:59:59.470
and pros. the majority of Linux distributions

01:59:59.470 --> 02:00:04.189
are heading towards using systemd and it is what

02:00:04.189 --> 02:00:09.310
it is. I wouldn't personally worry about it too

02:00:09.310 --> 02:00:15.890
much unless you really really want to keep Linux

02:00:15.890 --> 02:00:21.409
as rainbowy as possible and by rainbowy I mean

02:00:21.409 --> 02:00:26.729
all kinds of different solutions that do the

02:00:26.729 --> 02:00:30.050
same thing, so you have more choices in the matter.

02:00:30.829 --> 02:00:35.229
At the end of the day, if you just want to be

02:00:35.229 --> 02:00:38.470
a user and have your operating system out of

02:00:38.470 --> 02:00:43.850
your way, the best Linux distributions that do

02:00:43.850 --> 02:00:46.770
exactly that are the ones that we call stable

02:00:46.770 --> 02:00:50.630
Linux distributions, meaning those that tend

02:00:50.630 --> 02:00:56.840
to come out once in two years or up to once every

02:00:56.840 --> 02:01:01.520
half a year you know and the rolling ones will

02:01:01.520 --> 02:01:05.220
usually give you other benefits while at the

02:01:05.220 --> 02:01:09.420
same time keep you very entertained into fixing

02:01:09.420 --> 02:01:13.180
your computer and feeling like a hacker while

02:01:13.180 --> 02:01:17.300
at the same time losing a lot of time into fixing

02:01:17.300 --> 02:01:23.100
something that maybe should give you time to

02:01:23.100 --> 02:01:26.600
invest into something else and once again I will

02:01:26.600 --> 02:01:30.800
repeat it's not a bad thing but personally I

02:01:30.800 --> 02:01:36.020
have good experience with Linux and I don't need

02:01:36.020 --> 02:01:39.779
extra artificially induced problems with my computer

02:01:39.779 --> 02:01:43.859
other than those things that I break on purpose.

02:01:44.560 --> 02:01:46.779
because they want to break them and they want

02:01:46.779 --> 02:01:49.039
to see how they break and they want to see how

02:01:49.039 --> 02:01:51.680
they are to be fixed and this is how we learn

02:01:51.680 --> 02:01:56.539
things. Okay, okay. Makes sense. I want to ask

02:01:56.539 --> 02:02:02.619
you as well about some controversial distribution,

02:02:02.880 --> 02:02:05.340
we could call it that way. I had an interview

02:02:05.340 --> 02:02:10.079
recently with three other guys. Tony was one

02:02:10.079 --> 02:02:14.550
of them. Remisk, Joshua Blaze, they have YouTube

02:02:14.550 --> 02:02:17.409
channels, right? We touched on a point there

02:02:17.409 --> 02:02:20.329
about this distro. Have you heard about it? Omarchi?

02:02:21.050 --> 02:02:25.350
Tony doesn't like it. It's a current hype. Yeah,

02:02:25.369 --> 02:02:29.189
that's right. What are your thoughts on it? Have

02:02:29.189 --> 02:02:30.829
you used it? Do you have any thoughts, anything

02:02:30.829 --> 02:02:33.729
you want to share about it? Well, the guy who

02:02:33.729 --> 02:02:38.069
made it is a creator of Ruby on Rails, so it's

02:02:38.069 --> 02:02:43.930
a very popular figure. Don't think that he created

02:02:43.930 --> 02:02:47.869
this distribution to be used by a vast majority

02:02:47.869 --> 02:02:51.350
of people. I think he's making it for his own

02:02:51.350 --> 02:02:54.630
pleasure. That's how I see it. I think he's making

02:02:54.630 --> 02:02:57.810
it for his own pleasure. He calls it opinionated,

02:02:57.930 --> 02:03:01.229
but what it actually means, I configure it this

02:03:01.229 --> 02:03:03.310
way and everyone is going to use it this way

02:03:03.310 --> 02:03:08.359
because you will want to. My way is the best

02:03:08.359 --> 02:03:11.840
way. If you don't want my way, then feel free

02:03:11.840 --> 02:03:16.840
to use whatever else there is. But the way he

02:03:16.840 --> 02:03:21.220
designed it is like a lot of people who are unable

02:03:21.220 --> 02:03:24.140
to use Arch because they're not technically competent

02:03:24.140 --> 02:03:30.439
to read the Arch Wiki. Then they like to have

02:03:30.439 --> 02:03:32.819
something that is pre -configured out of the

02:03:32.819 --> 02:03:35.880
box. and it's basically the same for everyone

02:03:35.880 --> 02:03:41.859
and I have a couple of reasons why I will not

02:03:41.859 --> 02:03:45.399
use omarchi and these are not necessarily the

02:03:45.399 --> 02:03:49.720
reasons for other people. First, it is based

02:03:49.720 --> 02:03:52.579
on Arch Linux and I'm not saying that Arch is

02:03:52.579 --> 02:03:56.020
bad. I'm saying that everything that is based

02:03:56.020 --> 02:03:59.359
on Arch is bad. because i have no clue why it

02:03:59.359 --> 02:04:03.279
exists arch linux is an independent distribution

02:04:03.279 --> 02:04:07.899
a really good one if it suits your needs and

02:04:07.899 --> 02:04:10.560
from my point of view everything that is based

02:04:10.560 --> 02:04:13.960
on arch is just whatever i don't know why it

02:04:13.960 --> 02:04:16.659
exists like if you want to use arch use arch

02:04:16.659 --> 02:04:21.220
all of the other distributions that just attach

02:04:21.220 --> 02:04:25.579
themselves onto the arch package manager and

02:04:25.579 --> 02:04:29.949
onto the arch package maintainers is just like,

02:04:29.989 --> 02:04:36.810
now I'm going to say something really, really

02:04:36.810 --> 02:04:40.710
ugly. And I'm going to get a lot of hate for

02:04:40.710 --> 02:04:44.170
this, but I really want to say it in this way.

02:04:44.470 --> 02:04:52.069
You know what leeches do? So if you want to design

02:04:52.069 --> 02:04:56.789
your own Linux distribution, Why don't you do

02:04:56.789 --> 02:04:59.590
it properly? Your own package manager. Yeah,

02:04:59.630 --> 02:05:02.989
do everything from scratch. Be the man. Be the

02:05:02.989 --> 02:05:07.039
man. Do everything properly. and make an independent

02:05:07.039 --> 02:05:11.199
distribution and don't depend on Debian, don't

02:05:11.199 --> 02:05:14.060
depend on, you know, a lot of these distributions

02:05:14.060 --> 02:05:17.220
are like, I have tweaked the kernel a little

02:05:17.220 --> 02:05:20.180
bit. And that's that's a dig for the what's it

02:05:20.180 --> 02:05:23.119
called? Cache UIS. We have tweaked the kernel

02:05:23.119 --> 02:05:27.760
a little bit. So it's now 0 .5 % faster in video

02:05:27.760 --> 02:05:32.720
games. And we are now we are now very very good

02:05:32.720 --> 02:05:35.000
Linux distribution, but essentially we are just

02:05:35.000 --> 02:05:39.539
Arch Linux with a slightly modified kernel. Whatever,

02:05:39.720 --> 02:05:45.180
dude. A lot of other distributions are very similar

02:05:45.180 --> 02:05:49.340
in this way and I'm not saying they should stop

02:05:49.340 --> 02:05:53.100
existing. I'm only saying that I don't see the

02:05:53.100 --> 02:05:58.680
reason why I would use any of them. I like Debian

02:05:58.680 --> 02:06:01.800
for what it is. I do like Arch Linux for what

02:06:01.800 --> 02:06:04.739
it is. Don't get me wrong. I'm not an Arch hater.

02:06:04.840 --> 02:06:08.140
I really like it for what it is. But I don't

02:06:08.140 --> 02:06:12.399
see myself using it anymore. Then NixOS is really,

02:06:12.479 --> 02:06:16.399
really cool in its own way. But once again, I'm

02:06:16.399 --> 02:06:20.220
the one who doesn't see myself using it. Maybe

02:06:20.220 --> 02:06:22.180
I will change my mind. I don't know. But right

02:06:22.180 --> 02:06:26.399
now, I don't think I will. And there are a couple

02:06:26.399 --> 02:06:29.779
more like Fedora, Linux, really unique in its

02:06:29.779 --> 02:06:36.699
own way and stuff like that. So, I don't know.

02:06:36.779 --> 02:06:42.260
At the same time, I do recommend Zorin and I

02:06:42.260 --> 02:06:45.159
will explain this why. Zorin is based on Ubuntu

02:06:45.159 --> 02:06:51.819
and they don't change much, but they... tweak

02:06:51.819 --> 02:06:55.000
the default GNOME environment with their own

02:06:55.000 --> 02:06:58.680
skins that resemble Mac and Windows a lot. They

02:06:58.680 --> 02:07:01.680
have multiple skins you can pick and choose.

02:07:02.779 --> 02:07:07.300
This alone helps the newcomers from these two

02:07:07.300 --> 02:07:11.180
operating systems to feel slightly warmer like

02:07:11.180 --> 02:07:14.020
at home because it kind of looks like what they

02:07:14.020 --> 02:07:17.020
used to be using and I'm talking primarily about

02:07:17.020 --> 02:07:21.670
normal users. Okay, the normies. Normies, yes.

02:07:22.710 --> 02:07:26.989
Yeah, that's not a bad word. That's a word for

02:07:26.989 --> 02:07:29.510
people who want their computer to get the hell

02:07:29.510 --> 02:07:32.390
out of their way. They just want to use it, and

02:07:32.390 --> 02:07:37.810
they are used to... Zorin did a couple of things

02:07:37.810 --> 02:07:40.109
just right, in my opinion, and this is why I

02:07:40.109 --> 02:07:44.289
recommend it to the new people. When you're a

02:07:44.289 --> 02:07:48.010
new person coming from Windows, you're used to,

02:07:48.069 --> 02:07:52.609
like, I want OBS. let's see do you want OBS and

02:07:52.609 --> 02:07:55.609
the way that you have used to downloading OBS

02:07:55.609 --> 02:07:58.550
on Windows is you go to OBS website you click

02:07:58.550 --> 02:08:01.750
download and the OBS web page is stupid enough

02:08:01.750 --> 02:08:06.409
that it will offer you Windows version first

02:08:06.409 --> 02:08:10.329
and it will not automatically recognize what

02:08:10.329 --> 02:08:15.189
OS you are on and maybe by reflex you will click

02:08:15.189 --> 02:08:21.449
on the Windows button it will download obs .exe

02:08:21.449 --> 02:08:25.550
on your Zorin OS and you will run this icon.

02:08:25.670 --> 02:08:27.710
It looks like a normal Windows installer. You

02:08:27.710 --> 02:08:30.649
can run it and it pops up with a little message.

02:08:31.069 --> 02:08:34.170
This is what Zorin does. We have detected that

02:08:34.170 --> 02:08:37.069
you're trying to install OBS. We have a lot better

02:08:37.069 --> 02:08:41.520
place for you to install this in. on Linux, please

02:08:41.520 --> 02:08:44.079
click this button to take you to Linux store

02:08:44.079 --> 02:08:46.920
to install it properly like a native Linux package.

02:08:47.340 --> 02:08:52.100
It's a small text and the buttons are like...

02:08:53.850 --> 02:08:55.689
the highlighted button is the one that takes

02:08:55.689 --> 02:08:58.670
you to linux store and the non -highlighted button

02:08:58.670 --> 02:09:01.829
is no i know what i'm doing i want to install

02:09:01.829 --> 02:09:04.350
the windows version and if you install the windows

02:09:04.350 --> 02:09:07.670
version of obs then the windows compatibility

02:09:07.670 --> 02:09:13.310
layer fires out automatically and installs itself

02:09:13.310 --> 02:09:18.789
fully in a fully automated way and it works with

02:09:18.789 --> 02:09:22.710
windows binaries but generally Yeah, true wine,

02:09:22.890 --> 02:09:27.729
but it is so well automated by the Zorin team

02:09:27.729 --> 02:09:31.050
that you will not notice that this is wine. It's

02:09:31.050 --> 02:09:35.689
just, do you want to run this executable that

02:09:35.689 --> 02:09:38.829
is Windows? We can do that for you. And you click

02:09:38.829 --> 02:09:42.949
yes and it works. Of course, it still works as

02:09:42.949 --> 02:09:47.310
good as anything else works in wine. Zorin doesn't

02:09:47.310 --> 02:09:51.130
make wine work better. They only make it easier,

02:09:51.760 --> 02:09:56.399
to use because with raw wine you have to understand

02:09:56.399 --> 02:09:58.760
how the config files work and stuff like that

02:09:58.760 --> 02:10:04.439
with Zorin it is just pre -configured for a lot

02:10:04.439 --> 02:10:08.460
of different packages and when you click okay

02:10:08.460 --> 02:10:11.800
take me to the store it takes you to the like

02:10:11.800 --> 02:10:15.579
Zorin kind of a store, which is basically GNOME

02:10:15.579 --> 02:10:18.319
store, which basically hooks up to the flat hub

02:10:18.319 --> 02:10:24.359
and installs the typical latest version of containerized

02:10:24.359 --> 02:10:32.020
applications. It really serves the end user normie

02:10:32.020 --> 02:10:38.479
in a good way. And once this normie becomes very

02:10:38.479 --> 02:10:43.489
comfortable with Linux, most likely they will

02:10:43.489 --> 02:10:47.670
try other distributions and then they are ready

02:10:47.670 --> 02:10:52.189
to try them on their own. But as a new person

02:10:52.189 --> 02:10:57.090
coming towards me to ask for a question, I will

02:10:57.090 --> 02:11:00.770
never tell them to try Arch because they will

02:11:00.770 --> 02:11:04.270
hate me. And they will hate Linux and they will

02:11:04.270 --> 02:11:07.590
hate all of the YouTubers because I told them

02:11:07.590 --> 02:11:13.479
to use Arch. So it's not a good way to build

02:11:13.479 --> 02:11:16.899
Linux community. And I don't mean my community,

02:11:17.039 --> 02:11:19.600
I mean the whole Linux community. If you want

02:11:19.600 --> 02:11:23.460
new users, you have to help them with onboarding

02:11:23.460 --> 02:11:29.460
the best you can. And I would like to recommend

02:11:29.460 --> 02:11:33.439
Debian, but it's not that easy to install for

02:11:33.439 --> 02:11:37.500
a plain normie. Yeah, for a beginner. It's just

02:11:37.500 --> 02:11:43.869
not. And I can make all of the guides for that,

02:11:44.010 --> 02:11:48.390
but Zorin is just a lot easier. It's just literally

02:11:48.390 --> 02:11:50.850
next, next, next. What do you use on servers?

02:11:51.149 --> 02:11:55.449
Do you run any distro on your servers? Yeah,

02:11:55.489 --> 02:11:58.170
all of them are Debian. Okay, that's what I was

02:11:58.170 --> 02:12:01.649
thinking when I decided to, you know, do you

02:12:01.649 --> 02:12:03.609
use any hypervisor? Do you have a home lab or

02:12:03.609 --> 02:12:07.130
something or no? yeah yeah i i use uh the built

02:12:07.130 --> 02:12:13.630
-in hypervisor in the uh in linux okay the kvm

02:12:13.630 --> 02:12:17.069
in the kernel kernel uh what is it called kernel

02:12:17.069 --> 02:12:21.829
virtual machine okay okay okay um because i was

02:12:21.829 --> 02:12:24.449
thinking okay what should i use in all my servers

02:12:24.449 --> 02:12:27.029
and i was ubuntu is what you see everywhere but

02:12:27.029 --> 02:12:30.250
i was like but why am i going to go with this

02:12:30.960 --> 02:12:34.279
kid of Debian, why don't I go to the daddy directly?

02:12:34.600 --> 02:12:37.119
Why don't I go to the source? Is there a reason

02:12:37.119 --> 02:12:39.399
why people use Ubuntu on servers? I have been

02:12:39.399 --> 02:12:42.539
using Debian on servers for years and have installed,

02:12:42.840 --> 02:12:45.279
well, I installed Docker on them, Kubernetes,

02:12:45.520 --> 02:12:48.119
and I just run stuff in Docker and Kubernetes,

02:12:48.359 --> 02:12:51.279
right? Those host machines don't do much. Some

02:12:51.279 --> 02:12:54.420
of them do, right? I have my DNS servers on Debian,

02:12:54.539 --> 02:12:58.420
some cluster clusters as well. But why do people

02:12:58.420 --> 02:13:03.189
use... something other than Debian in servers,

02:13:03.550 --> 02:13:06.010
you know, when they could be using Debian? Well,

02:13:06.090 --> 02:13:12.090
for one thing, Ubuntu is the child of a company

02:13:12.090 --> 02:13:16.470
called Canonical. So the moment when we say company,

02:13:16.689 --> 02:13:25.289
there are some monetary goals. Okay, so the fact...

02:13:25.609 --> 02:13:29.130
Not marketing. The fact that Canonical is a company

02:13:29.130 --> 02:13:35.689
and they need money to exist. This is what gives

02:13:35.689 --> 02:13:39.890
you slight confidence that they will do everything

02:13:39.890 --> 02:13:46.390
in their power to keep that system good for selling.

02:13:47.170 --> 02:13:50.270
In the lack of a better way to express myself.

02:13:51.470 --> 02:13:56.579
People are sometimes wondering how come Debian

02:13:56.579 --> 02:14:00.960
comes out with a long -term support kernel and

02:14:00.960 --> 02:14:04.220
they stick to it because the upstream is giving

02:14:04.220 --> 02:14:07.319
them patches for this kernel for a long time,

02:14:07.420 --> 02:14:11.359
which is kind of logical. How come Ubuntu doesn't

02:14:11.359 --> 02:14:13.979
come with a long -term support kernel but they

02:14:13.979 --> 02:14:16.560
pick a random one which is not a long -term support

02:14:16.560 --> 02:14:20.319
kernel? The reason is very simple. The difference

02:14:20.319 --> 02:14:22.760
between long -term support kernel which comes

02:14:22.760 --> 02:14:26.399
out once per year in January or actually in December

02:14:26.399 --> 02:14:33.260
but at the switch of the year. The reason why

02:14:33.260 --> 02:14:40.939
Ubuntu uses the random latest kernel is because

02:14:40.939 --> 02:14:43.760
there is no difference between the LTS one and

02:14:43.760 --> 02:14:46.279
the latest one except the latest one has the

02:14:46.279 --> 02:14:50.750
latest drivers. and canonical has their own kernel

02:14:50.750 --> 02:14:56.329
developers who maintain this version of kernel

02:14:56.329 --> 02:15:02.029
on their own so it may not be officially called

02:15:02.029 --> 02:15:04.430
the long -term support kernel but technically

02:15:04.430 --> 02:15:08.689
it's actually supported longer the one in ubuntu

02:15:08.689 --> 02:15:12.710
lts is actually supported for longer than the

02:15:12.710 --> 02:15:18.220
one that linux upstream considers long -term

02:15:18.220 --> 02:15:21.220
support kernel because i don't know by heart

02:15:21.220 --> 02:15:25.560
i think right now the lts kernel officially is

02:15:25.560 --> 02:15:29.939
supported for three years someone correct me

02:15:29.939 --> 02:15:31.859
if i'm wrong but i think it's three years now

02:15:31.859 --> 02:15:38.539
the latest information while the ubuntu lts that

02:15:38.539 --> 02:15:43.199
doesn't even ship with lts kernel is giving support

02:15:43.199 --> 02:15:51.710
for 10 years So they do patch your kernel for

02:15:51.710 --> 02:15:54.529
a very long time. They do it themselves. They

02:15:54.529 --> 02:15:57.890
have the manpower to do that. They have people

02:15:57.890 --> 02:16:02.550
on payroll that do these things. So Debian team,

02:16:02.649 --> 02:16:05.189
on the other hand, they can use their resources

02:16:05.189 --> 02:16:12.529
a lot better by bringing more packages, taking

02:16:12.529 --> 02:16:15.439
care that everything is... properly polished

02:16:15.439 --> 02:16:17.479
and stuff like that and they leave the kernel

02:16:17.479 --> 02:16:21.600
stuff to the kernel people so from that perspective

02:16:21.600 --> 02:16:26.380
you could get like longer support if that's something

02:16:26.380 --> 02:16:29.800
that you would care about i don't know personally

02:16:29.800 --> 02:16:32.700
i just switched to the next debian system once

02:16:32.700 --> 02:16:35.500
this one is finished what do you do do you install

02:16:35.500 --> 02:16:38.260
it from scratch or you just sometimes depending

02:16:38.260 --> 02:16:42.639
on what i do sometimes i upgrade if i if i don't

02:16:42.639 --> 02:16:46.870
see any problems on my server and sometimes it

02:16:46.870 --> 02:16:51.010
happens that over time I did some experiments

02:16:51.010 --> 02:16:54.250
and I kind of feel like I want to go clean and

02:16:54.250 --> 02:16:58.649
I reinstall everything. It depends on how I feel

02:16:58.649 --> 02:17:02.670
about this particular machine when the time comes,

02:17:02.709 --> 02:17:07.450
right? So my main server is running Debian 12,

02:17:07.729 --> 02:17:11.829
although Debian 13 has come out four months ago.

02:17:12.489 --> 02:17:16.530
But there is no reason why I would have to upgrade

02:17:16.530 --> 02:17:21.110
because my Debian 12 main server still does everything

02:17:21.110 --> 02:17:25.030
in the same way that Debian 13 would do for me.

02:17:25.110 --> 02:17:29.290
And it's still fully supported. So I have still

02:17:29.290 --> 02:17:34.110
time to transition to the Debian 13. And not

02:17:34.110 --> 02:17:39.870
transitioning day one gives me less potential

02:17:39.870 --> 02:17:43.569
headaches. with day one releases so i'm that

02:17:43.569 --> 02:17:47.389
kind of a stable users user i want my servers

02:17:47.389 --> 02:17:54.069
to never go down because of my thirst for the

02:17:54.069 --> 02:17:58.149
latest and greatest now if they go down do you

02:17:58.149 --> 02:18:00.069
have a rule to upgrade or something because i'm

02:18:00.069 --> 02:18:02.549
also on deviant 12 on this server and i have

02:18:02.549 --> 02:18:05.250
not even updated not even packages for a long

02:18:05.250 --> 02:18:07.229
time and that's also another thing that i want

02:18:07.229 --> 02:18:10.040
to ask you about unattended upgrades i don't

02:18:10.040 --> 02:18:12.579
remember but i heard drew mention something about

02:18:12.579 --> 02:18:15.719
that you know but two questions yeah do you have

02:18:15.719 --> 02:18:18.459
a rule like okay so i'm gonna update this year

02:18:18.459 --> 02:18:22.760
or this month every year or every few years and

02:18:22.760 --> 02:18:24.959
what are your thoughts on automatic security

02:18:24.959 --> 02:18:29.860
updates oh security updates you you should update

02:18:29.860 --> 02:18:36.059
them as soon as possible but depends on what

02:18:36.059 --> 02:18:42.129
your server is doing The servers that are exposed

02:18:42.129 --> 02:18:47.489
publicly, and I have some, these guys I patch

02:18:47.489 --> 02:18:50.569
all the time. Like all the time. Makes sense.

02:18:50.690 --> 02:18:55.930
All the time. The reboot don't matter. If there

02:18:55.930 --> 02:18:59.430
is a new kernel that's patched, I just install

02:18:59.430 --> 02:19:03.420
it. fairly immediately and reboot because that's

02:19:03.420 --> 02:19:05.879
what you need to do. And is that done automatically

02:19:05.879 --> 02:19:08.879
or you do it manually? No, manually. Always manually

02:19:08.879 --> 02:19:16.520
because I don't trust anything automated because

02:19:16.520 --> 02:19:21.799
if other people depend on this server being up

02:19:21.799 --> 02:19:26.020
and running and the server updates itself on

02:19:26.020 --> 02:19:30.090
its own and something bad happens, Even if it's

02:19:30.090 --> 02:19:32.510
a little problem, but it's still a problem that

02:19:32.510 --> 02:19:38.989
users notice. And I'm away, completely detached

02:19:38.989 --> 02:19:43.809
from any computer access. That's bad. So I time

02:19:43.809 --> 02:19:47.930
my updates for everything that I host in public

02:19:47.930 --> 02:19:55.170
to when I will be able to deal with it for a

02:19:55.170 --> 02:19:59.190
while. I give myself time. But I do have a lot

02:19:59.190 --> 02:20:01.870
of servers on my home lab that are behind the

02:20:01.870 --> 02:20:05.930
firewall that don't really need to be updated

02:20:05.930 --> 02:20:08.010
all the time because people just can't reach

02:20:08.010 --> 02:20:11.950
them. Is there something you want to demo on

02:20:11.950 --> 02:20:14.250
your side? Do you want to demo your workflow

02:20:14.250 --> 02:20:20.209
or something? To be honest, I don't think I have

02:20:20.209 --> 02:20:23.229
anything meaningful to show on this particular

02:20:23.229 --> 02:20:27.389
computer. My desktop computer, as I said, was...

02:20:28.039 --> 02:20:30.620
reinstalled with debian and ever since i got

02:20:30.620 --> 02:20:34.100
back to debian i didn't really fill it up with

02:20:34.100 --> 02:20:37.739
anything that would feel like nonsense it just

02:20:37.739 --> 02:20:42.620
does what it needs to do you can switch to my

02:20:42.620 --> 02:20:46.649
screen But it is going to be a little bit boring.

02:20:46.829 --> 02:20:50.590
So this is the default wallpaper that comes with

02:20:50.590 --> 02:20:52.870
KDE Plasma. And I haven't changed this from day

02:20:52.870 --> 02:20:56.110
one. And the reason why I haven't changed the

02:20:56.110 --> 02:20:59.030
wallpaper is because I never see it except now.

02:20:59.889 --> 02:21:04.670
I am always in this mode or in similar modes.

02:21:05.209 --> 02:21:09.729
And usually the wallpaper is covered. So I don't

02:21:09.729 --> 02:21:12.770
see the point of a wallpaper. So I just leave

02:21:12.770 --> 02:21:18.079
it be. There is the GIMP software. You use DaVinci.

02:21:18.280 --> 02:21:21.040
That's what I use on Mac OS. Yeah, I'm going

02:21:21.040 --> 02:21:23.840
to come to that in a moment. I was going to go

02:21:23.840 --> 02:21:26.819
through all of the icons randomly. Basically,

02:21:26.840 --> 02:21:32.319
this is the way I do my thumbnails. It's nothing

02:21:32.319 --> 02:21:36.360
special. You have these layers and I just put

02:21:36.360 --> 02:21:40.090
them around and whatever, you know. I do some

02:21:40.090 --> 02:21:43.370
effects, shadows, whatever. That's GIMP. I don't

02:21:43.370 --> 02:21:53.750
use it to a very deep degree, so to speak. Someone

02:21:53.750 --> 02:21:59.049
noticed on your stream that I have Visual Studio

02:21:59.049 --> 02:22:02.469
Kodium installed. The reason why I have Kodium,

02:22:02.590 --> 02:22:06.430
although Visual Studio Code is also free and

02:22:06.430 --> 02:22:11.120
open source, but the binary distributed version

02:22:11.120 --> 02:22:15.260
of Visual Studio Code has a lot of telemetry

02:22:15.260 --> 02:22:19.739
in there. And once again, it's not like I'm hiding

02:22:19.739 --> 02:22:24.120
any secrets. It's just that it's none of Microsoft

02:22:24.120 --> 02:22:28.959
business what I'm doing on my computer. And this

02:22:28.959 --> 02:22:34.500
is why Visual Studio Code. And I don't actually

02:22:36.010 --> 02:22:39.110
code much in this. The reason why I have Kodium

02:22:39.110 --> 02:22:42.850
is only for one reason and that is because I

02:22:42.850 --> 02:22:45.989
was trying to learn how to code in Assembler

02:22:45.989 --> 02:22:52.030
and the Kodium or Visual Studio Code has this

02:22:52.030 --> 02:22:56.770
extension called Amiga assembly and this extension

02:22:56.770 --> 02:23:03.909
knows how to code in Assembler for Amiga and

02:23:03.909 --> 02:23:06.930
it gives me some color highlights. It gives me

02:23:06.930 --> 02:23:12.950
back to some of the code. When you highlight

02:23:12.950 --> 02:23:16.850
anything or just hover, it tells you how this

02:23:16.850 --> 02:23:19.989
command works and what it does. So it's a little

02:23:19.989 --> 02:23:22.309
bit easier to remember and stuff like that. I

02:23:22.309 --> 02:23:24.610
can't really do that in Vim or Emacs or anything

02:23:24.610 --> 02:23:28.030
like that. I need this particular extension that

02:23:28.030 --> 02:23:32.659
helps me to learn faster. And that's the only

02:23:32.659 --> 02:23:36.760
reason why I use Visual Studio Code or Kodium,

02:23:36.840 --> 02:23:41.420
whatever you want to call it. And there is my

02:23:41.420 --> 02:23:46.959
virtual machine manager. It needs my password.

02:23:47.860 --> 02:23:52.299
And this is one of my servers, which I have in

02:23:52.299 --> 02:23:57.040
my home lab. So these are the virtual machines

02:23:57.040 --> 02:24:01.059
that are running on what I... like to call my

02:24:01.059 --> 02:24:03.420
main server, and my main server looks exactly

02:24:03.420 --> 02:24:05.700
the same as your computer that you had in your

02:24:05.700 --> 02:24:10.659
hands a couple of minutes ago. It has 4 terabytes

02:24:10.659 --> 02:24:18.899
SSD and 32 gigs of RAM. The tiny Lenovo, right?

02:24:19.000 --> 02:24:25.120
Yeah, the micro ones. Yeah, tiny. M720. And on

02:24:25.120 --> 02:24:29.280
it I have the backup. software running as one

02:24:29.280 --> 02:24:32.379
virtual machine. I have my next cloud running

02:24:32.379 --> 02:24:35.620
as a separate virtual machine. I have my Pi Hall

02:24:35.620 --> 02:24:39.280
running as a third machine. I have my home assistant

02:24:39.280 --> 02:24:44.239
for some home automation as a separate virtual

02:24:44.239 --> 02:24:47.459
machine. This is Jellyfin for watching movies.

02:24:48.459 --> 02:24:53.120
This is some of my experiments. Well, it kind

02:24:53.120 --> 02:24:56.079
of became my main web server actually if you

02:24:56.079 --> 02:25:00.780
go to uh well let me show you this like boss

02:25:00.780 --> 02:25:04.979
headquarters this is my like a new brand uh i'm

02:25:04.979 --> 02:25:08.000
trying to hook up you notice this on matrix i

02:25:08.000 --> 02:25:11.379
have this name so linux renaissance is like my

02:25:11.379 --> 02:25:13.799
youtube channel and everything else that i do

02:25:13.799 --> 02:25:19.479
will be attached to this name So I have a matrix

02:25:19.479 --> 02:25:24.120
server that runs on this domain. I have some

02:25:24.120 --> 02:25:29.139
other services that run on this domain. I have

02:25:29.139 --> 02:25:34.760
started the quiz thing. I don't know if you have

02:25:34.760 --> 02:25:38.280
seen it. No, I haven't. Yeah, last week was the

02:25:38.280 --> 02:25:41.459
first or the pilot episode or the episode zero.

02:25:42.219 --> 02:25:44.559
I have hired the first contestant. It feels a

02:25:44.559 --> 02:25:46.280
little bit like who wants to be a millionaire,

02:25:46.459 --> 02:25:50.639
but with a twist and different rules and with

02:25:50.639 --> 02:25:55.719
Linux questions. And this guy was on the show

02:25:55.719 --> 02:25:58.379
and he scored some points and stuff like that.

02:25:59.280 --> 02:26:05.100
This is also like attached to to this FOSS headquarters

02:26:05.100 --> 02:26:08.120
brand and I have a lot of other plans that I'm

02:26:08.120 --> 02:26:10.219
going to attach to this brand. But generally

02:26:10.219 --> 02:26:13.819
the page that I have just loaded is loading from

02:26:13.819 --> 02:26:19.020
this light http demon on this virtual machine

02:26:19.020 --> 02:26:26.200
and this is a Debian SID installation. SID is

02:26:26.200 --> 02:26:29.500
the like a rolling release of Debian. Is there

02:26:29.500 --> 02:26:35.100
a reason for that? Yeah, on Sundays I keep Linux

02:26:35.100 --> 02:26:39.219
classrooms and I teach people Linux under the

02:26:39.219 --> 02:26:44.399
hood live on stream. And we usually use the rolling

02:26:44.399 --> 02:26:47.000
distribution for that because it kind of gives

02:26:47.000 --> 02:26:52.219
us the insight into new and shiny stuff. But

02:26:52.219 --> 02:26:57.100
I still like it to be Debian, so that's why it's

02:26:57.100 --> 02:27:01.809
Sid. My Matrix server is also running on this

02:27:01.809 --> 02:27:07.030
little tiny machine. This is my Minecraft server,

02:27:07.270 --> 02:27:10.049
the video game, which is currently not running

02:27:10.049 --> 02:27:12.069
because I haven't played it for a while. So it's

02:27:12.069 --> 02:27:15.510
just taking up RAM for no reason. And this one

02:27:15.510 --> 02:27:18.010
as well, I was testing OpenBSD for a while on

02:27:18.010 --> 02:27:21.190
the VM, but now I'm using it actually on my laptop,

02:27:21.290 --> 02:27:24.750
so I don't need this one. And this is my PeerTube.

02:27:25.360 --> 02:27:28.940
running here so there is a whole bunch of stuff

02:27:28.940 --> 02:27:35.340
running on just one server this is my youtube

02:27:35.340 --> 02:27:40.360
basically i have like a mirror of my youtube

02:27:40.360 --> 02:27:43.600
channel which you can watch on this domain without

02:27:43.600 --> 02:27:49.280
any ads or nagware or like with full privacy

02:27:49.280 --> 02:27:53.850
respecting I just don't know who watches this.

02:27:54.049 --> 02:27:57.809
The only thing that I know is that views go up

02:27:57.809 --> 02:28:00.270
and that's all. I have no clue who watches it,

02:28:00.370 --> 02:28:04.870
where do they come from or whatever. I just have

02:28:04.870 --> 02:28:09.170
these views go up and down and I'm pretty satisfied

02:28:09.170 --> 02:28:12.850
with that because there are obviously, if you

02:28:12.850 --> 02:28:15.250
can see from views, there are obviously some

02:28:15.250 --> 02:28:18.530
users that prefer to watch my stuff in this way

02:28:18.530 --> 02:28:22.260
rather than on YouTube. And I do respect that

02:28:22.260 --> 02:28:25.719
a lot. And I absolutely feel the need to have

02:28:25.719 --> 02:28:30.020
this option for them. So, you know, sometimes

02:28:30.020 --> 02:28:33.979
it's like 14 views, sometimes it's 150. It is

02:28:33.979 --> 02:28:37.219
what it is. Okay. And what do you use for your

02:28:37.219 --> 02:28:41.200
terminal? And also, are you a Neovim or Emacs

02:28:41.200 --> 02:28:44.739
person? Well, I think Emacs, but... Yeah, yeah.

02:28:45.059 --> 02:28:49.680
For the terminal in KD, I just use the built

02:28:49.680 --> 02:28:55.409
-in one. the console any thoughts on kitty and

02:28:55.409 --> 02:29:00.129
ghosty in western neo fetch i don't have any

02:29:00.129 --> 02:29:03.989
fetch software installed i think uh do i have

02:29:03.989 --> 02:29:10.370
no fast fetch then yeah you see how cool or uncool

02:29:10.370 --> 02:29:13.270
i am i don't even have fast fetch fast fetch

02:29:13.270 --> 02:29:17.190
uh that's for kids i have it but just yeah i

02:29:17.190 --> 02:29:20.739
know i know Yeah, I have it too. Okay, so now

02:29:20.739 --> 02:29:24.020
you see my computer here. Actually, let's make

02:29:24.020 --> 02:29:29.340
it bigger. So now it's nicer. Well, that's my

02:29:29.340 --> 02:29:32.719
main computer. And the reason why I use Konsole

02:29:32.719 --> 02:29:35.719
is because Konsole comes pre -installed with

02:29:35.719 --> 02:29:41.459
KDE. It fits into the KDE visual design language.

02:29:42.459 --> 02:29:45.219
Technically it does everything that I expect

02:29:45.219 --> 02:29:48.280
from a terminal emulator, so there is literally

02:29:48.280 --> 02:29:51.639
no reason why I should even try to switch to

02:29:51.639 --> 02:29:56.000
anything else. Except for when I was trying Hyperland.

02:29:56.780 --> 02:30:01.319
Hyperland by default has a small dependency on

02:30:01.319 --> 02:30:07.319
kitty, the terminal emulator called kitty, and

02:30:07.319 --> 02:30:11.260
then I had to install kitty out of curiosity.

02:30:11.959 --> 02:30:15.079
to see why is it a dependency in the default

02:30:15.079 --> 02:30:19.079
configuration of Hyperland and it kind of felt

02:30:19.079 --> 02:30:22.219
neat. I used it for a while and when I got back

02:30:22.219 --> 02:30:25.680
to KDE I literally just forgot about KDE because

02:30:25.680 --> 02:30:32.020
it does have some neat features but I don't really

02:30:32.020 --> 02:30:37.549
care. Nothing that would change my life in any

02:30:37.549 --> 02:30:41.489
meaningful way. And even on my laptop where I

02:30:41.489 --> 02:30:45.309
use OpenBSD now, there I have ST installed, the

02:30:45.309 --> 02:30:49.309
Suckless terminal, or simple terminal if you

02:30:49.309 --> 02:30:54.229
want. Do you know about Suckless? I have seen

02:30:54.229 --> 02:30:56.610
it in videos, but I don't understand what it

02:30:56.610 --> 02:31:01.899
is. Well, you always have... in the free software

02:31:01.899 --> 02:31:05.620
community you have all kinds of users and there

02:31:05.620 --> 02:31:12.319
is a solid group of people who like to use minimal

02:31:12.319 --> 02:31:16.500
software in a way that it uses the minimal amount

02:31:16.500 --> 02:31:23.540
of bloat in their opinion and it takes up very

02:31:23.540 --> 02:31:28.350
little resources you can view this as a good

02:31:28.350 --> 02:31:31.590
or bad thing depending on how you view things

02:31:31.590 --> 02:31:35.069
in software, but generally what Sackless software

02:31:35.069 --> 02:31:39.110
is, as one of your viewers said in chat, they

02:31:39.110 --> 02:31:46.129
make everything really small, but just enough

02:31:46.129 --> 02:31:50.250
so that it does the job. So, for example, the

02:31:50.250 --> 02:31:53.409
Sackless terminal that I use on OpenBSD is 100

02:31:53.409 --> 02:31:56.559
kilobytes. and it does everything it does everything

02:31:56.559 --> 02:32:05.659
that it needs to do so one of their main things

02:32:05.659 --> 02:32:08.120
that they do they don't have configuration files

02:32:08.120 --> 02:32:11.239
for anything the way you configure their software

02:32:11.239 --> 02:32:14.020
is by downloading source code editing the config

02:32:14.020 --> 02:32:18.420
.h file and changing some parameters there and

02:32:18.420 --> 02:32:21.200
then recompiling and deploying your binary on

02:32:21.200 --> 02:32:24.100
your own. That's one way to configure it. And

02:32:24.100 --> 02:32:26.379
another way to configure their software is if

02:32:26.379 --> 02:32:29.680
something is missing, then you need to program

02:32:29.680 --> 02:32:33.959
the missing functionality on your own. You lost

02:32:33.959 --> 02:32:38.200
me there already. Not interested. So that's how

02:32:38.200 --> 02:32:43.280
it works. They do have a lot of patches. For

02:32:43.280 --> 02:32:47.610
example, their window manager. I also use their

02:32:47.610 --> 02:32:50.889
window manager at the moment on my OpenBSD and

02:32:50.889 --> 02:32:54.989
I'm gonna explain that one. You have customization

02:32:54.989 --> 02:33:04.610
patches. So for the patches you have like shitload

02:33:04.610 --> 02:33:08.409
of patches provided by other people. They add

02:33:08.409 --> 02:33:11.969
a bunch of different functionalities so you can

02:33:11.969 --> 02:33:17.299
actually avoid being a programmer and just apply

02:33:17.299 --> 02:33:19.360
other people's patches that add functionality.

02:33:19.719 --> 02:33:22.420
This is what Drew was talking about. Drew from

02:33:22.420 --> 02:33:25.100
the Linux cast, just the guy Linux, because he

02:33:25.100 --> 02:33:28.120
uses the WM and he mentioned patches and I was

02:33:28.120 --> 02:33:32.680
like, what? Okay, I get it. Okay. Yeah, it doesn't

02:33:32.680 --> 02:33:34.899
have to be a thing for everyone. I'm just explaining

02:33:34.899 --> 02:33:40.639
how it is. One of the things that is very specific

02:33:40.639 --> 02:33:45.440
for the whole Suckless group of programmers is

02:33:45.440 --> 02:33:49.819
this part here. Because DWM, the window manager,

02:33:49.979 --> 02:33:52.760
is customized through editing its source code,

02:33:52.879 --> 02:33:56.360
it is pointless to make binary packages of it.

02:33:56.479 --> 02:34:01.280
This keeps its user base small and elitist. No

02:34:01.280 --> 02:34:04.590
novices asking stupid questions. I like that,

02:34:04.709 --> 02:34:12.489
okay. Yeah, how Gen Z would say they are based.

02:34:13.610 --> 02:34:18.569
So they are very direct, honest, and you either

02:34:18.569 --> 02:34:24.290
love them or hate them. Personally, on my Linux,

02:34:24.430 --> 02:34:29.229
I use a very bloated... desktop environment the

02:34:29.229 --> 02:34:34.149
KDE Plasma and I say bloated in a funny way because

02:34:34.149 --> 02:34:39.969
I don't really mean it but I do. I mean the KDE

02:34:39.969 --> 02:34:42.790
Plasma has a gazillion of features and I kind

02:34:42.790 --> 02:34:47.290
of enjoy having a gazillion of features because

02:34:47.290 --> 02:34:51.930
it feels like a professional operating system.

02:34:52.209 --> 02:34:58.340
It has everything. And a lot of people dislike

02:34:58.340 --> 02:35:03.899
this. They will not go even near KDE Plasma.

02:35:04.040 --> 02:35:08.639
So Linux is like that. It offers a lot of choices.

02:35:09.819 --> 02:35:15.260
However, the reason why I tried the DWM Window

02:35:15.260 --> 02:35:18.850
Manager... This one, yeah, is because I am currently

02:35:18.850 --> 02:35:22.190
testing OpenBSD on the laptop and I'm trying

02:35:22.190 --> 02:35:26.489
to see how it feels to use OpenBSD as my daily

02:35:26.489 --> 02:35:29.409
laptop driver. It cannot be my daily driver on

02:35:29.409 --> 02:35:32.170
my main machine because it's a little bit difficult

02:35:32.170 --> 02:35:36.469
to get everything that I need like streaming,

02:35:36.690 --> 02:35:40.590
OBS, graphics and everything. It's a bit difficult

02:35:40.590 --> 02:35:45.299
to get there but I do enjoy the feeling which

02:35:45.299 --> 02:35:49.620
is very reminiscent of using Linux for the first

02:35:49.620 --> 02:35:55.280
time. That's how OpenBSD feels very raw and minimal

02:35:55.280 --> 02:35:59.899
and just by the fact that it feels so minimal

02:35:59.899 --> 02:36:04.219
it gives me this desire to use it as minimal

02:36:04.219 --> 02:36:07.520
as possible on top of the base operating system.

02:36:07.799 --> 02:36:11.489
So I tried a couple of window managers all of

02:36:11.489 --> 02:36:16.129
them are fairly minimal and when I tried DWM

02:36:16.129 --> 02:36:20.610
first it felt really stupid that I have to recompile

02:36:20.610 --> 02:36:24.170
it all the time and then I tried to use it a

02:36:24.170 --> 02:36:27.090
little bit in its default state without modifying

02:36:27.090 --> 02:36:30.950
anything and it felt very much like Hyperland

02:36:30.950 --> 02:36:35.530
which I actually liked without the eye candy

02:36:35.530 --> 02:36:39.049
and eye candy is not something that I really

02:36:39.049 --> 02:36:43.629
need So it kind of started feeling like DWM might

02:36:43.629 --> 02:36:47.190
be good for me to use on OpenBSD, but then there

02:36:47.190 --> 02:36:50.389
is this recompilation and shit like that. And

02:36:50.389 --> 02:36:53.610
then I made a script, a very small one, that

02:36:53.610 --> 02:37:00.129
says while true loop reload DWM. And basically

02:37:00.129 --> 02:37:04.870
I just edit the source code when I want to edit

02:37:04.870 --> 02:37:09.110
some config files. And I just type make. And

02:37:09.110 --> 02:37:14.670
it recompiles in three seconds or so the entire

02:37:14.670 --> 02:37:20.729
window manager. And I just kill it literally

02:37:20.729 --> 02:37:23.329
with a key combination. I kill the window manager

02:37:23.329 --> 02:37:26.290
and it reloads in half a second back. Like you

02:37:26.290 --> 02:37:30.209
see a dark picture for split second and it comes

02:37:30.209 --> 02:37:33.809
back because my background script reloads it.

02:37:34.479 --> 02:37:40.659
And it feels like you have dynamically loading

02:37:40.659 --> 02:37:46.620
your config file. It was very easy to get it

02:37:46.620 --> 02:37:48.760
to this state because the software is so small

02:37:48.760 --> 02:37:52.059
that you can recompile it so fast. It kind of

02:37:52.059 --> 02:37:55.579
started feeling usable and I started reconfiguring

02:37:55.579 --> 02:37:59.579
my shortcuts. And funny enough, I don't use default

02:37:59.579 --> 02:38:03.899
DWM shortcuts. I use default HyperLens shortcuts

02:38:03.899 --> 02:38:08.280
in DWM because HyperLens is the one that taught

02:38:08.280 --> 02:38:11.040
me these shortcuts and now I have to stick with

02:38:11.040 --> 02:38:15.719
those. It kind of went into my finger memory,

02:38:15.940 --> 02:38:23.049
muscle memory. Then I discovered Peacom. Oh,

02:38:23.069 --> 02:38:27.069
yeah. Drew talked about that as well. Yeah, Peacom,

02:38:27.069 --> 02:38:31.090
right? Yes. And Peacom basically adds all of

02:38:31.090 --> 02:38:34.430
the missing eye candy from DWM that Hyperland

02:38:34.430 --> 02:38:40.930
has. So now I have almost Hyperland experience

02:38:40.930 --> 02:38:44.969
with two pieces of software that together are

02:38:44.969 --> 02:38:50.209
like... Not even a megabyte, I think. Maybe I

02:38:50.209 --> 02:38:53.549
am wrong about the file size, but I'm sure it's

02:38:53.549 --> 02:38:57.629
very small. So that's kind of interesting. That's

02:38:57.629 --> 02:39:03.489
my other story with currently trying to learn

02:39:03.489 --> 02:39:06.909
everything that I can about OpenBSD. This is

02:39:06.909 --> 02:39:10.190
kind of a new passion. I have a question about

02:39:10.190 --> 02:39:12.989
that open BSD, free BSD. What's the difference

02:39:12.989 --> 02:39:16.829
and why did you decide to go there? Like, okay,

02:39:16.969 --> 02:39:20.270
does it take a lot of your time? Don't you feel

02:39:20.270 --> 02:39:23.649
like, man? It does. Yep. It does. But all my

02:39:23.649 --> 02:39:28.329
free time that I invest in my hobbies are...

02:39:28.569 --> 02:39:31.350
equally distributed and it doesn't matter if

02:39:31.350 --> 02:39:34.969
I'm working on Linux or on OpenBSD. Both of them

02:39:34.969 --> 02:39:38.850
are my hobby and they bring me joy and I love

02:39:38.850 --> 02:39:42.290
to share what I learned and other people come

02:39:42.290 --> 02:39:45.430
to me and tell me like, oh, you're using BSD.

02:39:45.569 --> 02:39:49.110
I also like BSD. And have you tried something?

02:39:49.290 --> 02:39:51.610
And I say, no, I have no clue. Show it to me

02:39:51.610 --> 02:39:54.889
and then the conversation starts. And I was also

02:39:54.889 --> 02:39:59.770
on a physical BSD conference. like a couple of

02:39:59.770 --> 02:40:02.270
weeks ago and I met a lot of people there and

02:40:02.270 --> 02:40:06.069
that was kind of awesome because I have had I

02:40:06.069 --> 02:40:08.889
don't know if it's still on my table when you

02:40:08.889 --> 02:40:12.010
go to a conference you get a paper tag on your

02:40:12.010 --> 02:40:16.469
neck with your name and stuff and my name was

02:40:16.469 --> 02:40:20.450
Linux Renaissance on a BSD conference and a lot

02:40:20.450 --> 02:40:25.180
of people thought that I'm trolling and they

02:40:25.180 --> 02:40:31.840
learned what that means. But it was a nice experience.

02:40:32.100 --> 02:40:36.739
But you asked about the difference. The Berkeley

02:40:36.739 --> 02:40:40.879
Software Distribution is the name of a very old

02:40:40.879 --> 02:40:47.379
Unix system, BSD. And at one point people made

02:40:47.379 --> 02:40:53.280
it free by making derivatives of this old Unix

02:40:53.280 --> 02:40:58.799
system. called FreeBSD and then came NetBSD or

02:40:58.799 --> 02:41:03.040
maybe it was the other way around and then people

02:41:03.040 --> 02:41:06.959
who were working on NetBSD came to a disagreement

02:41:06.959 --> 02:41:12.180
so out of NetBSD came OpenBSD and now we have

02:41:12.180 --> 02:41:16.440
three versions of BSDs which are totally unlike

02:41:16.440 --> 02:41:19.579
Linux distributions which use the exact same

02:41:19.579 --> 02:41:23.319
kernel, the exact same userland. BSDs, however,

02:41:23.520 --> 02:41:26.200
they each develop their own kernels, which are

02:41:26.200 --> 02:41:29.139
totally different from each other. They develop

02:41:29.139 --> 02:41:37.680
their own user -land based software. They are

02:41:37.680 --> 02:41:41.079
different, but same. They are same in philosophy,

02:41:41.340 --> 02:41:45.959
but they are generally not compatible in any

02:41:45.959 --> 02:41:50.850
way in terms of binary. However, the unix being

02:41:50.850 --> 02:41:54.209
unix you can pre -compile stuff that works on

02:41:54.209 --> 02:41:57.270
linux on bsd and the other bsd so that's not

02:41:57.270 --> 02:42:03.610
really a problem so in short freebsd kind of

02:42:03.610 --> 02:42:06.969
feels the most ready for the desktop because

02:42:06.969 --> 02:42:10.549
they invest a lot of effort into developing speed

02:42:10.549 --> 02:42:15.909
operating system being snappy they invest a lot

02:42:15.909 --> 02:42:20.290
in modern desktops fully functional including

02:42:20.290 --> 02:42:23.950
the Wayland that was kind of invented on Linux

02:42:23.950 --> 02:42:29.649
but FreeBSD is afraid that they will be left

02:42:29.649 --> 02:42:32.709
behind if they don't embrace the latest and greatest

02:42:32.709 --> 02:42:37.069
on Linux in terms of desktop environments and

02:42:37.069 --> 02:42:41.930
how it works. So the first one that has usable

02:42:41.930 --> 02:42:46.670
Wayland experience is FreeBSD. Then we have NetBSD,

02:42:46.809 --> 02:42:50.250
which is the version of BSD that works on any

02:42:50.250 --> 02:42:54.409
imaginable hardware in the universe, literally.

02:42:54.790 --> 02:43:00.329
The very latest version of NetBSD works on my

02:43:00.329 --> 02:43:04.629
35 -year -old Amiga computer. So that's how much

02:43:04.629 --> 02:43:07.690
they care about working on every piece of hardware

02:43:07.690 --> 02:43:13.040
in existence. That's their main goal. They are

02:43:13.040 --> 02:43:16.899
also quite good in being a networking, let's

02:43:16.899 --> 02:43:21.700
say, internet server, but a bit raw, like an

02:43:21.700 --> 02:43:27.639
old Unix server. OpenBSD is having a totally

02:43:27.639 --> 02:43:29.860
different philosophy and I think that's why they

02:43:29.860 --> 02:43:35.000
split from NetBSD. Their goal is to be the most

02:43:35.000 --> 02:43:38.299
secure operating system in the world and they

02:43:38.299 --> 02:43:44.010
are trying very hard to do that. So they have

02:43:44.010 --> 02:43:48.530
a very bold claim that they have had only two

02:43:48.530 --> 02:43:52.649
remote exploits in a very long set of years.

02:43:53.389 --> 02:43:56.870
In comparison, you could probably count remote

02:43:56.870 --> 02:44:01.750
exploits in Windows every week. So the contrast

02:44:01.750 --> 02:44:07.290
is very hard. So they care about security very,

02:44:07.409 --> 02:44:11.079
very hard. to the point where they will sacrifice

02:44:11.079 --> 02:44:16.520
everything else in the name of security literally

02:44:16.520 --> 02:44:21.579
everything else so they do try to be a good desktop

02:44:21.579 --> 02:44:25.079
operating system they do try to be like everything

02:44:25.079 --> 02:44:30.920
but security comes first and if it's still possible

02:44:30.920 --> 02:44:36.250
to do this they will do it but once again security

02:44:36.250 --> 02:44:41.469
comes first and their motto is very minimal like

02:44:41.469 --> 02:44:44.850
almost like suckless software you know they everything

02:44:44.850 --> 02:44:48.110
they do is very minimal and this reduces the

02:44:48.110 --> 02:44:52.629
attack surface that's how they work okay and

02:44:52.629 --> 02:44:57.069
who is bsd for then like regular users you and

02:44:57.069 --> 02:45:00.250
me someone that has a home lab oh i lost power

02:45:01.020 --> 02:45:02.879
that's why you hear that beep in the background

02:45:02.879 --> 02:45:06.420
because my ups is beeping i hope it comes back

02:45:06.420 --> 02:45:12.879
but um okay who is bsd4 who is using bsd uh playstation

02:45:12.879 --> 02:45:20.840
uses bsd okay so it's good for uh developing

02:45:20.840 --> 02:45:29.049
some uh how to say um projects on which you can

02:45:29.049 --> 02:45:33.569
build upon and earn i suppose money i mean sony

02:45:33.569 --> 02:45:38.270
makes money on playstation um and stuff like

02:45:38.270 --> 02:45:42.110
that who who are bsds for uh uh yeah there there

02:45:42.110 --> 02:45:44.870
are these conversations where people want to

02:45:44.870 --> 02:45:48.569
know where will they run away when linux like

02:45:48.569 --> 02:45:52.829
falls you know There are different ways to look

02:45:52.829 --> 02:45:56.409
at this. For example, Linus Torvalds as the main

02:45:56.409 --> 02:46:02.409
gatekeeper of Linux is taking very good care

02:46:02.409 --> 02:46:07.110
of its baby. And a lot of people are very afraid

02:46:07.110 --> 02:46:10.809
what is going to happen with Linux when he will

02:46:10.809 --> 02:46:14.069
no longer be maintaining it for whatever reason.

02:46:14.190 --> 02:46:19.420
But at some point he will step down. as every

02:46:19.420 --> 02:46:23.440
human does, you know, and people are afraid that

02:46:23.440 --> 02:46:28.520
nobody is capable of replacing him. And some

02:46:28.520 --> 02:46:32.260
people think that the corporations that kind

02:46:32.260 --> 02:46:36.200
of control Linux now will take over completely

02:46:36.200 --> 02:46:40.920
and everything will go to shit. So that could

02:46:40.920 --> 02:46:45.620
be a valid way of seeing it, but we just don't

02:46:45.620 --> 02:46:51.049
know. where will it go when he steps down. Also

02:46:51.049 --> 02:46:59.489
there is a really large group of people that

02:46:59.489 --> 02:47:02.709
really dislike Rust programming language and

02:47:02.709 --> 02:47:09.149
it has been entering a good part of Linux kernel

02:47:09.149 --> 02:47:16.469
so they think the Linux will fall apart. to lack

02:47:16.469 --> 02:47:18.989
of better words for that as i said i'm not a

02:47:18.989 --> 02:47:22.770
developer so i can discuss it in any um properly

02:47:22.770 --> 02:47:25.870
technical way but people a lot of people think

02:47:25.870 --> 02:47:28.809
that if linux was made in c it should remain

02:47:28.809 --> 02:47:34.950
in c and not mix up languages and like rust being

02:47:34.950 --> 02:47:38.409
too young and changes too often and not being

02:47:38.409 --> 02:47:42.579
a good fit for for Linux but then again I try

02:47:42.579 --> 02:47:45.559
to understand Linus Torvalds. I mean he needs

02:47:45.559 --> 02:47:51.540
active maintainers and a lot of C programmers

02:47:51.540 --> 02:47:58.739
are old and C is not cool. Rust is cool and this

02:47:58.739 --> 02:48:01.139
means that every new kid on the block will learn

02:48:01.139 --> 02:48:08.040
Rust. So if you want new fresh meat on kernel

02:48:08.040 --> 02:48:13.579
development Chances are they will be using Rust

02:48:13.579 --> 02:48:19.079
and they will demand to use Rust or else they

02:48:19.079 --> 02:48:23.920
will not help you with your kernel. So they will

02:48:23.920 --> 02:48:27.020
help someone else with their skills who uses

02:48:27.020 --> 02:48:33.079
Rust on their kernel. So I think Torvald's reasoning

02:48:33.079 --> 02:48:37.370
is good. On this, because you really do need

02:48:37.370 --> 02:48:39.750
maintainers to keep developing the system. So

02:48:39.750 --> 02:48:42.809
if you don't have maintainers because they all

02:48:42.809 --> 02:48:47.569
died, that's kind of not good. And it's not his

02:48:47.569 --> 02:48:52.469
job to make C cool again. It's the job of C foundation,

02:48:52.809 --> 02:48:58.610
whatever they're called. Do you feel that Linux

02:48:58.610 --> 02:49:03.629
community is subdivided because I see a lot of

02:49:03.629 --> 02:49:08.530
hate between distros. I'm on Ubuntu and I hate,

02:49:08.610 --> 02:49:11.829
I don't know, Arch users. I'm on Arch and I hate

02:49:11.829 --> 02:49:14.569
Ubuntu users. And you know, the list goes on

02:49:14.569 --> 02:49:18.809
and on and on, right? This is very natural for

02:49:18.809 --> 02:49:22.790
human beings. So you can't do nothing about that.

02:49:22.909 --> 02:49:30.170
You can accept people being who they are. and

02:49:30.170 --> 02:49:35.670
try to help them to overcome the fear. I think

02:49:35.670 --> 02:49:39.290
that's fear what drives them to talk like that.

02:49:40.709 --> 02:49:45.010
But generally, I do get quite a few comments.

02:49:45.229 --> 02:49:49.389
It's not a lot, like it's not the majority, but

02:49:49.389 --> 02:49:54.290
I do notice them quite a few when people come

02:49:54.290 --> 02:49:59.110
and judge me very negatively about this particular

02:49:59.110 --> 02:50:02.389
distro that I am describing in this particular

02:50:02.389 --> 02:50:05.850
video because they think this is my primary distribution

02:50:05.850 --> 02:50:09.350
because that's the only video they saw from my

02:50:09.350 --> 02:50:11.569
channel and they think that's my distribution

02:50:11.569 --> 02:50:16.049
and they have a very strong reason why I should

02:50:16.049 --> 02:50:19.629
not be using that distribution. It doesn't matter

02:50:19.629 --> 02:50:21.909
that I'm not even using that distribution. I'm

02:50:21.909 --> 02:50:25.260
just showing it. But they do know that I'm using

02:50:25.260 --> 02:50:27.559
this one because I'm showing it and I should

02:50:27.559 --> 02:50:29.659
not be using it because this and this and this.

02:50:30.680 --> 02:50:38.799
And sometimes they say very ugly things and you

02:50:38.799 --> 02:50:44.920
would not believe, but I thank every single one

02:50:44.920 --> 02:50:51.059
of them very warmly. And I asked them to... if

02:50:51.059 --> 02:50:53.500
they can to better construct their criticism

02:50:53.500 --> 02:50:58.600
so I can improve and 50 % of them just disappear

02:50:58.600 --> 02:51:04.399
after such comment and the other 50 % tends to

02:51:04.399 --> 02:51:06.899
say like I'm sorry I didn't mean it like that

02:51:06.899 --> 02:51:12.700
and then the conversation starts. So it's very

02:51:12.700 --> 02:51:17.129
natural for humans to be divided. And in clans,

02:51:17.209 --> 02:51:20.469
and this is what we did when we had sticks and

02:51:20.469 --> 02:51:24.129
rocks. And this is what we still do when we have

02:51:24.129 --> 02:51:29.829
software on microchips. So it will remain that

02:51:29.829 --> 02:51:36.790
way probably forever. And I wouldn't bet on it

02:51:36.790 --> 02:51:41.370
100%, but very long time from now. Okay. And

02:51:41.370 --> 02:51:46.049
you have been more Emacs. Yeah. I think I did

02:51:46.049 --> 02:51:49.049
give you a hint in the beginning of this video

02:51:49.049 --> 02:51:53.809
that I'm not into any camp and simply I wanted

02:51:53.809 --> 02:51:59.450
when I started learning teaching myself programming

02:51:59.450 --> 02:52:03.690
a little bit more I wanted some tool that can

02:52:03.690 --> 02:52:09.920
minimally be distracting for me and I was even

02:52:09.920 --> 02:52:13.659
prepared to work in the terminal as long as the

02:52:13.659 --> 02:52:17.260
tool is minimally good enough for what I need.

02:52:17.979 --> 02:52:22.520
And Vim and Emacs are very, very popular, both

02:52:22.520 --> 02:52:27.379
of them in their own way. So I did try both of

02:52:27.379 --> 02:52:33.299
them and I still interchangeably use them. But

02:52:33.299 --> 02:52:40.569
mostly I use Vim for very quick editing and mostly

02:52:40.569 --> 02:52:43.889
I use Emacs for learning programming and some

02:52:43.889 --> 02:52:50.090
other things because I'm trying to... OpenBSD

02:52:50.090 --> 02:52:53.469
is one of the reason who is driving me towards

02:52:53.469 --> 02:52:57.049
some sort of minimalism and this is not a bad

02:52:57.049 --> 02:53:03.790
thing. It's just my... How do I say it? I am

02:53:03.790 --> 02:53:12.020
eager for seeing how this will work for me. So

02:53:12.020 --> 02:53:15.100
one of the things that I want to do, which I

02:53:15.100 --> 02:53:19.500
am working on right now, is setting up Emacs

02:53:19.500 --> 02:53:23.000
as my email server, email client, sorry, email

02:53:23.000 --> 02:53:27.299
client. But also I want to bring my own email

02:53:27.299 --> 02:53:34.190
server to my own server. Right now it's not hosted

02:53:34.190 --> 02:53:36.870
on my server because I think it's a lot of work

02:53:36.870 --> 02:53:41.590
to maintain. Email is not easy. It's easy to

02:53:41.590 --> 02:53:45.729
set up but it's not easy when you get blacklisted

02:53:45.729 --> 02:53:48.889
all around for whatever reason and then you have

02:53:48.889 --> 02:53:52.989
to beg around the entire internet to un -blacklist

02:53:52.989 --> 02:53:55.229
you because people cannot receive your emails.

02:53:55.389 --> 02:54:03.600
It's not easy. configuring the email client that

02:54:03.600 --> 02:54:06.159
shouldn't be that difficult so that's one of

02:54:06.159 --> 02:54:09.579
the things that i want to put in emacs i also

02:54:09.579 --> 02:54:15.239
want to move my rss feeds into emacs i also tried

02:54:15.239 --> 02:54:19.360
matrix chat in emacs and it works but it's a

02:54:19.360 --> 02:54:22.360
little bit cumbersome to use so i don't do that

02:54:22.360 --> 02:54:29.940
i use wechat for irds and for matrix and still

02:54:29.940 --> 02:54:32.680
in elements mostly because the other software

02:54:32.680 --> 02:54:37.239
is shit for for the most part and i really dislike

02:54:37.239 --> 02:54:42.659
uh electron but it is what it is um i'm trying

02:54:42.659 --> 02:54:46.719
to put a lot of stuff in emacs and this is what

02:54:46.719 --> 02:54:51.840
emacs does best eats a lot of stuff and at the

02:54:51.840 --> 02:54:57.079
same time At the same time, it can help me with

02:54:57.079 --> 02:55:00.020
programming. Out of the box, it comes with something

02:55:00.020 --> 02:55:04.600
called EGLOT, which is like a language server

02:55:04.600 --> 02:55:10.260
processor. It helps me with code completion and

02:55:10.260 --> 02:55:15.440
telling me why this command is not good. And

02:55:15.440 --> 02:55:21.020
it also gives me a built -in debugger for C programming

02:55:21.020 --> 02:55:26.799
language. and also I can test my code within

02:55:26.799 --> 02:55:32.200
Emacs and compile it within Emacs. With Vim it

02:55:32.200 --> 02:55:36.180
looks like edit the file, save the file, exit

02:55:36.180 --> 02:55:43.680
the file, compile, test, go back to Vim and stuff

02:55:43.680 --> 02:55:46.840
like that. With Emacs I can do it all inside

02:55:46.840 --> 02:55:51.129
there. It kind of feels natural for me to go

02:55:51.129 --> 02:55:54.989
into that direction because it gives me all these

02:55:54.989 --> 02:55:57.750
kinds of things like integrated into one package

02:55:57.750 --> 02:56:02.190
and this is precisely what WIM doesn't even try

02:56:02.190 --> 02:56:07.510
to do and I still want to say that one is better

02:56:07.510 --> 02:56:10.010
than the other it's simply that they serve a

02:56:10.010 --> 02:56:13.530
completely different purpose and I kind of feel

02:56:13.530 --> 02:56:18.629
that this other Emeksi purpose is what feels

02:56:19.640 --> 02:56:24.520
closer to home. I feel more at home in this kind

02:56:24.520 --> 02:56:29.159
of environment. If I feel like I want to add

02:56:29.159 --> 02:56:32.260
some other functionality, it turns out that it

02:56:32.260 --> 02:56:38.040
can do that. Whatever it is. Like a Swiss Army

02:56:38.040 --> 02:56:41.239
knife, it might not be the best. It probably

02:56:41.239 --> 02:56:44.139
is not the best. it at anything but it really

02:56:44.139 --> 02:56:47.239
does a lot of different things and if they're

02:56:47.239 --> 02:56:49.500
good enough i will use them if they're not good

02:56:49.500 --> 02:56:51.840
enough i will use another tool i don't waste

02:56:51.840 --> 02:56:55.260
my time on something that doesn't satisfy my

02:56:55.260 --> 02:56:58.579
needs but i do give every software a fair chance

02:56:58.579 --> 02:57:03.399
you know to to show itself to me just as i did

02:57:03.399 --> 02:57:06.260
with arch linux i didn't try arch for a week

02:57:06.260 --> 02:57:10.239
i used it for more than a year on all my computers

02:57:10.959 --> 02:57:14.680
at the same time so it's not just one computer

02:57:14.680 --> 02:57:19.459
it's you know more at work at home on my laptop

02:57:19.459 --> 02:57:24.760
and on my second laptop so um except on servers

02:57:24.760 --> 02:57:27.659
i don't believe and i never believed in arch

02:57:27.659 --> 02:57:30.319
linux to be good for servers not for a second

02:57:30.319 --> 02:57:34.440
so that's not something that i ever even considered

02:57:34.440 --> 02:57:39.059
okay it's not even a topic for me okay makes

02:57:39.059 --> 02:57:42.159
sense okay Now, I did cover all the questions

02:57:42.159 --> 02:57:45.040
that I had here. Are there any topics or something

02:57:45.040 --> 02:57:47.899
you would like to discuss before we wrap it up?

02:57:48.239 --> 02:57:51.079
Thanks for that. It was very fun. Yeah, I know.

02:57:51.219 --> 02:57:54.040
Really appreciate you. Tony sent the message

02:57:54.040 --> 02:57:57.600
there. He's the one that donated below. So, is

02:57:57.600 --> 02:58:00.680
Debian the king of distros? It seems like all

02:58:00.680 --> 02:58:03.159
the money in the world is made up of Debian servers

02:58:03.159 --> 02:58:06.700
and now proprietary wrappers for Bed Hat servers,

02:58:07.040 --> 02:58:11.129
Amazon, Linux. is is is devian the king of all

02:58:11.129 --> 02:58:15.010
distros what would you say yes or no uh probably

02:58:15.010 --> 02:58:19.049
i mean the question is not very tricky it's fully

02:58:19.049 --> 02:58:22.969
specific you know uh but if i have to answer

02:58:22.969 --> 02:58:26.090
i will i would go with yes yeah i would go with

02:58:26.090 --> 02:58:34.590
yes agree agree Yeah, what he said, it's everywhere.

02:58:35.170 --> 02:58:39.450
Not just on a lot of desktops, but it holds quite

02:58:39.450 --> 02:58:45.889
a good chunk of internet. Okay. Okay, Darth,

02:58:46.090 --> 02:58:48.370
really appreciate it. I know it's getting late

02:58:48.370 --> 02:58:50.790
for you. We didn't plan this at all. I reached

02:58:50.790 --> 02:58:56.159
out yesterday, today. Siri in chat. highlighted

02:58:56.159 --> 02:59:00.180
me is the Red Hat Unnode to Red Hat Linux. I

02:59:00.180 --> 02:59:03.860
did try to explain that and it's not, but it

02:59:03.860 --> 02:59:09.200
is at the same time. I saw this hat in a shop

02:59:09.200 --> 02:59:13.600
very randomly and I literally entered there and

02:59:13.600 --> 02:59:16.239
bought it because the hat was talking to me,

02:59:16.260 --> 02:59:22.079
told me to buy it. And yes, it does, it reminds...

02:59:22.350 --> 02:59:26.649
both me and everyone else on Red Hat and Red

02:59:26.649 --> 02:59:31.250
Hat is Linux so for the channel it kind of makes

02:59:31.250 --> 02:59:36.569
sense that it's a good prop but after all it's

02:59:36.569 --> 02:59:40.549
just a prop and I get a lot of comments quite

02:59:40.549 --> 02:59:45.129
a lot on my videos where I as the people express

02:59:45.129 --> 02:59:49.639
themselves where I shield for Debian while wearing

02:59:49.639 --> 02:59:54.420
a red hat and they and then they say subbed so

02:59:54.420 --> 02:59:59.440
it does serve a purpose tony keeps talking about

02:59:59.440 --> 03:00:02.200
mdocs and we don't know what that is what is

03:00:02.200 --> 03:00:05.899
mdocs tony is it a company what is it i guess

03:00:05.899 --> 03:00:09.219
we will we will discuss it on matrix matrix yeah

03:00:09.219 --> 03:00:14.700
yeah so i will do you still don't know what it

03:00:14.700 --> 03:00:17.979
is yeah do you still play games start yeah yeah

03:00:17.979 --> 03:00:21.219
quite a lot if you switch to my screen again

03:00:21.219 --> 03:00:27.239
yeah uh you can see steam pre -installed uh you

03:00:27.239 --> 03:00:30.979
can also see here my uh oh i cannot see it hold

03:00:30.979 --> 03:00:34.500
on i can see oh i see that okay yeah you're showing

03:00:34.500 --> 03:00:39.059
fast pitch right now okay yeah yeah so it's a

03:00:39.059 --> 03:00:43.819
pretty gamey cpu and a pretty gamey gpu and steam

03:00:43.819 --> 03:00:48.100
is now open And right now I'm playing Cyberpunk.

03:00:49.719 --> 03:00:54.000
Oh man, that is a base. That's my favorite game.

03:00:54.180 --> 03:00:57.120
If you notice my wallpaper, right? The one that

03:00:57.120 --> 03:01:00.840
I have in the background. Can I show it? Where

03:01:00.840 --> 03:01:04.200
can I show it? If you take a look at this in

03:01:04.200 --> 03:01:06.840
the background, you will not be able to see it.

03:01:06.899 --> 03:01:11.090
I have to click on the edge here. It can't. Oh

03:01:11.090 --> 03:01:12.850
man, I don't know how to bring it up because

03:01:12.850 --> 03:01:16.510
I don't have a desk here. So on Linux, it's pretty

03:01:16.510 --> 03:01:19.450
common in all window managers, including regular

03:01:19.450 --> 03:01:22.750
desktops and styling window managers, that you

03:01:22.750 --> 03:01:25.870
can just hold the super key, which is on Windows

03:01:25.870 --> 03:01:30.030
key, and just dragging a window wherever you

03:01:30.030 --> 03:01:31.989
take it. It doesn't matter if it's styled or

03:01:31.989 --> 03:01:35.549
not. For example, on Hyperland, if it's styled

03:01:35.549 --> 03:01:39.030
and you move it around, it will just... untile

03:01:39.030 --> 03:01:43.510
it. You don't have to grab it on the top, you

03:01:43.510 --> 03:01:45.829
can just grab it anywhere by holding the super

03:01:45.829 --> 03:01:49.989
key. So it's kind of useful. But yeah, the Skyrim

03:01:49.989 --> 03:01:53.870
is not something that I play very actively, like

03:01:53.870 --> 03:01:58.229
from day to day. It's just my... What do you

03:01:58.229 --> 03:02:04.290
call it? My... This will sound a bit wrong because

03:02:04.290 --> 03:02:07.770
I'm lacking the right expression, but it's like

03:02:07.770 --> 03:02:11.729
the one that gives you warm feelings, like a

03:02:11.729 --> 03:02:15.309
cozy game. Oh yeah, do you like seeing the nature,

03:02:15.569 --> 03:02:19.250
hearing the music is beautiful? Yes, and the

03:02:19.250 --> 03:02:23.270
fact that not only that I have finished the game,

03:02:23.329 --> 03:02:26.430
but after you finish it, you have like a gazillion

03:02:26.430 --> 03:02:30.469
of... spots where you just never have been before

03:02:30.469 --> 03:02:34.610
and you enter and you find something new. It's

03:02:34.610 --> 03:02:38.309
not very meaningful to finishing the game, but

03:02:38.309 --> 03:02:42.450
it's more like playing it for years, just a little

03:02:42.450 --> 03:02:49.209
bit at a time. And this is probably my favorite

03:02:49.209 --> 03:02:52.549
game ever. I don't play it actually anymore.

03:02:53.639 --> 03:02:56.500
uh this one i actually it says like 45 hours

03:02:56.500 --> 03:03:00.040
but i actually played it like a couple of thousand

03:03:00.040 --> 03:03:05.959
of hours on xbox previously and it's like a game

03:03:05.959 --> 03:03:10.360
of pirates it's a cartoony looking but actually

03:03:10.360 --> 03:03:14.399
a sort of simulation of physics the you turn

03:03:14.399 --> 03:03:19.520
the um the the the sheet of you know of your

03:03:19.520 --> 03:03:23.829
ships on the um I don't know the words, but you

03:03:23.829 --> 03:03:27.750
can get the mimics. You need to turn the thing

03:03:27.750 --> 03:03:30.709
into the wind so you can go faster and you have

03:03:30.709 --> 03:03:33.430
to dig for treasure. And once you dig it out,

03:03:33.469 --> 03:03:35.790
you have to carry it to your ship and then you

03:03:35.790 --> 03:03:38.969
have to drive the treasure with your ship across

03:03:38.969 --> 03:03:41.329
the sea to the destination and hand it over.

03:03:42.069 --> 03:03:45.569
And it's very manual game. Is it an old game

03:03:45.569 --> 03:03:51.290
or is it new? No, it's from 2018. Okay. And this

03:03:51.290 --> 03:03:56.370
one is also one of my favorites. Oh, that's pretty

03:03:56.370 --> 03:03:59.389
fast -paced. I think I saw that in my brother

03:03:59.389 --> 03:04:02.750
-in -law's house in the PlayStation. It is very

03:04:02.750 --> 03:04:06.569
fast -paced. It was too fast for me. Yeah, it's

03:04:06.569 --> 03:04:10.290
very fast -paced. This one I'm kind of trying

03:04:10.290 --> 03:04:15.770
to get into, but I just didn't. This one is very

03:04:15.770 --> 03:04:18.649
awesome. And this is actually free software.

03:04:19.200 --> 03:04:23.020
The game is really small, like, I don't know,

03:04:23.020 --> 03:04:26.659
a couple hundred megabytes, I think. It's also

03:04:26.659 --> 03:04:28.399
free software. You can get it on any operating

03:04:28.399 --> 03:04:34.200
system, literally any. It's like, let me switch

03:04:34.200 --> 03:04:41.200
to store page. It's like a move -based strategy

03:04:41.200 --> 03:04:46.100
game with RNG numbers. If you are in the woods,

03:04:46.600 --> 03:04:50.180
Then your archer has better stats than the ones

03:04:50.180 --> 03:04:53.159
outside of the woods. And then you attack them

03:04:53.159 --> 03:04:57.020
and you have to conquer them. I will not spoil

03:04:57.020 --> 03:05:01.739
it any longer, but it's worth a try. If you are

03:05:01.739 --> 03:05:05.520
into high -end graphics, you will probably puke.

03:05:06.520 --> 03:05:12.350
But I guarantee it's a good game. and it's 20

03:05:12.350 --> 03:05:15.290
years old and it's still very actively developed

03:05:15.290 --> 03:05:21.049
and it has a very live community and this one

03:05:21.049 --> 03:05:27.250
is also for good feelings and this one i bought

03:05:27.250 --> 03:05:32.370
very recently i played only 100 minutes it's

03:05:32.370 --> 03:05:38.610
like a rogue -like game in space I'm gonna stop

03:05:38.610 --> 03:05:41.889
there. You manage your spaceship and enemies

03:05:41.889 --> 03:05:45.690
attack you and you have to handle your engines,

03:05:45.809 --> 03:05:49.809
your drive, your shields, your weapons, your

03:05:49.809 --> 03:05:53.090
upgrades, your humans, your fire extinguishers,

03:05:53.090 --> 03:05:59.069
your air, a lot of stuff and other ones are attacking

03:05:59.069 --> 03:06:02.909
you and if you die it's game over and you start

03:06:02.909 --> 03:06:06.579
from the beginning. Yeah, this one is like Super

03:06:06.579 --> 03:06:10.420
Mario, and it's kind of fun. Never finished this

03:06:10.420 --> 03:06:14.000
one, but when I feel like brainless jumping around,

03:06:14.219 --> 03:06:17.680
then it's this one. This one, I have no clue

03:06:17.680 --> 03:06:21.700
what it is. I just bought it, literally. And

03:06:21.700 --> 03:06:25.940
it seemed kind of cool. I have yet to start it.

03:06:27.459 --> 03:06:30.440
This one I started... This one, obviously, I

03:06:30.440 --> 03:06:35.190
played when it came out in the 90s, but... I

03:06:35.190 --> 03:06:39.209
started streaming it on Twitch, so I'm probably

03:06:39.209 --> 03:06:42.290
going to finish it. I have no idea why I have

03:06:42.290 --> 03:06:46.790
this. I don't know why it's disinstalled. And

03:06:46.790 --> 03:06:50.350
this one also felt like something spacey for

03:06:50.350 --> 03:06:53.049
me. I also only played it for half an hour just

03:06:53.049 --> 03:06:55.670
to give it a try. It feels nice, I don't know.

03:06:56.069 --> 03:07:00.950
I kind of jump between games. Oh, okay. A lot,

03:07:01.110 --> 03:07:05.379
but generally... generally you can see a little

03:07:05.379 --> 03:07:09.540
bit of my taste here okay yeah skyrim is my favorite

03:07:09.540 --> 03:07:12.600
game but i don't play anymore um yeah i don't

03:07:12.600 --> 03:07:14.979
have the time and i get tired easily and i get

03:07:14.979 --> 03:07:19.600
bored and i'm like no let me yeah i used to play

03:07:19.600 --> 03:07:22.680
a really lot of video games before i started

03:07:22.680 --> 03:07:27.420
my youtube channel so you can't invest a limited

03:07:27.420 --> 03:07:32.940
amount of time into yeah a it is what it is yeah

03:07:32.940 --> 03:07:37.479
youtube takes a lot of time yeah all right darth

03:07:37.479 --> 03:07:40.079
really appreciate it man thanks for sharing with

03:07:40.079 --> 03:07:43.799
us um i'm going to be editing this video i'm

03:07:43.799 --> 03:07:46.879
gonna be releasing it probably friday right now

03:07:46.879 --> 03:07:49.579
it's gonna go unlisted so you will not be able

03:07:49.579 --> 03:07:53.180
to see it anymore but uh friday i will post it

03:07:53.180 --> 03:07:57.319
it will also be available as a podcast in spotify

03:07:57.319 --> 03:08:00.299
and all those i i just know spotify youtube music

03:08:00.299 --> 03:08:03.219
and whatever you know other other platforms the

03:08:03.219 --> 03:08:05.500
other thing that i wanted to do is thank the

03:08:05.500 --> 03:08:08.540
ceo because i have members right different membership

03:08:08.540 --> 03:08:13.840
levels uh the ceo member web23 web23 .com and

03:08:13.840 --> 03:08:16.760
all the other members i also want to thank you

03:08:16.760 --> 03:08:19.459
want to thank chat for you know sending messages

03:08:19.459 --> 03:08:23.659
there and keeping the conversation going so thank

03:08:23.659 --> 03:08:28.540
you thank you for inviting me that was i i even

03:08:28.540 --> 03:08:33.139
think that you uh didn't plan for this much no

03:08:33.139 --> 03:08:38.420
no we didn't plan yep yeah um thank you yep i'll

03:08:38.420 --> 03:08:42.659
see you till next time see you bye bye