WEBVTT

00:00:00.000 --> 00:00:02.680
Because I get this question all the time. I can't

00:00:02.680 --> 00:00:04.780
switch from Vim to Emacs because what if I'm

00:00:04.780 --> 00:00:07.660
remote into some server that doesn't have Emacs?

00:00:08.039 --> 00:00:11.960
It doesn't matter. You remote from your machine

00:00:11.960 --> 00:00:15.300
that has Emacs on it from inside Emacs. And you

00:00:15.300 --> 00:00:17.399
can still use your Emacs on this machine. And

00:00:17.399 --> 00:00:20.140
I noticed that your headings in org mode are

00:00:20.140 --> 00:00:22.760
bigger because I know a little bit about org

00:00:22.760 --> 00:00:25.219
mode only. Is that a default thing in Emacs?

00:00:25.300 --> 00:00:27.780
You can make the headings bigger? I don't know

00:00:27.780 --> 00:00:31.160
if you have any thoughts on PewDiePie's video.

00:00:31.379 --> 00:00:33.520
The headers of the table of contents and the

00:00:33.520 --> 00:00:35.679
descriptions, these are all just part of the

00:00:35.679 --> 00:00:37.640
literate config, the org document. I just want

00:00:37.640 --> 00:00:39.740
to hear your thoughts on macOS. Let's go with

00:00:39.740 --> 00:00:46.119
that first. So my thoughts on macOS is if I need

00:00:46.119 --> 00:00:48.640
a terminal, I could do, in my case, space TV

00:00:48.640 --> 00:00:51.500
as a key binding. I have to toggle on vterm.

00:00:51.619 --> 00:00:54.299
vterm is one of the terminal emulators here inside

00:00:54.299 --> 00:00:58.240
Emacs. And I assume you can also configure SSH

00:00:58.240 --> 00:01:02.079
key -based authentication in Emacs, right? Sure.

00:01:02.280 --> 00:01:05.159
You know, I'm pretty wordy as far as describing

00:01:05.159 --> 00:01:07.819
things. Like I tell you, hey, this block, this

00:01:07.819 --> 00:01:09.980
is what I'm doing, and that's why. Does it keep

00:01:09.980 --> 00:01:13.859
growing exponentially once you reach a certain

00:01:13.859 --> 00:01:18.260
point? Oh, no. Yeah, yeah. Because I remember,

00:01:18.420 --> 00:01:22.579
you know, really caring about my analytics in

00:01:22.579 --> 00:01:24.159
the first two or three years. What are your thoughts

00:01:24.159 --> 00:01:30.310
on Windows? Oh, so if I lose one of my three

00:01:30.310 --> 00:01:32.590
storage servers, I have them here. Where are

00:01:32.590 --> 00:01:36.870
they? VMs. These are my storage servers. Storage

00:01:36.870 --> 00:01:39.030
one, two and three. Right. So I can lose one

00:01:39.030 --> 00:01:43.090
of them and I can still keep it working. I know

00:01:43.090 --> 00:01:45.709
I should be using something else like Seth. Yeah,

00:01:45.750 --> 00:01:47.750
well, I retire from YouTube. I'm putting Debian

00:01:47.750 --> 00:01:50.829
back on my computer. If you're listening to this

00:01:50.829 --> 00:01:53.030
as a podcast, remember that it was originally

00:01:53.030 --> 00:01:55.150
recorded as a video. If you're not following

00:01:55.150 --> 00:01:57.379
along, you can go to my YouTube channel. My username

00:01:57.379 --> 00:01:59.680
is Linkarzu. And if you want to support me to

00:01:59.680 --> 00:02:02.200
keep this podcast going, you can donate in Ko

00:02:02.200 --> 00:02:04.000
-fi. I'm going to leave a link in the description.

00:02:04.340 --> 00:02:06.439
All right. So let's get started with this chapter

00:02:06.439 --> 00:02:10.080
then. What do we have today? We have DT, Derek,

00:02:10.300 --> 00:02:14.240
Mr. Tu on the call. How's it going, man? Man,

00:02:14.360 --> 00:02:17.280
I'm doing just lovely. I'm on my third cup of

00:02:17.280 --> 00:02:19.819
coffee this morning and I'm just trying to get

00:02:19.819 --> 00:02:22.000
by. Appreciate you inviting me. We're going to

00:02:22.000 --> 00:02:24.580
have a... I'm sure just a great conversation

00:02:24.580 --> 00:02:28.099
about Linux, Mac, possibly some Windows talk.

00:02:28.919 --> 00:02:32.199
Exactly. Yep. I have watched your videos, you

00:02:32.199 --> 00:02:35.080
know, because when you look for Linux on YouTube,

00:02:35.319 --> 00:02:39.259
what do you think shows up? A lot of folks show

00:02:39.259 --> 00:02:42.719
up, but you show up most of the times, right?

00:02:44.090 --> 00:02:47.930
I've made a lot of videos. I've spammed the YouTube

00:02:47.930 --> 00:02:51.169
algorithm a little bit. When did you get started

00:02:51.169 --> 00:02:53.909
with YouTube and why did that happen? I started

00:02:53.909 --> 00:02:58.449
in October of 2017 with the DistroTube channel.

00:02:59.449 --> 00:03:01.469
That was the first YouTube channel I'd ever had.

00:03:01.509 --> 00:03:05.909
First time I ever made a video, period. I got

00:03:05.909 --> 00:03:08.330
started making videos about Linux because there

00:03:08.330 --> 00:03:12.550
wasn't a lot of Linux content back then. There

00:03:12.550 --> 00:03:16.699
was some. But it was a much smaller space because

00:03:16.699 --> 00:03:20.460
this was before there was no Steam on Linux back

00:03:20.460 --> 00:03:25.120
then, which was a total game changer back when

00:03:25.120 --> 00:03:27.240
that happened. There was a lot of the bigger

00:03:27.240 --> 00:03:30.520
distributions that are around now, like Manjaro,

00:03:30.659 --> 00:03:35.020
I think, was just getting started. Things like

00:03:35.020 --> 00:03:38.979
that. Pretty much the only desktop Linux distribution

00:03:38.979 --> 00:03:42.180
people really knew back then was Ubuntu. Still

00:03:42.180 --> 00:03:44.930
very popular. But, you know, it was just much

00:03:44.930 --> 00:03:47.689
smaller space. And a lot of the people that did

00:03:47.689 --> 00:03:51.629
Linux content, the few that did, I didn't like

00:03:51.629 --> 00:03:54.169
the way they did it because they didn't focus

00:03:54.169 --> 00:03:59.150
necessarily on the free software and open source

00:03:59.150 --> 00:04:04.610
software, you know, part of the Linux ecosystem.

00:04:04.770 --> 00:04:06.810
Like, you know, they were just talking about

00:04:06.810 --> 00:04:08.669
Linux like it's just another desktop operating

00:04:08.669 --> 00:04:11.629
system, just like Windows and Mac. Like, no,

00:04:11.830 --> 00:04:15.419
it's not really. You know, the philosophy behind

00:04:15.419 --> 00:04:19.639
it all certainly is a much bigger part than necessarily

00:04:19.639 --> 00:04:23.379
the technology, in my opinion. And a lot of people

00:04:23.379 --> 00:04:25.279
didn't focus on that at all or they tried to

00:04:25.279 --> 00:04:27.459
ignore it. And there were a lot of Linux content

00:04:27.459 --> 00:04:31.339
creators that actively tried to downplay open

00:04:31.339 --> 00:04:33.300
source. Like they didn't want to talk about it

00:04:33.300 --> 00:04:36.000
that way because they thought that was a negative

00:04:36.000 --> 00:04:38.420
thing, which I thought that's kind of weird.

00:04:39.160 --> 00:04:42.360
So, you know, that was part of why I started

00:04:42.360 --> 00:04:44.860
doing what I'm doing. Oh, when you started doing

00:04:44.860 --> 00:04:50.060
the videos, then Linux wasn't too popular. It

00:04:50.060 --> 00:04:53.680
wasn't as popular as it is now. We've probably,

00:04:53.879 --> 00:04:57.040
I bet we've at least doubled our desktop market

00:04:57.040 --> 00:05:01.399
share since then. Okay. It was smaller. Because

00:05:01.399 --> 00:05:04.220
really, when you look at a lot of the numbers,

00:05:04.420 --> 00:05:07.120
which you don't have any really reliable stats,

00:05:07.240 --> 00:05:10.139
but if you look at... A global market share as

00:05:10.139 --> 00:05:12.120
far as like with stat counter and things like

00:05:12.120 --> 00:05:16.519
that. Or maybe around 4 % now. You don't know.

00:05:16.600 --> 00:05:18.759
I know we weren't at 2 % though when I started.

00:05:18.879 --> 00:05:21.560
I know that. We were under that number for sure.

00:05:21.740 --> 00:05:24.819
Because we never had a rating above 2 % that

00:05:24.819 --> 00:05:27.300
I can remember until just a few years ago. And

00:05:27.300 --> 00:05:29.839
then it went pretty quickly from 2 to 3. And

00:05:29.839 --> 00:05:32.699
pretty quickly from 3 to 4 now. So it's definitely.

00:05:33.899 --> 00:05:36.560
There's a lot of reasons for that. Steam. was

00:05:36.560 --> 00:05:38.920
a big reason. Uh, the steam deck now I think

00:05:38.920 --> 00:05:41.180
is a big reason because obviously that's getting

00:05:41.180 --> 00:05:45.759
factored into some of those figures. Um, so that

00:05:45.759 --> 00:05:48.220
was, that was really a big deal was the gaming.

00:05:49.019 --> 00:05:55.540
Okay. I see that you have around 264 ,000 subscribers,

00:05:56.180 --> 00:06:02.560
um, 1600 videos. That's a lot. Um, What do you

00:06:02.560 --> 00:06:05.399
talk about in your channel? Is it Linux only

00:06:05.399 --> 00:06:09.860
or? As far as operating systems, it's Linux only

00:06:09.860 --> 00:06:11.779
for the most part, because that's the only operating

00:06:11.779 --> 00:06:14.620
system I use. It's the only operating system

00:06:14.620 --> 00:06:20.480
I have used probably in 16 years, 18 years. It's

00:06:20.480 --> 00:06:23.279
been a long time since I had a machine that ran.

00:06:24.000 --> 00:06:26.920
Windows was what I was running before I moved

00:06:26.920 --> 00:06:30.899
to Linux full time. I haven't used a Mac. I had

00:06:30.899 --> 00:06:33.879
to use Macs in college, like computer labs and

00:06:33.879 --> 00:06:38.399
things. That was in the 1990s. So it's not the

00:06:38.399 --> 00:06:42.639
Mac you know. It's not modern Mac. So, yeah,

00:06:42.740 --> 00:06:45.829
I don't know much about Mac OS these days. Okay.

00:06:45.870 --> 00:06:48.209
Play with it in virtual machines. Same thing

00:06:48.209 --> 00:06:50.870
with Windows. I've run Windows 11 and a VM a

00:06:50.870 --> 00:06:53.589
time or two if I need to for whatever. If I need

00:06:53.589 --> 00:06:55.170
to do something on camera, for example, because

00:06:55.170 --> 00:06:57.870
sometimes I will do funny things with Windows

00:06:57.870 --> 00:07:02.490
on camera. I spin up a virtual machine for that

00:07:02.490 --> 00:07:07.189
typically. I had a call with Chasten. He has

00:07:07.189 --> 00:07:12.189
a channel. He was called Tinkerbell Linux, I

00:07:12.189 --> 00:07:14.790
think, and now he changed the name of his channel.

00:07:15.370 --> 00:07:19.949
And he talked about this core utils, that they're

00:07:19.949 --> 00:07:24.290
being rewritten. I know we're going somewhere

00:07:24.290 --> 00:07:26.449
else right now, but what are your thoughts? I

00:07:26.449 --> 00:07:28.269
haven't watched this video. What are your thoughts

00:07:28.269 --> 00:07:31.629
there? He does not agree to that rewrite. Are

00:07:31.629 --> 00:07:37.620
your thoughts the same? Well, it's just... There's

00:07:37.620 --> 00:07:40.060
a group of developers that have rewritten the

00:07:40.060 --> 00:07:43.600
GNU Core Utils using Rust. The GNU Core Utils,

00:07:43.660 --> 00:07:49.620
of course, are written in C. I don't mind people

00:07:49.620 --> 00:07:52.319
that rewrite things just because they're learning

00:07:52.319 --> 00:07:54.459
a programming language. We all do it. We start

00:07:54.459 --> 00:07:57.259
learning a language and we rewrite some simple

00:07:57.259 --> 00:08:00.779
thing using that language. I don't mind that.

00:08:00.939 --> 00:08:04.160
But when Linux distributions, especially big...

00:08:04.879 --> 00:08:07.220
Server distributions, for example, like Ubuntu,

00:08:07.420 --> 00:08:10.839
want to replace the core components of the operating

00:08:10.839 --> 00:08:14.439
system for no reason. Why are you switching out

00:08:14.439 --> 00:08:17.839
the core utils? That's like the major part of

00:08:17.839 --> 00:08:20.279
the operating system, that and the kernel. I

00:08:20.279 --> 00:08:24.660
mean, that's... I don't know. It's weird. Because

00:08:24.660 --> 00:08:26.220
there's nothing wrong with the new core utils.

00:08:26.339 --> 00:08:29.459
They're not switching because there's something

00:08:29.459 --> 00:08:31.860
wrong with these core utils. I mean, the core

00:08:31.860 --> 00:08:35.899
utils have been around for... 40 years, whenever

00:08:35.899 --> 00:08:40.299
GNU first started back in the mid -1980s or whatever,

00:08:40.379 --> 00:08:42.340
started working on what would be the operating

00:08:42.340 --> 00:08:45.659
system. Nobody has ever complained and said,

00:08:45.740 --> 00:08:47.879
oh, the GNU core utils, they're bad. We need

00:08:47.879 --> 00:08:51.580
to swap them out. That's just weird. It's kind

00:08:51.580 --> 00:08:54.299
of random. There's a vice president that works

00:08:54.299 --> 00:08:57.600
at Canonical. He's a programmer. He's a fan of

00:08:57.600 --> 00:09:01.480
Rust. And he wants to swap it out. Or reasons,

00:09:01.600 --> 00:09:04.039
I don't know. Like, there's no real reason other

00:09:04.039 --> 00:09:08.879
than he likes Rust. And that's it. It's like,

00:09:08.919 --> 00:09:12.320
well, that's not a great reason to do that. Especially

00:09:12.320 --> 00:09:16.259
these core utils that are written in Rust, they're

00:09:16.259 --> 00:09:20.460
not 100 % drop -in replacement just yet. Some

00:09:20.460 --> 00:09:24.100
of them still, when they test them, you know,

00:09:24.100 --> 00:09:28.379
they still have failures. So it's not, there's

00:09:28.379 --> 00:09:30.350
going to be some issues with it. You're not just

00:09:30.350 --> 00:09:32.429
going to swap it out and it's going to, oh, magically

00:09:32.429 --> 00:09:34.429
everything just works. Obviously, there's going

00:09:34.429 --> 00:09:38.090
to be some breakage. So why go through that if

00:09:38.090 --> 00:09:39.990
there's no real reason to go through that is

00:09:39.990 --> 00:09:44.029
my thoughts. OK, there could be something, I

00:09:44.029 --> 00:09:46.629
don't know, some hidden agenda there, conspiracy

00:09:46.629 --> 00:09:49.789
theories. I don't know. I don't know what the

00:09:49.789 --> 00:09:53.549
some of the conspiracy theories. I wouldn't say

00:09:53.549 --> 00:09:56.539
it's a conspiracy theory, but the. Rust rewrite

00:09:56.539 --> 00:09:59.019
of the core utils, the package is called the

00:09:59.019 --> 00:10:04.500
uutils. It's licensed not under the GPL. It's

00:10:04.500 --> 00:10:08.519
licensed, I believe, under the MIT license. I

00:10:08.519 --> 00:10:10.320
could be wrong about that. Maybe the BSD license.

00:10:10.379 --> 00:10:12.080
I think it's the MIT license. It's a permissive

00:10:12.080 --> 00:10:14.460
license, though. It's not the GPL. And that's

00:10:14.460 --> 00:10:17.840
a problem for some people. Because part of the

00:10:17.840 --> 00:10:20.820
core component of our good news slash Linux operating

00:10:20.820 --> 00:10:23.299
system is the fact that the core utils and the

00:10:23.299 --> 00:10:27.809
kernel are all GPL software. And that's part

00:10:27.809 --> 00:10:31.970
of why I think, in my opinion, why Linux has

00:10:31.970 --> 00:10:35.669
lasted as long as it has, why it's become much

00:10:35.669 --> 00:10:38.289
more popular in recent years on the desktop,

00:10:38.389 --> 00:10:41.509
but obviously dominates the server space. And

00:10:41.509 --> 00:10:43.710
a lot of that has to do with all of these millions

00:10:43.710 --> 00:10:46.269
of contributors around the world over the years

00:10:46.269 --> 00:10:48.990
that have contributed to the Linux kernel. And

00:10:48.990 --> 00:10:52.149
the licensing is a big part of why they did that.

00:10:52.980 --> 00:10:55.600
So we don't want to mess with that either. Again,

00:10:55.779 --> 00:10:58.620
if something's working, you know, why mess with

00:10:58.620 --> 00:11:01.980
it? Yeah, makes sense. Something out of topic.

00:11:02.100 --> 00:11:05.480
I don't see a video here in your in your channel.

00:11:05.639 --> 00:11:09.179
I don't know if you have any thoughts on PewDiePie's

00:11:09.179 --> 00:11:12.139
video, which became. I haven't watched it. No.

00:11:12.730 --> 00:11:14.809
I haven't watched it. It's not the kind of content

00:11:14.809 --> 00:11:17.990
I would typically watch for fun. I know some

00:11:17.990 --> 00:11:19.950
people wanted me to watch it just so I can make

00:11:19.950 --> 00:11:22.289
a video about it, but I don't know. Just watching

00:11:22.289 --> 00:11:26.909
somebody say, hey, I'm running Linux, that's

00:11:26.909 --> 00:11:30.169
not something interesting to me. As far as PewDiePie,

00:11:30.190 --> 00:11:33.750
though, I know he started... I've never watched

00:11:33.750 --> 00:11:36.070
a single minute of any video of this guy, but

00:11:36.070 --> 00:11:39.159
I know he's a gamer, right? I don't know. It

00:11:39.159 --> 00:11:41.200
kind of makes sense why he kind of knows what

00:11:41.200 --> 00:11:44.279
Linux is here with Steam and the Steam Deck.

00:11:45.120 --> 00:11:47.460
It's not that unusual that somebody like him

00:11:47.460 --> 00:11:50.019
has played with Linux a little bit. It's not

00:11:50.019 --> 00:11:53.960
like some random person like your grandmother

00:11:53.960 --> 00:11:56.840
tried Linux. It's somebody that's a complete

00:11:56.840 --> 00:12:01.039
tech noob. I'm sure this guy, he can make Linux

00:12:01.039 --> 00:12:04.000
work. It's not a shock that he's playing with

00:12:04.000 --> 00:12:08.460
Linux. What are your thoughts on him bringing

00:12:08.460 --> 00:12:12.779
a lot of users or people to Linux. Are you okay

00:12:12.779 --> 00:12:16.139
with that? What do you think? I have no problems

00:12:16.139 --> 00:12:20.259
with Linux getting popular. I know some people

00:12:20.259 --> 00:12:23.620
actually do for whatever weird reason. But for

00:12:23.620 --> 00:12:27.000
me, I don't care as far as if we gain market

00:12:27.000 --> 00:12:29.659
share, great. If we don't, that's great too.

00:12:29.779 --> 00:12:32.820
I'm not running Linux because it's popular. I'm

00:12:32.820 --> 00:12:35.259
just running it because it's what I like, what

00:12:35.259 --> 00:12:40.440
works for me. I don't worry about, a lot of people

00:12:40.440 --> 00:12:43.340
worry about how popular the software they run

00:12:43.340 --> 00:12:47.320
is. Is my operating system popular? Is the Linux

00:12:47.320 --> 00:12:49.480
distribution that I run, is it one of the more

00:12:49.480 --> 00:12:52.799
popular ones? Do people talk about it? The text

00:12:52.799 --> 00:12:55.000
editor I use, is it popular? I don't care about

00:12:55.000 --> 00:12:58.200
any of that. If it works for me, if it's what

00:12:58.200 --> 00:13:01.580
I like, I run it. I don't try to tell people

00:13:01.580 --> 00:13:05.269
what to run either. I don't care. software you

00:13:05.269 --> 00:13:07.970
use right i don't think some people do though

00:13:07.970 --> 00:13:10.429
it's it's kind of weird there's always sides

00:13:10.429 --> 00:13:14.110
right so they want us to take sides i think so

00:13:14.110 --> 00:13:16.990
i'm on the same boat as well as long as it works

00:13:16.990 --> 00:13:20.289
for me i don't really care you know and i have

00:13:20.289 --> 00:13:22.769
people that talk about emacs in the channel you

00:13:22.769 --> 00:13:25.149
know and we discuss emacs i want to learn emacs

00:13:25.149 --> 00:13:27.289
you know i use new of them that's my main editor

00:13:27.289 --> 00:13:29.429
but i want to learn about other stuff you know

00:13:29.429 --> 00:13:33.149
i don't have to be on one side only you know

00:13:33.149 --> 00:13:38.129
so People can find you on YouTube. That's where

00:13:38.129 --> 00:13:42.990
I put everything. I do have a channel also on

00:13:42.990 --> 00:13:45.730
Odyssey for people that want to watch me somewhere

00:13:45.730 --> 00:13:49.350
that's not YouTube. Okay. So that's available

00:13:49.350 --> 00:13:53.610
for people, obviously. But yeah, mainly YouTube

00:13:53.610 --> 00:13:57.269
is where I'm at. Okay. I see it here. Odyssey

00:13:57.269 --> 00:13:59.649
in the links. Well, everything is in here in

00:13:59.649 --> 00:14:06.759
the links. Okay. Right. Wonderful. I want to

00:14:06.759 --> 00:14:09.620
know more about your background. You know, this

00:14:09.620 --> 00:14:13.120
is just to motivate people that is trying to

00:14:13.120 --> 00:14:15.799
get started in all this and to get to know how

00:14:15.799 --> 00:14:19.460
it all started. So why did you end up in tech?

00:14:19.600 --> 00:14:21.559
How did all that happen? You want to share that?

00:14:21.980 --> 00:14:25.200
Well, I mean, I guess I ended up in tech, if

00:14:25.200 --> 00:14:27.779
you count being a YouTuber, being in tech, but

00:14:27.779 --> 00:14:32.840
I'm not trained in any professional way. In any

00:14:32.840 --> 00:14:36.299
tech -related field. I don't have college degrees

00:14:36.299 --> 00:14:38.879
in tech. I actually went to college for music.

00:14:38.940 --> 00:14:40.799
I have a bachelor's and a master's degree in

00:14:40.799 --> 00:14:44.960
music performance. And, you know, went to school

00:14:44.960 --> 00:14:50.080
for that. Jobs after that. Taught a little bit

00:14:50.080 --> 00:14:53.879
because of music. Don't want to be a teacher,

00:14:53.940 --> 00:14:56.879
though. Didn't like that. Or I don't mind being

00:14:56.879 --> 00:14:58.659
an educator. I didn't like teaching public school.

00:15:02.549 --> 00:15:05.169
But, you know, and after that, you know, I've

00:15:05.169 --> 00:15:10.210
worked many years in retail, you know, and supervisory

00:15:10.210 --> 00:15:15.070
roles, various retail companies until I started

00:15:15.070 --> 00:15:17.269
my channel in 2017. I was still working at the

00:15:17.269 --> 00:15:20.769
time, obviously. COVID, though, in 2020, when

00:15:20.769 --> 00:15:25.570
the shutdown happened here in the U .S. I was

00:15:25.570 --> 00:15:28.149
not going to have a job when I returned from

00:15:28.149 --> 00:15:30.009
the shutdown because the company I was working

00:15:30.009 --> 00:15:33.889
at was doing pretty poorly before COVID. They

00:15:33.889 --> 00:15:36.210
were about to file bankruptcy. They were going

00:15:36.210 --> 00:15:39.009
to scale back a lot of positions. And one of

00:15:39.009 --> 00:15:41.070
the positions they were going to cut was the

00:15:41.070 --> 00:15:45.730
position I held. So when COVID happened, I was

00:15:45.730 --> 00:15:49.450
already doing YouTube. It was a side gig. It

00:15:49.450 --> 00:15:52.190
just became the gig. So I've been doing this.

00:15:53.129 --> 00:15:56.330
But I do like you. I do see YouTube as an extension

00:15:56.330 --> 00:15:59.409
of me being a teacher. Yep. One of the things

00:15:59.409 --> 00:16:03.950
I love is teaching people how to use some of

00:16:03.950 --> 00:16:05.649
this software, how to use things like, you know,

00:16:05.649 --> 00:16:09.289
many mags and various shell utilities, you know,

00:16:09.289 --> 00:16:12.269
the new core you tools, how to do some scripting

00:16:12.269 --> 00:16:13.889
programming, things like, you know, some basic

00:16:13.889 --> 00:16:16.970
stuff that a lot of people fear until somebody

00:16:16.970 --> 00:16:20.889
kind of explains it. And I'm pretty good at.

00:16:21.680 --> 00:16:26.179
Talking in a understandable, deliberate way and

00:16:26.179 --> 00:16:28.019
getting people through some topics that they

00:16:28.019 --> 00:16:30.940
think are hard. So that's always been a strength

00:16:30.940 --> 00:16:33.100
of mine. That's kind of what I was doing, even

00:16:33.100 --> 00:16:35.740
at my jobs. You know, typically my positions

00:16:35.740 --> 00:16:38.320
were usually HR or training related, you know,

00:16:38.320 --> 00:16:41.500
teaching people, you know, whatever. So it's

00:16:41.500 --> 00:16:44.639
always kind of been how I saw myself. So I think

00:16:44.639 --> 00:16:47.200
YouTube is a great extension for. Again, just

00:16:47.200 --> 00:16:50.139
educating people on anything. And anybody can

00:16:50.139 --> 00:16:53.100
do this. Anybody, because I hear from people

00:16:53.100 --> 00:16:54.980
all the time, you know, I've been wanting to

00:16:54.980 --> 00:16:56.940
start a YouTube channel. It looks fun, but I

00:16:56.940 --> 00:16:59.460
don't know what I want to do. It's like, well,

00:16:59.500 --> 00:17:02.500
everybody has life experience. Everybody knows

00:17:02.500 --> 00:17:05.259
something about something. And trust me, there

00:17:05.259 --> 00:17:07.140
will be people that watch that content about

00:17:07.140 --> 00:17:11.339
the stuff you know. So just start the camera

00:17:11.339 --> 00:17:14.019
recording. Just put the first video out. It's

00:17:14.019 --> 00:17:16.460
not going to be a good video. Your first video

00:17:16.460 --> 00:17:18.380
is not going to, it's going to, the audio is

00:17:18.380 --> 00:17:21.720
going to suck, right? Because that crappy $10

00:17:21.720 --> 00:17:23.980
microphone you bought at Walmart, trust me, it's

00:17:23.980 --> 00:17:26.640
going to suck. But put the first video out. Once

00:17:26.640 --> 00:17:30.079
you get started, you know, then you'll quickly

00:17:30.079 --> 00:17:34.039
figure out what works, what doesn't. And, you

00:17:34.039 --> 00:17:36.559
know, eventually you'll figure out how this whole

00:17:36.559 --> 00:17:40.019
content creation game works. Man, my first videos,

00:17:40.059 --> 00:17:42.940
I recorded them with my AirPods, with my headphones.

00:17:43.180 --> 00:17:47.519
Man, the audio sucks. You hear the echo. Still,

00:17:47.700 --> 00:17:50.519
my audio sucks, but not that much compared to

00:17:50.519 --> 00:17:52.700
the first videos. And I gave up, you know, I

00:17:52.700 --> 00:17:55.960
recorded like, I don't know, 10 videos, a playlist,

00:17:56.180 --> 00:17:58.500
you know, how to get started with Mac OS, like

00:17:58.500 --> 00:18:01.700
advanced stuff in Mac OS. What I was expecting

00:18:01.700 --> 00:18:05.400
success right away. No, it didn't happen. Gave

00:18:05.400 --> 00:18:08.279
up, stopped for three months. And then I decided

00:18:08.279 --> 00:18:11.660
I'll keep doing this, you know, but I'll do it

00:18:11.660 --> 00:18:14.079
because I want to do it. And here we are like

00:18:14.079 --> 00:18:19.299
a year after. When I started, I did have a proper

00:18:19.299 --> 00:18:22.599
webcam. I had a Logitech webcam, which was OK.

00:18:22.779 --> 00:18:25.500
And kind of like I think it's the C920, kind

00:18:25.500 --> 00:18:27.980
of like a standard webcam that a lot of people

00:18:27.980 --> 00:18:30.660
start using with YouTube. I happen to have one.

00:18:31.119 --> 00:18:33.380
which was great because I didn't go into this

00:18:33.380 --> 00:18:35.700
planning to do YouTube videos. I was just using

00:18:35.700 --> 00:18:37.720
whatever I happened to have. I happened to have

00:18:37.720 --> 00:18:41.859
that camera, which was good. The mic on that

00:18:41.859 --> 00:18:43.539
camera, though, because it does have a built

00:18:43.539 --> 00:18:47.960
-in mic, it's horrible. I had another mic and

00:18:47.960 --> 00:18:51.259
it had no markings on it. It didn't even say

00:18:51.259 --> 00:18:54.700
what brand it was. All it said was made in China.

00:18:55.740 --> 00:19:00.730
And that thing was just barely. Better than the

00:19:00.730 --> 00:19:04.130
camera audio microphones like it was the audio

00:19:04.130 --> 00:19:07.450
on my first few videos was so bad. I was like,

00:19:07.509 --> 00:19:10.369
man, if if I'm going to take this seriously,

00:19:10.549 --> 00:19:13.289
you know, like I've got to do something like

00:19:13.289 --> 00:19:16.150
I got to upgrade. I can't just be using whatever

00:19:16.150 --> 00:19:18.809
random microphone I found in a junk drawer somewhere

00:19:18.809 --> 00:19:21.450
that I pulled out. Don't even know what brand

00:19:21.450 --> 00:19:24.829
it is. So I went and bought a blue Yeti. Oh,

00:19:24.950 --> 00:19:28.539
I think I found a blue Yeti at. Best Buy. I went

00:19:28.539 --> 00:19:30.539
to Best Buy. And they actually had, you know,

00:19:30.539 --> 00:19:32.819
like for gamers, you know, they had microphones

00:19:32.819 --> 00:19:36.019
and stuff. And I was like, oh, that one looks

00:19:36.019 --> 00:19:38.440
all right. I paid a hundred bucks for it at the

00:19:38.440 --> 00:19:41.359
time. And that was like a million times better

00:19:41.359 --> 00:19:44.539
for audio. And then, of course, you know, as

00:19:44.539 --> 00:19:47.619
you go along, you know, you got better equipment

00:19:47.619 --> 00:19:51.599
and better equipment along the way. Would you

00:19:51.599 --> 00:19:53.519
recommend someone starting a channel nowadays?

00:19:53.920 --> 00:19:57.430
You said yes already, but. Oh, yeah. Yeah, because

00:19:57.430 --> 00:20:00.470
I, a lot of people, I think a lot of people are

00:20:00.470 --> 00:20:02.490
under this misconception that YouTube is kind

00:20:02.490 --> 00:20:04.589
of saturated because there's, you know, so many

00:20:04.589 --> 00:20:07.190
YouTubers and so many, you know, billions of

00:20:07.190 --> 00:20:09.390
videos and billions of hours of videos that get

00:20:09.390 --> 00:20:12.690
uploaded like every month. And it's, it's not

00:20:12.690 --> 00:20:14.849
saturated because people are consuming that content,

00:20:14.950 --> 00:20:21.329
you know, and a lot of it is garbage, automated

00:20:21.329 --> 00:20:26.640
spam, AI crap. Unfortunately, YouTube is kind

00:20:26.640 --> 00:20:29.519
of overrun with that kind of stuff. So people

00:20:29.519 --> 00:20:32.660
like listening to a real human being actually

00:20:32.660 --> 00:20:36.500
really talk and discuss things. So, yeah, I don't

00:20:36.500 --> 00:20:41.180
think it's saturated at all. I think people just

00:20:41.180 --> 00:20:43.200
need to get started. Anybody that has considered

00:20:43.200 --> 00:20:46.079
it, you know, just get started. I mean, what's

00:20:46.079 --> 00:20:47.880
the worst that can happen? You make a couple

00:20:47.880 --> 00:20:50.799
of videos and you realize, oh. I'm not very good

00:20:50.799 --> 00:20:53.099
at this or this is a lot of work, which it is

00:20:53.099 --> 00:20:54.460
a lot of work. A lot of people don't realize

00:20:54.460 --> 00:20:57.859
how much work goes into it. But hey, so you do

00:20:57.859 --> 00:21:00.240
it. You make a few videos over a few weeks or

00:21:00.240 --> 00:21:01.779
a few months. You realize, you know what? I'm

00:21:01.779 --> 00:21:04.680
not really into that. OK, well, you didn't really.

00:21:04.799 --> 00:21:08.240
What are you out a few hours of work? Yeah. So,

00:21:08.339 --> 00:21:12.539
OK. Yeah. I think you have to know what to expect.

00:21:12.640 --> 00:21:16.150
Right. Because I was expecting, you know. I don't

00:21:16.150 --> 00:21:18.210
know what I was expecting. It didn't happen.

00:21:18.269 --> 00:21:20.710
So you have to have the right expectations, I

00:21:20.710 --> 00:21:23.089
guess. It's going to take time, right? How long

00:21:23.089 --> 00:21:25.750
did it take for you to see results? Was it in

00:21:25.750 --> 00:21:27.750
the first year? Did it take longer than that?

00:21:27.950 --> 00:21:32.990
No, no. I was actually shocked because I wasn't,

00:21:32.990 --> 00:21:35.890
when I started my YouTube channel, I knew what

00:21:35.890 --> 00:21:37.990
YouTube was. I watched some YouTube. That's why

00:21:37.990 --> 00:21:40.009
I knew there was some Linux content, but it wasn't

00:21:40.009 --> 00:21:42.630
a lot. I didn't expect anybody really to watch

00:21:42.630 --> 00:21:48.319
anything I did. And I became monetized, I think,

00:21:48.339 --> 00:21:51.160
within three months. So I had to get, what, a

00:21:51.160 --> 00:21:54.779
thousand subs and like four thousand watch hours

00:21:54.779 --> 00:21:58.359
or something. The watch time was really easy

00:21:58.359 --> 00:22:00.960
because I got a lot of views on some of those

00:22:00.960 --> 00:22:04.480
early videos. More views than I thought I would.

00:22:04.579 --> 00:22:06.119
And I was kind of shocked that people were interested

00:22:06.119 --> 00:22:09.339
in Linux content. The subs were a little harder

00:22:09.339 --> 00:22:14.079
to come by. But I got a shout out from another

00:22:14.079 --> 00:22:16.819
bigger Linux content creator somewhere along

00:22:16.819 --> 00:22:19.880
the way. That channel was called Big Daddy Linux.

00:22:20.039 --> 00:22:23.720
He's not around anymore. But he helped get me

00:22:23.720 --> 00:22:28.339
to the thousand sub mark, you know, within two

00:22:28.339 --> 00:22:30.220
or three months after starting my channel. And

00:22:30.220 --> 00:22:33.119
from there, I mean, by the end of the first year

00:22:33.119 --> 00:22:36.319
of my channel, I don't remember. It's been so

00:22:36.319 --> 00:22:39.380
long ago. I bet I had 30 or 40 ,000 subs after

00:22:39.380 --> 00:22:43.279
a year. Oh, that's a lot. Yeah. So, and, you

00:22:43.279 --> 00:22:47.119
know, it just keeps going. Okay. Okay. Does it

00:22:47.119 --> 00:22:51.240
keep growing exponentially once you reach a certain

00:22:51.240 --> 00:22:56.359
point? No. Yeah. Yeah. Because I remember, you

00:22:56.359 --> 00:23:00.079
know, really caring about my analytics in the

00:23:00.079 --> 00:23:02.519
first two or three years. I paid attention. I

00:23:02.519 --> 00:23:05.500
mean, views did I get today? I mean, subs did

00:23:05.500 --> 00:23:09.200
I get? I go check my dashboard. I haven't. It

00:23:09.200 --> 00:23:12.299
has been. Seriously, years. I do go into my YouTube

00:23:12.299 --> 00:23:15.180
dashboard to upload. I never check the analytics

00:23:15.180 --> 00:23:18.700
anymore. I don't focus on it anymore. I don't

00:23:18.700 --> 00:23:22.759
care if I get any new subs, new views. You get

00:23:22.759 --> 00:23:27.740
burnout trying to play that game. Now I just

00:23:27.740 --> 00:23:29.660
make the videos I want to make. People watch

00:23:29.660 --> 00:23:32.279
them. Great. They don't watch them. That's fine,

00:23:32.339 --> 00:23:34.359
too. I still made the video I wanted to make,

00:23:34.420 --> 00:23:40.190
doing what I want to do. Yeah, I remember, I

00:23:40.190 --> 00:23:44.589
think it was late 2020, early 2021, the second

00:23:44.589 --> 00:23:49.150
time I came down with COVID. Because I remember

00:23:49.150 --> 00:23:52.490
getting sick. And I remember the channel then

00:23:52.490 --> 00:23:58.670
had like 160, 170 ,000 subs. And I was really

00:23:58.670 --> 00:24:00.750
pushing myself hard, putting out a lot of content

00:24:00.750 --> 00:24:03.769
all the time. Some of these videos, it took a

00:24:03.769 --> 00:24:07.220
lot of effort. hours of prep work and learning

00:24:07.220 --> 00:24:11.700
new things. And I think me pushing myself kind

00:24:11.700 --> 00:24:14.700
of hard was part of the reason that I was getting

00:24:14.700 --> 00:24:18.920
sick. Because I'm not somebody that gets sick

00:24:18.920 --> 00:24:21.640
very often. It's rare. I come down with anything.

00:24:22.200 --> 00:24:25.200
Like, damn, I got COVID two or three times in

00:24:25.200 --> 00:24:27.579
this year. This is a COVID year, though. But

00:24:27.579 --> 00:24:29.920
it was like, hey, I shouldn't be getting this.

00:24:30.240 --> 00:24:34.480
So I kind of backed off a little bit. I made

00:24:34.480 --> 00:24:38.440
a You know, kind of in my head, I told myself,

00:24:38.619 --> 00:24:40.480
OK, you know what? You're going to slow down.

00:24:41.420 --> 00:24:44.319
You're going to keep working, obviously. But,

00:24:44.319 --> 00:24:49.200
you know, we're not I'm not so concerned about

00:24:49.200 --> 00:24:51.720
the analytics anymore. Let's just say that. Yeah,

00:24:51.819 --> 00:24:55.079
that's healthier. Definitely. You want to share

00:24:55.079 --> 00:24:58.440
two of your favorite music bands to get to get

00:24:58.440 --> 00:25:01.640
to know you there since you're into music. Well,

00:25:01.819 --> 00:25:05.799
my music degrees. Obviously, I was a classical

00:25:05.799 --> 00:25:08.160
musician, so I'm mostly into classical music.

00:25:08.539 --> 00:25:12.680
But as far as popular music. What piano or what

00:25:12.680 --> 00:25:14.819
instruments? My main instrument is trombone.

00:25:15.059 --> 00:25:18.019
Okay. I play a few different things, but trombone

00:25:18.019 --> 00:25:21.660
was my main instrument. Okay. And people can

00:25:21.660 --> 00:25:23.359
check out some of my trombone playing on the

00:25:23.359 --> 00:25:25.420
YouTube channel. I have played it in the past.

00:25:25.799 --> 00:25:28.640
Actually, I've played the recorder on the channel

00:25:28.640 --> 00:25:30.960
in the past a few times. I might have played

00:25:30.960 --> 00:25:33.420
the harmonica once or twice. I've got some music

00:25:33.420 --> 00:25:36.400
stuff. Oh, and there's some rap videos as well,

00:25:36.440 --> 00:25:39.579
me rapping. But you don't want to, don't view

00:25:39.579 --> 00:25:45.579
those. But as far as popular music, some of my

00:25:45.579 --> 00:25:50.319
favorite bands, for people that are into metal,

00:25:50.380 --> 00:25:55.299
I'm not a big metal fan, but one of my favorite

00:25:55.299 --> 00:25:58.440
metal musicians from the 80s and 90s is King

00:25:58.440 --> 00:26:03.670
Diamond. Oh, yep. Yep. He is, you know, black

00:26:03.670 --> 00:26:05.849
metal musician, but he is really interesting

00:26:05.849 --> 00:26:10.130
just from his style. Very artsy. Like he actually

00:26:10.130 --> 00:26:13.210
tells a story and basically writes a novel and

00:26:13.210 --> 00:26:15.849
turns it into an album. Each track is a chapter

00:26:15.849 --> 00:26:19.589
of the story. And he with his voice inflection,

00:26:19.609 --> 00:26:22.849
he acts out various characters in the story through

00:26:22.849 --> 00:26:25.910
music. And it's it's very interesting stuff.

00:26:26.539 --> 00:26:30.059
OK, so I really like that for for that particular

00:26:30.059 --> 00:26:35.799
genre. For me growing up, I was born in the 70s,

00:26:35.799 --> 00:26:37.819
but, you know, I grew up in the 80s. So I'm a

00:26:37.819 --> 00:26:41.920
big fan of 80s hair metal, 80s rock bands, bands

00:26:41.920 --> 00:26:45.019
like Bon Jovi and Def Leppard and Journey. All

00:26:45.019 --> 00:26:48.259
that 80s hair music was just that's the best

00:26:48.259 --> 00:26:57.130
stuff ever. Do you like Skid Row? By the time

00:26:57.130 --> 00:27:01.369
they came around, that genre was on the way out

00:27:01.369 --> 00:27:05.390
because of the rise of grunge. Once Nirvana came

00:27:05.390 --> 00:27:10.329
out, the hairband era was over instantly. So

00:27:10.329 --> 00:27:14.269
Skid Row, their first album came out in, what,

00:27:14.289 --> 00:27:17.250
like 89 or 90? So they barely had a couple of

00:27:17.250 --> 00:27:22.190
years before all that was over anyway. But yeah,

00:27:22.250 --> 00:27:24.450
their albums were great, though. They put out

00:27:24.450 --> 00:27:28.009
some amazing music. Okay, so you're more focused

00:27:28.009 --> 00:27:32.529
or you like more metal, rock type of music. All

00:27:32.529 --> 00:27:36.490
genres. I was mentioning those because the audience

00:27:36.490 --> 00:27:39.609
probably is familiar with those artists. Didn't

00:27:39.609 --> 00:27:41.369
want to go down the classical route, but I mean,

00:27:41.390 --> 00:27:45.049
I listen to, I don't like a lot of modern music.

00:27:45.710 --> 00:27:49.910
So like with rock, you know, anything prior to

00:27:49.910 --> 00:27:52.190
like the mid -90s is okay in my book. But once

00:27:52.190 --> 00:27:55.269
we get into all the auto -tune, drum track BS.

00:27:56.480 --> 00:27:59.700
I'm not like you can't hire a real drummer, really.

00:28:00.160 --> 00:28:03.079
And you don't think I can tell that that's not

00:28:03.079 --> 00:28:04.819
a real human being playing these instruments.

00:28:05.039 --> 00:28:10.200
It sounds very soulless. It's just not it's not

00:28:10.200 --> 00:28:13.980
good. But don't get me started on that. So I

00:28:13.980 --> 00:28:16.400
listen to a lot of older rock country music,

00:28:16.480 --> 00:28:19.660
again, older country, mostly because, again,

00:28:19.839 --> 00:28:23.680
modern music, a lot of times not that great.

00:28:25.009 --> 00:28:30.329
like some old reggae, like reggae, some of the

00:28:30.329 --> 00:28:35.390
old rap, hip -hop stuff, you know, that when

00:28:35.390 --> 00:28:39.130
I was, say, in high school or in college that

00:28:39.130 --> 00:28:42.029
was popular. So the earlier stuff with folks

00:28:42.029 --> 00:28:45.890
like Snoop Dogg, Dr. Dre, and then, you know,

00:28:45.890 --> 00:28:49.230
Tupac and Biggie, right? I love all that. The

00:28:49.230 --> 00:28:54.819
new stuff, not as good. Again, maybe I'm just

00:28:54.819 --> 00:28:59.480
a boomer, right? Yeah, I like old music as well.

00:28:59.619 --> 00:29:02.680
You know, 80s, 90s music. 80s is my favorite.

00:29:02.759 --> 00:29:05.680
I like listening to Earth, Wind & Fire, stuff

00:29:05.680 --> 00:29:09.140
like that. Oh yeah, Earth, Wind & Fire was awesome.

00:29:09.680 --> 00:29:13.339
Of course, being a trombone player, any group

00:29:13.339 --> 00:29:16.039
that has a brass section. So Earth, Wind & Fire,

00:29:16.279 --> 00:29:20.150
yeah, awesome. What is this other one? Chicago

00:29:20.150 --> 00:29:23.089
is another one. You know Chicago? Yeah. Especially

00:29:23.089 --> 00:29:25.849
from the 60s and 70s when, you know, actually

00:29:25.849 --> 00:29:28.849
one of their founding members, Jim Hankel, is

00:29:28.849 --> 00:29:30.509
the trombone player. He actually founded the

00:29:30.509 --> 00:29:34.250
group. And what about Kool and the Gang? They

00:29:34.250 --> 00:29:37.230
have a brass section too, right? Yeah, everybody

00:29:37.230 --> 00:29:41.029
loves Kool and the Gang. You can't go to a party

00:29:41.029 --> 00:29:43.849
without hearing Celebration. Yeah, definitely.

00:29:44.269 --> 00:29:47.609
And what about movies? You like movies? You want

00:29:47.609 --> 00:29:51.349
to share two with us? Yeah. You know what? Again,

00:29:51.450 --> 00:29:54.289
I'm going to sound like a boomer, but movies

00:29:54.289 --> 00:29:59.589
have gone way downhill, say, in the last 10,

00:29:59.630 --> 00:30:06.410
15 years. It is all CGI all the time. And I can't

00:30:06.410 --> 00:30:09.710
stand it. But movies that I actually like, as

00:30:09.710 --> 00:30:12.269
far as favorite movies of all time, one of my

00:30:12.269 --> 00:30:17.700
all -time favorites is Aliens. James Cameron's

00:30:17.700 --> 00:30:22.519
Aliens. That movie, I just watch it all the time.

00:30:22.619 --> 00:30:24.240
Anytime it's on, I've got to watch the whole

00:30:24.240 --> 00:30:25.920
thing. And it's a longer movie. It's like a two

00:30:25.920 --> 00:30:28.480
and a half hour movie. It's an investment. But

00:30:28.480 --> 00:30:30.839
it's such a damn good movie. Just the acting.

00:30:31.099 --> 00:30:34.500
It's hilarious. Some of the lines in it. Especially

00:30:34.500 --> 00:30:37.680
Bill Paxton's character in that movie just cracks

00:30:37.680 --> 00:30:40.180
me up. And then, of course, the action. A lot

00:30:40.180 --> 00:30:42.599
of shooting, explosions, and the horror elements

00:30:42.599 --> 00:30:47.440
as well. It's like the perfect movie. And it's

00:30:47.440 --> 00:30:49.799
all practical effects. This was before CGI was

00:30:49.799 --> 00:30:52.940
even a thing. Right. So like the creatures and

00:30:52.940 --> 00:30:54.380
everything, they had to actually build those

00:30:54.380 --> 00:30:57.140
puppets and those models. And it looks so good.

00:30:57.200 --> 00:31:01.119
If they made that movie now, it would be such

00:31:01.119 --> 00:31:03.619
a turd. Yeah. Because, you know, they wouldn't

00:31:03.619 --> 00:31:07.539
build the first set and the first actual model.

00:31:07.680 --> 00:31:09.640
You know, it would just all be computerized.

00:31:09.900 --> 00:31:12.359
Yeah. And it wouldn't be nearly. And you can

00:31:12.359 --> 00:31:15.430
tell. Yes. People from the old school can tell,

00:31:15.509 --> 00:31:18.990
I guess. I don't know if younger generations

00:31:18.990 --> 00:31:22.309
care about that or not, but yeah, I do care.

00:31:22.329 --> 00:31:24.029
I think a lot of them do, because I've noticed

00:31:24.029 --> 00:31:26.569
some young people, when they go back and look

00:31:26.569 --> 00:31:29.509
at like classic sci -fi horror movies, anything

00:31:29.509 --> 00:31:32.450
with a creature or a monster, they're like, oh,

00:31:32.490 --> 00:31:35.490
that looks really good. You know, it doesn't

00:31:35.490 --> 00:31:38.130
look like this Marvel movie I just watched that,

00:31:38.150 --> 00:31:40.529
you know, you can tell. But, you know, when they

00:31:40.529 --> 00:31:45.940
see. I don't know. Things like Alien or John

00:31:45.940 --> 00:31:48.539
Carpenter's The Thing. I don't know if you're

00:31:48.539 --> 00:31:51.740
familiar with it. But that thing, whoever did

00:31:51.740 --> 00:31:55.180
the special effects on that, props to you, guy.

00:31:55.299 --> 00:31:59.140
Because that's an amazing movie. I still sit

00:31:59.140 --> 00:32:01.279
there and look at some of those scenes and wonder,

00:32:01.359 --> 00:32:04.200
how in the hell did they do that? Because this

00:32:04.200 --> 00:32:07.119
was definitely before computers and CGI were

00:32:07.119 --> 00:32:11.579
a thing in movies. Yeah. Or like, like this other

00:32:11.579 --> 00:32:16.180
one, the fly, it's horrible. Yeah. But the, the

00:32:16.180 --> 00:32:20.319
effects, you know, man looks, I remember watching

00:32:20.319 --> 00:32:24.079
it as a kid and it was disgusting, but it's,

00:32:24.119 --> 00:32:27.019
well, that's more of a, yeah, well, it was supposed

00:32:27.019 --> 00:32:30.599
to be disgusting. That was, uh, it was designed

00:32:30.599 --> 00:32:33.640
to be body horror is what they call it. Right.

00:32:33.660 --> 00:32:36.799
That's when, you know, somebody's body is. It's

00:32:36.799 --> 00:32:38.880
scaring you because it's going through whatever

00:32:38.880 --> 00:32:41.619
transformations or being infected by bugs or,

00:32:41.640 --> 00:32:44.420
you know, I was never a fan of those kinds of

00:32:44.420 --> 00:32:48.019
films myself. But The Fly, as far as the effects

00:32:48.019 --> 00:32:50.180
in it. Yeah. Special effects are amazing in that

00:32:50.180 --> 00:32:53.500
thing, too. Yeah. What about video games? Are

00:32:53.500 --> 00:32:55.380
you into video games? What are your thoughts

00:32:55.380 --> 00:33:01.799
there? I don't game much. And. Yeah, I'm not

00:33:01.799 --> 00:33:04.019
really a hardcore gamer at all. I don't own a

00:33:04.019 --> 00:33:07.609
lot of games. I have a Steam account. But I don't

00:33:07.609 --> 00:33:10.950
really own anything. I own Cities Skylines. I've

00:33:10.950 --> 00:33:15.710
played it. I've got a few other. I don't know.

00:33:15.769 --> 00:33:18.710
I really don't own any games. I do play some

00:33:18.710 --> 00:33:20.589
of the free and open source games that are available

00:33:20.589 --> 00:33:23.890
on Linux. Just because for a long time, that

00:33:23.890 --> 00:33:26.849
was all I had on Linux. We didn't have Steam.

00:33:26.910 --> 00:33:30.230
We had no games. We just had a few mostly open

00:33:30.230 --> 00:33:34.049
source first person shooters. I still play a

00:33:34.049 --> 00:33:37.140
lot of those. I play a little bit of a game called

00:33:37.140 --> 00:33:40.140
Sauerbraten. Fantastic game. Free and open source,

00:33:40.279 --> 00:33:44.480
first -person shooter. Zenotic, another good

00:33:44.480 --> 00:33:48.319
first -person shooter, open source. And I do

00:33:48.319 --> 00:33:50.759
play a real -time strategy game called Zero A

00:33:50.759 --> 00:33:54.119
.D. Also free and open source software. Just

00:33:54.119 --> 00:33:56.079
a fantastic game. If you're a fan of the old

00:33:56.079 --> 00:34:00.220
Age of Empires games, Zero A .D. is amazing.

00:34:00.740 --> 00:34:07.960
Okay. This one? Yes. Okay. Okay. And you don't

00:34:07.960 --> 00:34:10.519
play because of time or? Yeah, you're right.

00:34:10.619 --> 00:34:12.280
I don't play because it takes a lot of time.

00:34:12.320 --> 00:34:16.139
Typically, I'm always doing something. And when

00:34:16.139 --> 00:34:19.980
I sit down to play a game, it's for like I'm

00:34:19.980 --> 00:34:23.139
really wore out from doing everything else going

00:34:23.139 --> 00:34:26.300
on. I just want to, for example, pull up a first

00:34:26.300 --> 00:34:28.500
person shooter and frag as many people as I can

00:34:28.500 --> 00:34:31.260
for 15 minutes and then get out. I'm not one

00:34:31.260 --> 00:34:34.980
of these people that play like a. RPG game that's

00:34:34.980 --> 00:34:37.639
like some of the massive multiplayer games that

00:34:37.639 --> 00:34:39.599
are going to take me six weeks to complete and

00:34:39.599 --> 00:34:43.119
I got to spend eight hours a day. Not doing that.

00:34:43.320 --> 00:34:45.659
Yeah, you have to choose your time. Everything

00:34:45.659 --> 00:34:50.400
I play is something that can be done in a few

00:34:50.400 --> 00:34:53.260
minutes or like a game of Zero AD might run an

00:34:53.260 --> 00:34:56.980
hour or so, depending on number of opponents

00:34:56.980 --> 00:34:59.760
and whether I'm winning or not. If I'm losing,

00:34:59.840 --> 00:35:03.010
it'll be over quick. Yeah, it makes sense. I

00:35:03.010 --> 00:35:06.010
feel the same way. I'm like, I could be doing

00:35:06.010 --> 00:35:07.869
something else. That's what I think, you know,

00:35:07.889 --> 00:35:10.070
I should be doing something else. I feel like

00:35:10.070 --> 00:35:13.690
I'm just not being, even though I'm not being

00:35:13.690 --> 00:35:15.690
productive doing something else, I feel like

00:35:15.690 --> 00:35:18.409
I'm just, I could be doing something better,

00:35:18.469 --> 00:35:20.929
but that's just me, my personal feeling. And

00:35:20.929 --> 00:35:26.050
moving on to other topics, what's your ID or

00:35:26.050 --> 00:35:31.619
editor of choice? Is it Emacs or? Yeah. That's

00:35:31.619 --> 00:35:35.360
where I spend most of my time in is Emacs. I

00:35:35.360 --> 00:35:38.579
have Vim and NeoVim installed on my system. I

00:35:38.579 --> 00:35:43.579
do use them often, too. It just depends. A lot

00:35:43.579 --> 00:35:46.780
of times, whatever I'm doing on camera, if I'm

00:35:46.780 --> 00:35:49.219
already in a terminal emulator and then I want

00:35:49.219 --> 00:35:51.260
to open something, I'll typically use NeoVim

00:35:51.260 --> 00:35:55.739
for it. If I'm specifically doing something already

00:35:55.739 --> 00:36:01.710
using Emacs, I'll be in Emacs. But I could use

00:36:01.710 --> 00:36:06.510
either one. But I mean, if I if I didn't do the

00:36:06.510 --> 00:36:08.090
YouTube channel, typically I'd probably just

00:36:08.090 --> 00:36:10.429
live in Emacs. I'd open Emacs full screen and

00:36:10.429 --> 00:36:12.449
that would be my desktop environment. It would

00:36:12.449 --> 00:36:15.670
essentially be my operating system because, well,

00:36:15.769 --> 00:36:19.010
if I move to my screen here, I mean, a typical

00:36:19.010 --> 00:36:21.829
kind of Emacs workflow would be you just, you

00:36:21.829 --> 00:36:24.329
know, you open. Let me make sure I'm on the right

00:36:24.329 --> 00:36:27.840
monitor here. Open Emacs. You know, and then

00:36:27.840 --> 00:36:32.019
I could navigate to anything I want to view.

00:36:32.079 --> 00:36:34.940
Maybe, I don't know, my Qtile config, which is

00:36:34.940 --> 00:36:37.099
the window manager I'm in. It's my Qtile config,

00:36:37.260 --> 00:36:40.880
which is written in org mode, by the way. I wrote

00:36:40.880 --> 00:36:43.840
the config. It actually, you know, the source

00:36:43.840 --> 00:36:46.539
code blocks, you know, you can say begin source

00:36:46.539 --> 00:36:50.139
Python. So I've got the Python code in the source

00:36:50.139 --> 00:36:52.710
code blocks. But, you know, the... the headers

00:36:52.710 --> 00:36:54.590
of the table of contents and the descriptions,

00:36:54.769 --> 00:36:56.989
these are all just part of the literate config,

00:36:57.170 --> 00:36:59.429
the org document. They don't get written to the

00:36:59.429 --> 00:37:03.230
proper config .py, but these source code blocks

00:37:03.230 --> 00:37:06.150
do. They get written to the actual config later

00:37:06.150 --> 00:37:09.710
when I save. But, you know, you'll work in something,

00:37:09.829 --> 00:37:12.329
a text document. If I need a terminal, I could

00:37:12.329 --> 00:37:15.409
do, in my case, space tv is the key binding I

00:37:15.409 --> 00:37:17.829
have to toggle on vterm. vterm is one of the

00:37:17.829 --> 00:37:21.610
terminal emulators here inside Emacs. If I need

00:37:21.610 --> 00:37:25.110
a proper terminal, this is the term, using my

00:37:25.110 --> 00:37:27.389
shell, the fish shell, using my fish config and

00:37:27.389 --> 00:37:29.730
everything. So I've got a terminal inside Emacs

00:37:29.730 --> 00:37:32.949
if I need it. I don't really need another terminal.

00:37:33.329 --> 00:37:35.349
Yeah, you don't need to go out. And I noticed

00:37:35.349 --> 00:37:38.449
that your headings in org mode are bigger because

00:37:38.449 --> 00:37:41.610
I know a little bit about org mode only. Is that

00:37:41.610 --> 00:37:44.170
a default thing in Emacs? You can make the headings

00:37:44.170 --> 00:37:47.750
bigger? There's nothing default in Emacs because

00:37:47.750 --> 00:37:53.760
you have to configure it yourself. So, no. Everything

00:37:53.760 --> 00:37:56.920
you see here, yeah, I had to do a settings for.

00:37:57.000 --> 00:38:00.659
Let me get into my Emacs config. I have a key

00:38:00.659 --> 00:38:02.920
binding to get into that config. This is my Emacs

00:38:02.920 --> 00:38:07.340
config. And if I go to the table of contents

00:38:07.340 --> 00:38:10.639
here, I've got a section, org mode, bullets.

00:38:10.699 --> 00:38:15.860
Here we go. So, org bullets is the package that

00:38:15.860 --> 00:38:19.159
I installed to get the fancy bullets. Because

00:38:19.159 --> 00:38:21.800
otherwise, these would just be asterisks. This

00:38:21.800 --> 00:38:25.500
would be one asterisk. This would be two. But

00:38:25.500 --> 00:38:27.920
it condenses it to one character. And then, you

00:38:27.920 --> 00:38:30.500
know, the specific shape and color that I could

00:38:30.500 --> 00:38:33.780
set. Same thing if I went down a third level.

00:38:33.860 --> 00:38:38.000
You know, if I wanted a third level, right? Third

00:38:38.000 --> 00:38:41.659
level, whatever. Obviously, I don't want to do

00:38:41.659 --> 00:38:44.559
that to my config. But it would convert that

00:38:44.559 --> 00:38:48.539
to whatever symbol. As far as why the heading

00:38:48.539 --> 00:38:52.699
is bigger, that is in my fonts section. Let's

00:38:52.699 --> 00:38:59.619
see, fonts. I did learn about this type of configuration

00:38:59.619 --> 00:39:02.559
because Joshua Blaze mentioned it. I had a call

00:39:02.559 --> 00:39:05.920
with him and he showed me around Emacs. So what

00:39:05.920 --> 00:39:09.039
is this called again? Where you document and

00:39:09.039 --> 00:39:12.699
configure at the same time, right? Literate.

00:39:12.699 --> 00:39:16.079
Yeah, literate config. Yeah. Okay. Yeah, it's

00:39:16.079 --> 00:39:20.739
basically where you write something that serves

00:39:20.739 --> 00:39:23.300
as documentation, but it is also the source code

00:39:23.300 --> 00:39:27.960
for something as well. The blocks, in this case,

00:39:28.019 --> 00:39:32.780
what this does, the actual Emacs config is config

00:39:32.780 --> 00:39:38.480
.el. This file is config .org, though. Now, what

00:39:38.480 --> 00:39:41.340
it does is it writes all the source code blocks

00:39:41.340 --> 00:39:44.099
that are. you know emacs list source code blocks

00:39:44.099 --> 00:39:48.179
it writes that over to the config .el so it that's

00:39:48.179 --> 00:39:51.780
but like the headers and all of this it doesn't

00:39:51.780 --> 00:39:54.980
do anything to those which is great because if

00:39:54.980 --> 00:40:01.360
i go to my gitlab go to my dot files repository

00:40:01.360 --> 00:40:05.380
for example okay so all of your emacs config

00:40:05.380 --> 00:40:09.039
is in your dot files in gitlab right It is. Go

00:40:09.039 --> 00:40:12.800
to .config slash emacs. This is the folders where

00:40:12.800 --> 00:40:15.159
your emacs config would be on a Linux system.

00:40:15.519 --> 00:40:18.719
And if I go to config .org, you know, it's a

00:40:18.719 --> 00:40:21.400
proper document with a table of contents and,

00:40:21.500 --> 00:40:23.260
you know, nice formatting and everything. You

00:40:23.260 --> 00:40:25.920
can actually read it. Now, these blocks are the

00:40:25.920 --> 00:40:28.239
actual source code blocks for the file config

00:40:28.239 --> 00:40:31.199
.el. Like, if you want to go read that, you could

00:40:31.199 --> 00:40:33.739
go read that. But who wants to do that, right?

00:40:33.800 --> 00:40:36.219
It's much easier to read the config .org, right?

00:40:36.519 --> 00:40:38.619
Especially if you don't know anything about Emacs.

00:40:38.900 --> 00:40:42.559
Because, you know, I'm pretty wordy as far as

00:40:42.559 --> 00:40:44.980
describing things. Like I tell you, hey, this

00:40:44.980 --> 00:40:47.099
block, this is what I'm doing. That's why I wrote

00:40:47.099 --> 00:40:49.159
this block this way. This package, this is what

00:40:49.159 --> 00:40:52.719
this package does. Yada, yada, yada, right? Some

00:40:52.719 --> 00:40:55.260
of them, I even like write tables for like key

00:40:55.260 --> 00:40:56.960
bindings and things, you know, things that are

00:40:56.960 --> 00:40:58.920
not part of the actual source code, but, you

00:40:58.920 --> 00:41:02.369
know, help people, you know. Right here. This

00:41:02.369 --> 00:41:06.130
is a table. Like, hey, I installed this package,

00:41:06.269 --> 00:41:08.510
org tempo. You don't know what it does? Well,

00:41:08.530 --> 00:41:12.789
here's what it does. Type your less than sign

00:41:12.789 --> 00:41:16.309
A and then tab, and it's going to add this into

00:41:16.309 --> 00:41:20.090
the file. This block here. So, actually, I can

00:41:20.090 --> 00:41:24.570
show you that. The source code blocks, if I want

00:41:24.570 --> 00:41:28.309
to add one, let me do the less than sign S and

00:41:28.309 --> 00:41:31.900
hit tab. Oh. There's my source block. Snippet.

00:41:31.920 --> 00:41:35.019
Yeah. And then what am I writing? Well, in this

00:41:35.019 --> 00:41:37.539
case, I would be writing emacs list, but I could,

00:41:37.539 --> 00:41:40.139
you know, obviously do something like bash or

00:41:40.139 --> 00:41:44.019
Python or Haskell, you know, whatever it is,

00:41:44.039 --> 00:41:45.659
you know, whatever it is you're trying to write.

00:41:46.400 --> 00:41:49.159
Let me undo all of that because this is my proper

00:41:49.159 --> 00:41:53.820
config. Yeah, it seems extremely useful, actually.

00:41:53.940 --> 00:41:56.099
And how did you make the heading speaker then?

00:41:56.199 --> 00:41:58.940
Is this this? Oh, this is it. This block that

00:41:58.940 --> 00:42:02.420
I was searching for. org level headers so there

00:42:02.420 --> 00:42:05.500
is these variables here org level one through

00:42:05.500 --> 00:42:10.260
seven and i set them to various heights 1 .7

00:42:10.260 --> 00:42:13.460
for the top level so that would be top level

00:42:13.460 --> 00:42:17.780
this okay and then you know org level two would

00:42:17.780 --> 00:42:21.099
be these org level three which i don't think

00:42:21.099 --> 00:42:24.019
i have a lot of third level uh things in this

00:42:24.019 --> 00:42:28.579
document but i mean we could quickly add some

00:42:31.420 --> 00:42:40.559
And fourth. And. Five. And so forth, you know,

00:42:40.559 --> 00:42:45.739
six. Yada, yada, yada. Yes. Yeah. It makes this.

00:42:45.800 --> 00:42:49.699
Yeah. Much easier to read. There's also similar

00:42:49.699 --> 00:42:52.699
variables for those of you that like to play

00:42:52.699 --> 00:42:55.510
in Markdown. You can also set the headers in

00:42:55.510 --> 00:42:58.389
a markdown document in Emacs to be variable.

00:42:58.650 --> 00:43:02.630
Oh, for markdown files. Okay. Okay. But that

00:43:02.630 --> 00:43:06.409
is possible in Emacs because any of them people

00:43:06.409 --> 00:43:08.789
have asked, I'm going to switch to my screen

00:43:08.789 --> 00:43:11.570
real quick. Any of them, I can't, right? So,

00:43:11.670 --> 00:43:14.369
or at least, I don't know, maybe it's possible.

00:43:14.550 --> 00:43:19.309
I don't know. So I had to, you know, set. the

00:43:19.309 --> 00:43:22.170
background for the different headings. That's

00:43:22.170 --> 00:43:24.369
the way I can tell, okay, heading level two,

00:43:24.530 --> 00:43:27.469
heading level three by the colors. I leave the

00:43:27.469 --> 00:43:29.690
number on the left side of it, you know, but

00:43:29.690 --> 00:43:35.610
having a bigger font is also pretty useful. Yeah.

00:43:35.610 --> 00:43:38.449
And if you prefer, instead of doing the bigger

00:43:38.449 --> 00:43:40.670
font, if you prefer doing background colors,

00:43:40.750 --> 00:43:43.369
you certainly can theme things in that way. You

00:43:43.369 --> 00:43:45.619
can actually see. Probably barely because it's

00:43:45.619 --> 00:43:48.219
just a slight hinting. My source code blocks

00:43:48.219 --> 00:43:50.820
are a little darker than the rest. Yeah, you

00:43:50.820 --> 00:43:53.480
can see it. But you can also set that for some

00:43:53.480 --> 00:43:55.679
people that have their cursor line, you know,

00:43:55.679 --> 00:43:57.099
a different color. So it's obvious where the

00:43:57.099 --> 00:43:59.079
cursor is. In my case, I have my cursor blinking

00:43:59.079 --> 00:44:01.699
when it moves. That way I know where it's at.

00:44:03.760 --> 00:44:08.500
Okay. It's all available. Okay. One thing with

00:44:08.500 --> 00:44:13.019
Emacs, the reason I get this variable font size.

00:44:13.579 --> 00:44:16.019
It's because Emacs is an actual graphical application.

00:44:16.099 --> 00:44:19.900
It's a GUI window, not a terminal. Where a terminal,

00:44:20.099 --> 00:44:22.280
unfortunately, the limitation of a terminal is

00:44:22.280 --> 00:44:25.940
everything has to be the same size font. You

00:44:25.940 --> 00:44:28.159
can't have variable font sizes in a terminal,

00:44:28.219 --> 00:44:31.719
unfortunately. And if I used Emacs, Emacs does

00:44:31.719 --> 00:44:36.099
have a terminal version. In case you're stuck

00:44:36.099 --> 00:44:39.219
in a TTY. You can actually run Emacs inside a

00:44:39.219 --> 00:44:41.320
terminal, but it would have the same limitations

00:44:41.320 --> 00:44:43.420
of something like Vim or NeoVim. You're not going

00:44:43.420 --> 00:44:45.800
to get the fancy bullets and everything in the

00:44:45.800 --> 00:44:49.760
TTY. Okay, makes sense. But, you know, if you're

00:44:49.760 --> 00:44:51.860
in a bind, you're stuck in a TTY, it doesn't

00:44:51.860 --> 00:44:53.159
really matter. You're not worried about images

00:44:53.159 --> 00:44:57.019
and things in a TTY. Why do you go out of Emacs,

00:44:57.179 --> 00:45:00.179
though? Like, why not, like you said, right?

00:45:00.599 --> 00:45:04.519
Why do you sometimes go out of Emacs and do stuff

00:45:04.519 --> 00:45:07.059
in the terminal? Well, a lot of what I do on

00:45:07.059 --> 00:45:11.000
camera is stuff I'm doing at the shill anyway.

00:45:11.920 --> 00:45:14.699
And I'm going to spend almost all my time in

00:45:14.699 --> 00:45:17.639
a terminal. I don't launch Emacs just to then

00:45:17.639 --> 00:45:20.800
launch it. I'll just launch my terminal. Like

00:45:20.800 --> 00:45:25.539
a lot of the videos I do. Just me launching a

00:45:25.539 --> 00:45:29.559
terminal, zooming way in and discussing whatever.

00:45:30.340 --> 00:45:32.539
I'm going to do a tutorial today on various.

00:45:33.079 --> 00:45:35.519
core utilities, whatever it happens to be, LS

00:45:35.519 --> 00:45:39.920
or, you know, CP for copy and MV for, you know,

00:45:39.920 --> 00:45:41.880
I do all this in a terminal. There's no reason

00:45:41.880 --> 00:45:44.840
for me to be an Emacs for this. I'm not ever

00:45:44.840 --> 00:45:47.219
going to edit text. A lot of the other stuff

00:45:47.219 --> 00:45:50.019
that comes with Emacs, I mean, it's got Git clients

00:45:50.019 --> 00:45:52.539
and things like that. I'm not doing any of that

00:45:52.539 --> 00:45:56.500
kind of stuff because Emacs really, once you've

00:45:56.500 --> 00:45:59.619
configured it with all that crap, it's really

00:45:59.619 --> 00:46:02.630
an IDE. And if all I need is a terminal, I'm

00:46:02.630 --> 00:46:04.769
just going to open the terminal. In this case,

00:46:04.789 --> 00:46:07.510
I'm using Alacrity for the terminal here. Alacrity.

00:46:07.590 --> 00:46:11.429
Okay. That's a good point to touch. Why Alacrity?

00:46:11.530 --> 00:46:14.289
Why haven't you moved on to something else? Because

00:46:14.289 --> 00:46:17.670
everyone's like, now Ghosty. That's like the

00:46:17.670 --> 00:46:20.269
trend topic. Ghosty. Before that, what was it?

00:46:20.289 --> 00:46:24.670
Western, Kitty. Why Alacrity? I mean, I've played

00:46:24.670 --> 00:46:27.210
with all of them. I did a video recently about

00:46:27.210 --> 00:46:31.599
Ghosty. And it's okay. My thing with Alacrity,

00:46:31.659 --> 00:46:34.300
a lot of times with my terminals, the way I use

00:46:34.300 --> 00:46:37.599
them, I want an empty frame. I don't want any

00:46:37.599 --> 00:46:40.099
title bars, headers, or anything. I just want

00:46:40.099 --> 00:46:43.539
a plain terminal window that's simple to configure.

00:46:43.739 --> 00:46:46.019
The Alacrity configuration file is really easy

00:46:46.019 --> 00:46:47.960
to work with if you want to add key bindings

00:46:47.960 --> 00:46:51.260
or theme, like with my colors. You know, you

00:46:51.260 --> 00:46:53.300
saw the color scheme. Basically the same color

00:46:53.300 --> 00:46:56.119
scheme I use in Emacs and everywhere else I've

00:46:56.119 --> 00:47:00.650
got going on in Alacrity. But it's also, it just

00:47:00.650 --> 00:47:04.650
works. One of the things with Alacrity, you know,

00:47:04.690 --> 00:47:06.329
I first tried it out like four or five years

00:47:06.329 --> 00:47:10.289
ago. I made a video about it. And Alacrity was

00:47:10.289 --> 00:47:13.309
still kind of new at the time. I might have been

00:47:13.309 --> 00:47:15.409
part of the reason why Alacrity has become kind

00:47:15.409 --> 00:47:18.010
of popular because that video got a lot of views

00:47:18.010 --> 00:47:20.510
at the time. And it kind of, you know, a lot

00:47:20.510 --> 00:47:22.230
of people have tried Alacrity since then. It's

00:47:22.230 --> 00:47:24.789
like the default terminal emulator on some Linux

00:47:24.789 --> 00:47:27.349
distributions. Like it's really become kind of

00:47:27.349 --> 00:47:30.440
a standard. One of the cool things with it was

00:47:30.440 --> 00:47:33.079
Unicode support. I don't know if you use a lot

00:47:33.079 --> 00:47:37.360
of weird Unicode glyphs and symbols in your terminal,

00:47:37.500 --> 00:47:42.000
but some terminal emulators really suck at displaying

00:47:42.000 --> 00:47:45.179
some of that. A lot of the older terminal emulators

00:47:45.179 --> 00:47:47.880
that people were using before, things like Alacrity

00:47:47.880 --> 00:47:52.639
and Kitty and Westerm came along. Xterm gets

00:47:52.639 --> 00:47:55.719
installed. Well, it's not really installed with

00:47:55.719 --> 00:47:58.699
the... X11 server, but usually you're going to

00:47:58.699 --> 00:48:01.219
install Xterm. At least that was kind of a de

00:48:01.219 --> 00:48:04.300
facto standard, say, 20 years ago on Linux. Xterm

00:48:04.300 --> 00:48:07.619
sucks for Unicode support. There's going to be

00:48:07.619 --> 00:48:09.099
a lot of weird things that you're going to try

00:48:09.099 --> 00:48:10.739
to display in that terminal, and it just can't

00:48:10.739 --> 00:48:14.800
display it. It can't render. URXVT is another

00:48:14.800 --> 00:48:17.820
very popular terminal emulator that was really

00:48:17.820 --> 00:48:20.559
maybe the most popular terminal emulator when

00:48:20.559 --> 00:48:24.440
I got started on Linux, especially from like

00:48:24.440 --> 00:48:27.409
the People that were tiling window manager users,

00:48:27.409 --> 00:48:29.510
people that lived in the terminal, that was the

00:48:29.510 --> 00:48:33.090
one they all promoted, URXVT. It probably has

00:48:33.090 --> 00:48:36.070
the worst Unicode support of any terminal emulator

00:48:36.070 --> 00:48:39.150
I've ever tried. Its claim to fame was it was

00:48:39.150 --> 00:48:42.489
fast and it had a daemon associated with it.

00:48:42.550 --> 00:48:45.610
So there was always this URXVT server running

00:48:45.610 --> 00:48:48.650
in the background. So it's a server -client relationship

00:48:48.650 --> 00:48:52.650
with your windows, which made your terminals

00:48:52.650 --> 00:48:56.239
launch faster. Great. But it also made, hey,

00:48:56.260 --> 00:48:59.139
when one terminal window crashed, and they're

00:48:59.139 --> 00:49:01.079
all part of the server -client relationship,

00:49:01.320 --> 00:49:05.320
all your terminal windows crashed. So you don't

00:49:05.320 --> 00:49:08.480
like that aspect with it. So, yeah, Alacrity

00:49:08.480 --> 00:49:10.260
just, yeah, it solved a lot of problems when

00:49:10.260 --> 00:49:12.519
it came out, right? It was so much better than

00:49:12.519 --> 00:49:16.079
a lot of the stuff that was around. And obviously,

00:49:16.559 --> 00:49:18.639
it's very popular. It receives a lot of development.

00:49:20.329 --> 00:49:22.750
And it doesn't come with a lot of the extra bells

00:49:22.750 --> 00:49:25.690
and whistles I don't need. I know a lot of people

00:49:25.690 --> 00:49:28.869
really like terminal emulators that have splits

00:49:28.869 --> 00:49:34.710
and tabs. I've never needed, I've never, because

00:49:34.710 --> 00:49:39.489
if you really need a split or a tab, you know,

00:49:39.489 --> 00:49:43.650
we have things like TMUX and GNU Screen for multiplexing.

00:49:43.710 --> 00:49:48.050
If you really need it, if you're in a TTY, most

00:49:48.050 --> 00:49:50.840
of the time I'm not in a TTY. And I use a tiling

00:49:50.840 --> 00:49:54.400
window manager. If I need a split, I just open

00:49:54.400 --> 00:49:58.280
a second terminal. If I'm looking at my screen

00:49:58.280 --> 00:50:01.320
right now. So if I need terminals, I've got all

00:50:01.320 --> 00:50:03.280
the terminals available in my window manager,

00:50:03.380 --> 00:50:06.400
which can manage those things just as good as

00:50:06.400 --> 00:50:09.659
buffers and splits. And that's another thing.

00:50:09.699 --> 00:50:11.679
If I'm in a terminal and I'm in either Vim or

00:50:11.679 --> 00:50:14.960
Emacs, I don't need the terminal to manage any

00:50:14.960 --> 00:50:18.730
of that stuff. But a lot of it is probably just

00:50:18.730 --> 00:50:21.389
what you've grown used to. Like if you've always

00:50:21.389 --> 00:50:24.969
used splits and tabs in a terminal, I guess that's

00:50:24.969 --> 00:50:27.050
what you're used to. For me, I've always used

00:50:27.050 --> 00:50:29.510
other things for that kind of stuff if I needed

00:50:29.510 --> 00:50:33.190
it. Yep. I used tabs in the past in terminals.

00:50:33.329 --> 00:50:36.449
I used a macOS terminal. It's called iTerm2.

00:50:37.050 --> 00:50:41.469
Then I met other terminals, Alacrity. I installed

00:50:41.469 --> 00:50:44.590
Alacrity. I loved it. But I had to use Tmux,

00:50:44.730 --> 00:50:47.110
right? Because I'm in macOS. Tmux. So I'm a huge

00:50:47.110 --> 00:50:50.929
Tmux fan. I use Tmux. What I love the most about

00:50:50.929 --> 00:50:54.050
Tmux is sessions, right? Because that's what

00:50:54.050 --> 00:50:55.949
allows me to switch between projects, right?

00:50:56.030 --> 00:50:58.949
So here I'm in my notes with a single key press,

00:50:59.130 --> 00:51:02.469
right? I'm in my .files, right? If I type that

00:51:02.469 --> 00:51:04.889
other key press or I can jump back to my notes

00:51:04.889 --> 00:51:10.039
or to my home directory. So that's... why I love

00:51:10.039 --> 00:51:12.000
Tmux and I love the lacquerty. I used it for

00:51:12.000 --> 00:51:14.119
a long time because I didn't need, like you said,

00:51:14.260 --> 00:51:16.659
I didn't need tabs. I don't like tabs in the

00:51:16.659 --> 00:51:19.059
terminal. I didn't need panes because I have

00:51:19.059 --> 00:51:22.659
Tmux for that, you know? And that was with other

00:51:22.659 --> 00:51:24.679
terminals that did come with that stuff out of

00:51:24.679 --> 00:51:27.420
the box. I always turned them off anyway. So

00:51:27.420 --> 00:51:30.219
it's just nice not to have to fool with turning

00:51:30.219 --> 00:51:32.340
that stuff off, like scroll bars and all that.

00:51:32.559 --> 00:51:36.159
I don't need any of that. Yeah, but I guess it's

00:51:36.159 --> 00:51:38.280
really complicated for terminal creators because

00:51:39.240 --> 00:51:42.699
Alacrity users will want tabs. And I know that

00:51:42.699 --> 00:51:46.000
Alacrity is like, nope, no tabs, no pain. So

00:51:46.000 --> 00:51:48.880
it must be really difficult to deal with that

00:51:48.880 --> 00:51:51.579
in the community, right? Because people always

00:51:51.579 --> 00:51:54.880
want the features that they want. Well, I thought,

00:51:54.980 --> 00:51:58.070
yeah, I don't follow development. of alacrity.

00:51:58.449 --> 00:52:01.349
But I thought, at least a couple of years ago,

00:52:01.489 --> 00:52:03.929
there was some talk about them adding tabs. I

00:52:03.929 --> 00:52:05.489
don't know if they had. They may have even added

00:52:05.489 --> 00:52:07.929
it. I don't know. I wouldn't use it anyway, so

00:52:07.929 --> 00:52:09.929
I don't know. But I know they'd been talking

00:52:09.929 --> 00:52:13.150
about adding tabs as far as splits. I don't know.

00:52:14.590 --> 00:52:18.050
But again, this is a problem that's already kind

00:52:18.050 --> 00:52:21.590
of solved. Like on Linux, every Linux distribution,

00:52:21.869 --> 00:52:24.369
for the most part, there's a few exceptions.

00:52:25.000 --> 00:52:27.159
probably already installed tmux for you it's

00:52:27.159 --> 00:52:30.039
there just like tmux in your terminal and hey

00:52:30.039 --> 00:52:32.420
now you get your tabs if you want them you're

00:52:32.420 --> 00:52:34.659
good to go what are your thoughts on thoughts

00:52:34.659 --> 00:52:37.579
on tmux do you use it a lot i don't use it a

00:52:37.579 --> 00:52:41.039
ton because again i don't necessarily need it

00:52:41.039 --> 00:52:42.940
being in a tiling window manager most of the

00:52:42.940 --> 00:52:45.679
time or being in emacs most of the time i've

00:52:45.679 --> 00:52:49.289
already got multiplexers you know the tmux becomes

00:52:49.289 --> 00:52:51.730
kind of redundant in that case if i'm in a tty

00:52:51.730 --> 00:52:54.210
i will sometimes use it i don't actually use

00:52:54.210 --> 00:52:57.010
it though for splits and tabs that's not why

00:52:57.010 --> 00:53:00.610
i use it in the tty and the tty i use it because

00:53:00.610 --> 00:53:03.710
i won't scroll back right because you don't get

00:53:03.710 --> 00:53:06.949
the text scroll back in a tty but in tmux you

00:53:06.949 --> 00:53:09.869
do so and you can select select and copy text

00:53:09.869 --> 00:53:13.780
yep right makes sense For your configuration,

00:53:14.260 --> 00:53:17.260
which is Emacs, your main editor, or NeoVim,

00:53:17.260 --> 00:53:19.579
you know, either or, do you use your own config

00:53:19.579 --> 00:53:22.099
or do you use a distribution as a starting point?

00:53:22.860 --> 00:53:26.960
No, that's my Emacs config. Yeah, from scratch.

00:53:28.920 --> 00:53:31.760
But I've used some of the various distributions

00:53:31.760 --> 00:53:35.980
of Emacs and NeoVim. You know, people ask me

00:53:35.980 --> 00:53:40.159
to try them out. I actually lived in Doom Emacs

00:53:40.159 --> 00:53:44.679
for... At least a year or two at one point. And

00:53:44.679 --> 00:53:47.099
that's a really good distribution of Emacs for

00:53:47.099 --> 00:53:48.900
Vim users because it already will have things

00:53:48.900 --> 00:53:50.800
like evil mode and everything already set up

00:53:50.800 --> 00:53:53.460
out of the box. And it's not very different from

00:53:53.460 --> 00:53:55.800
my config because my config, because I like Doom

00:53:55.800 --> 00:53:58.599
Emacs so much, I basically made my Emacs do a

00:53:58.599 --> 00:54:02.159
lot of the stuff Doom was doing anyway. Some

00:54:02.159 --> 00:54:05.599
things are different, obviously. But yeah, Doom

00:54:05.599 --> 00:54:07.699
Emacs is great for people that don't want to

00:54:07.699 --> 00:54:10.610
start writing an Emacs config from scratch. Because

00:54:10.610 --> 00:54:14.030
it can be daunting. You've got to write it in

00:54:14.030 --> 00:54:17.090
Emacs Lisp. Okay, well, I don't know any Emacs

00:54:17.090 --> 00:54:20.690
Lisp. You're brand new, right? So you can't do

00:54:20.690 --> 00:54:23.809
that, right? But it's not as hard as a lot of

00:54:23.809 --> 00:54:26.050
people think. If you've got any experience in

00:54:26.050 --> 00:54:29.449
programming at all, Emacs Lisp is pretty easy

00:54:29.449 --> 00:54:32.070
to wrap your head around. And there's plenty

00:54:32.070 --> 00:54:35.510
of tutorials and videos. Hell, I've made dozens.

00:54:36.349 --> 00:54:39.309
of Emacs configuration kind of videos to help

00:54:39.309 --> 00:54:41.849
people. Same thing with Vim as well. People trying

00:54:41.849 --> 00:54:45.050
to get into Vim and NeoVim. These things are

00:54:45.050 --> 00:54:48.489
not as complicated. The great thing about Vim

00:54:48.489 --> 00:54:51.190
and NeoVim though, I don't actually need to configure

00:54:51.190 --> 00:54:55.110
them to use them. Like when I do a fresh Linux

00:54:55.110 --> 00:54:58.250
installation, maybe setting up a web server or

00:54:58.250 --> 00:55:02.510
something, you know, and if Vim or NeoVim is

00:55:02.510 --> 00:55:05.130
there, I can just use it. I don't have to configure

00:55:05.130 --> 00:55:09.340
it to you. Emacs is very different. You got to

00:55:09.340 --> 00:55:11.480
configure. But the thing with Emacs, a lot of

00:55:11.480 --> 00:55:13.059
people don't realize this because I get this

00:55:13.059 --> 00:55:15.400
question all the time. I don't I can't switch

00:55:15.400 --> 00:55:17.579
from Vim to Emacs because what if I'm remote

00:55:17.579 --> 00:55:21.039
into some server that doesn't have Emacs? It

00:55:21.039 --> 00:55:24.219
doesn't matter. You don't you remote from your

00:55:24.219 --> 00:55:26.900
machine that has Emacs on it from inside Emacs.

00:55:27.219 --> 00:55:29.599
And you can still use your Emacs on this machine,

00:55:29.679 --> 00:55:35.460
but you're. So you can use it as an SSH client

00:55:35.460 --> 00:55:37.820
as well, Emacs? It's already built in, and you

00:55:37.820 --> 00:55:39.539
don't even have to configure that. It's already

00:55:39.539 --> 00:55:42.780
there for it. If I give it an address, instead

00:55:42.780 --> 00:55:46.679
of a file name, I give it an SSH address. Yeah,

00:55:46.739 --> 00:55:50.699
and I've got the password, obviously. But if

00:55:50.699 --> 00:55:54.059
you can, yeah, now when I look at DERIAD, the

00:55:54.059 --> 00:55:56.039
file manager inside Emacs, I'm actually looking

00:55:56.039 --> 00:55:58.079
at the file system of the remote machine now

00:55:58.079 --> 00:56:01.199
and editing files on it. And I assume you can

00:56:01.199 --> 00:56:04.059
also configure SSH key -based authentication

00:56:04.059 --> 00:56:09.059
in Emacs, right? I would assume. Yep. Okay. Interesting.

00:56:09.219 --> 00:56:12.440
Okay. What tool do you use in Emacs to push to

00:56:12.440 --> 00:56:17.960
GitLab? Is the one that you use? I don't actually

00:56:17.960 --> 00:56:22.980
use Emacs for my Git client. I can. I have used

00:56:22.980 --> 00:56:25.519
it. I've done videos about it. The reason I don't

00:56:25.519 --> 00:56:27.579
is because I've kind of got an exotic setup.

00:56:28.750 --> 00:56:32.769
For my dot files, I use a Git bear repository

00:56:32.769 --> 00:56:35.489
to manage my dot files. And the Emacs client,

00:56:35.789 --> 00:56:40.369
Magit, M -A -G -I -T, doesn't like bear repositories.

00:56:40.409 --> 00:56:42.550
It doesn't handle them well. So for my dot files,

00:56:42.869 --> 00:56:45.250
I would have to go to a terminal and just use

00:56:45.250 --> 00:56:49.889
my regular commits for that, which is mostly

00:56:49.889 --> 00:56:51.969
what I push is to my dot files. I've got other

00:56:51.969 --> 00:56:54.710
projects, too. But if I'm going to do that, I

00:56:54.710 --> 00:56:57.070
just use the terminal and Git for everything

00:56:57.070 --> 00:56:59.559
instead of Magit. If I didn't have that Git bear

00:56:59.559 --> 00:57:01.800
repository managing my dot files, I'd probably

00:57:01.800 --> 00:57:06.519
just do all of it in Git, in Magit inside Emacs.

00:57:06.599 --> 00:57:09.360
So that's a really fantastic Git client. You

00:57:09.360 --> 00:57:12.760
just learn the key bindings, you know, for adding

00:57:12.760 --> 00:57:15.860
and commit. You type your message inside Emacs,

00:57:16.000 --> 00:57:17.880
control C, control C, and it pushes it. You know,

00:57:17.880 --> 00:57:21.199
it's just magic. Yeah, so it's really, it's a

00:57:21.199 --> 00:57:24.039
nice Git client. I just, for what I have, I can't

00:57:24.039 --> 00:57:27.750
really use it. Okay, okay. We've been here for

00:57:27.750 --> 00:57:30.730
an hour. How much time do you have longer? We

00:57:30.730 --> 00:57:33.769
can go a little longer. Feel free. Shoot away.

00:57:34.050 --> 00:57:36.869
Okay. Yeah, because we're here to talk about,

00:57:37.010 --> 00:57:43.090
I want some advice, you know. I just want to

00:57:43.090 --> 00:57:45.210
hear your thoughts on macOS. Let's go with that

00:57:45.210 --> 00:57:51.670
first. So my thoughts on macOS is I haven't used

00:57:51.670 --> 00:57:55.780
it. It's like OS X. The modern versions of Mac

00:57:55.780 --> 00:57:58.219
that have been around for a long time now. I

00:57:58.219 --> 00:58:02.380
actually haven't used Mac OS X. Never had a Mac

00:58:02.380 --> 00:58:08.880
computer. I've used OS X in a virtual machine

00:58:08.880 --> 00:58:13.000
a time or two. But, yeah, I have no real thoughts.

00:58:13.179 --> 00:58:16.619
The last time I used a Mac computer was probably

00:58:16.619 --> 00:58:21.420
the late 90s. So I can't really speak on the

00:58:21.420 --> 00:58:26.010
operating system itself too much. Other than

00:58:26.010 --> 00:58:29.389
I know now, just like even then back in the 90s,

00:58:29.409 --> 00:58:34.570
it's a very kind of walled garden sort of ecosystem.

00:58:35.230 --> 00:58:37.389
You're not allowed to change much. It's kind

00:58:37.389 --> 00:58:42.489
of very rigid, not very flexible. And that was

00:58:42.489 --> 00:58:44.570
that case even in the 1990s compared to something

00:58:44.570 --> 00:58:47.230
like Microsoft Windows, which has its own set

00:58:47.230 --> 00:58:53.920
of problems, too. For somebody like me that loves

00:58:53.920 --> 00:58:56.780
customizing every little thing about the operating

00:58:56.780 --> 00:58:59.260
system, it would be totally the wrong operating

00:58:59.260 --> 00:59:02.460
system for me to use just because I would start

00:59:02.460 --> 00:59:04.840
with something that I've got to completely tear

00:59:04.840 --> 00:59:08.699
down. Yeah. And there's Linux distributions like

00:59:08.699 --> 00:59:14.219
that as well. Ubuntu, great Linux distribution.

00:59:14.840 --> 00:59:17.059
I'm not going to use the GNOME desktop environment

00:59:17.059 --> 00:59:19.889
or any of the... stuff that they ship with a

00:59:19.889 --> 00:59:21.510
lot of the applications and stuff would they

00:59:21.510 --> 00:59:24.269
ship out of the box why would i install that

00:59:24.269 --> 00:59:29.429
right so i would install it to uninstall everything

00:59:29.429 --> 00:59:32.090
i just installed well i could start with something

00:59:32.090 --> 00:59:36.070
minimal for example like a boom 2 server right

00:59:36.070 --> 00:59:39.030
and then install the window manager and everything

00:59:39.030 --> 00:59:41.909
emacs and everything i want to use or a debian

00:59:41.909 --> 00:59:44.170
server installation rather than the debian with

00:59:44.170 --> 00:59:48.079
the gnome desktop or in my case where i'm most

00:59:48.079 --> 00:59:50.059
comfortable these days, Arch Linux, just because

00:59:50.059 --> 00:59:53.940
Arch Linux is for those people that want to customize

00:59:53.940 --> 00:59:56.079
everything anyway. Instead of giving you something

00:59:56.079 --> 00:59:59.179
already pre -configured on Arch, you don't get

00:59:59.179 --> 01:00:02.199
anything except what you want. So there's nothing

01:00:02.199 --> 01:00:04.579
on this operating system that I didn't want.

01:00:04.800 --> 01:00:09.460
You touched Debian there and Ubuntu. I use Linux

01:00:09.460 --> 01:00:11.460
all the time, but only in servers, you know?

01:00:12.079 --> 01:00:15.559
SSH and... You know, no desktop environment at

01:00:15.559 --> 01:00:18.500
all. My distribution of choice is Debian always

01:00:18.500 --> 01:00:21.519
in servers. What are your thoughts there? Because

01:00:21.519 --> 01:00:24.179
Ubuntu is the popular one and everyone uses Ubuntu

01:00:24.179 --> 01:00:26.679
documentation, videos, everything is Ubuntu related.

01:00:26.960 --> 01:00:29.320
What are your thoughts there? Yeah, Debian is

01:00:29.320 --> 01:00:31.420
still a very popular server distro. It's just

01:00:31.420 --> 01:00:36.699
Ubuntu adds a lot of extra tools that make things

01:00:36.699 --> 01:00:39.559
so much easier than Debian as far as configuring

01:00:39.559 --> 01:00:44.400
certain things. There's a corporation behind

01:00:44.400 --> 01:00:47.860
Ubuntu, Canonical, and they know a lot of the

01:00:47.860 --> 01:00:49.440
things people are doing. Like if you're setting

01:00:49.440 --> 01:00:51.659
up a web server, they've already got their little

01:00:51.659 --> 01:00:54.500
tools and things, little programs you can run

01:00:54.500 --> 01:00:56.980
to help automate various things like setting

01:00:56.980 --> 01:00:59.099
up, I don't know, your AMP stack or whatever

01:00:59.099 --> 01:01:02.400
it is you're doing that, you know, use one command,

01:01:02.599 --> 01:01:05.460
you're done, you know, kind of thing where in

01:01:05.460 --> 01:01:07.320
Debian, you got to go through some work to install

01:01:07.320 --> 01:01:10.900
various things, then work with those config files,

01:01:11.079 --> 01:01:14.710
which, hey. You know how to do it. It's not like

01:01:14.710 --> 01:01:17.150
it's a lot of extra work, but it does save you

01:01:17.150 --> 01:01:19.130
some time sometimes if you want to just quickly

01:01:19.130 --> 01:01:21.909
spin up something. Setting up a Ubuntu server

01:01:21.909 --> 01:01:26.670
can be very quick. Also, not everybody loves

01:01:26.670 --> 01:01:29.690
Ubuntu and Snap Packaging, but the reason Snap

01:01:29.690 --> 01:01:32.650
Packages exist on Ubuntu is because of server.

01:01:34.289 --> 01:01:38.909
Snaps on a server make a lot of sense. For example,

01:01:39.070 --> 01:01:44.010
I use NextCloud. I use NextCloud file sync between

01:01:44.010 --> 01:01:46.989
all of my devices and stuff. Been using Nextcloud

01:01:46.989 --> 01:01:49.170
for a while. I run that on Ubuntu server and

01:01:49.170 --> 01:01:51.590
I installed it using the Snap package in Nextcloud.

01:01:52.369 --> 01:01:58.030
Why? It's because I could sudo snap install Nextcloud

01:01:58.030 --> 01:02:03.530
and be done. Because it installs the entire web

01:02:03.530 --> 01:02:06.010
server and all for you, all part of this container,

01:02:06.210 --> 01:02:10.989
right? And otherwise, it's a much more involved

01:02:10.989 --> 01:02:14.210
process. getting next cloud up and running yeah

01:02:14.210 --> 01:02:16.949
that's the thing with debian as well you know

01:02:16.949 --> 01:02:20.190
i use debian but what i do is i install docker

01:02:20.190 --> 01:02:22.429
and every application that i need to install

01:02:22.429 --> 01:02:25.329
is done through docker i install kubernetes as

01:02:25.329 --> 01:02:27.429
well it was playing around with kubernetes and

01:02:27.429 --> 01:02:30.789
i deploy applications so i don't rely on debian

01:02:30.789 --> 01:02:33.289
too much you know because docker is there kubernetes

01:02:33.289 --> 01:02:37.190
that is there i got the images already they run

01:02:37.190 --> 01:02:42.360
quite well but i have had to install stuff manually

01:02:42.360 --> 01:02:44.880
in the past as well in debian a lot of dependencies

01:02:44.880 --> 01:02:49.980
a lot of issues yeah yes uh it's not as big of

01:02:49.980 --> 01:02:52.159
an issue as it used to be but i remember years

01:02:52.159 --> 01:02:57.280
ago uh because i was mainly a debian slash ubuntu

01:02:57.280 --> 01:03:02.639
user most of the time i've been running linux

01:03:02.639 --> 01:03:05.739
uh i've been primarily an arch user since i started

01:03:05.739 --> 01:03:08.340
the youtube channel you know eight years ago

01:03:08.340 --> 01:03:12.559
uh because For the kind of work I do on camera,

01:03:12.719 --> 01:03:15.320
I wanted the latest packages for various things.

01:03:15.400 --> 01:03:17.179
And there were programs that I needed that wouldn't

01:03:17.179 --> 01:03:19.079
be in the Debian repos because Debian's too damn

01:03:19.079 --> 01:03:22.920
old, right? So that's why I started using Arch.

01:03:23.039 --> 01:03:26.840
And these days, I mean, if I didn't do YouTube

01:03:26.840 --> 01:03:29.039
and sometimes need the latest and greatest things

01:03:29.039 --> 01:03:32.059
sometimes for various things I'm doing on camera,

01:03:32.239 --> 01:03:36.699
I'd probably just install Debian Stable or Ubuntu

01:03:36.699 --> 01:03:40.170
LTS, very similar. And then my favorite window

01:03:40.170 --> 01:03:42.369
manager on top of it, whatever, you know, emacs

01:03:42.369 --> 01:03:45.550
and whatever. And I'd be perfectly happy. I don't

01:03:45.550 --> 01:03:49.070
need a rolling release necessarily if I didn't

01:03:49.070 --> 01:03:51.690
do this because I do this and I kind of need

01:03:51.690 --> 01:03:54.610
it. Yeah. When you retire, then. Yeah, when I

01:03:54.610 --> 01:03:56.550
retire from YouTube, I'm putting Debian back

01:03:56.550 --> 01:04:04.389
on my computer. Okay. And, well, what I use is

01:04:04.389 --> 01:04:07.489
macOS. You know, that's what I'm. What I'm recording

01:04:07.489 --> 01:04:09.750
this on right now, you know, that's how I have

01:04:09.750 --> 01:04:12.449
my phone connected. I don't have a camera. My

01:04:12.449 --> 01:04:14.829
phone is actually my camera. It's my iPhone connects

01:04:14.829 --> 01:04:18.869
to the computer. I open OBS, works. I update

01:04:18.869 --> 01:04:22.969
macOS, even to newer versions. I update the apps

01:04:22.969 --> 01:04:25.010
because I install all of them through Homebrew,

01:04:25.130 --> 01:04:28.369
right? That's the package manager you get in

01:04:28.369 --> 01:04:31.050
macOS. So I install them that way. I upgrade

01:04:31.050 --> 01:04:37.239
the packages or apps. And it just works. It has

01:04:37.239 --> 01:04:41.119
not broken on me, at least in the past, I don't

01:04:41.119 --> 01:04:45.480
know, three years or so. And I've been thinking

01:04:45.480 --> 01:04:48.019
about Linux. I want to try Linux, you know, because

01:04:48.019 --> 01:04:50.679
like you said, macOS is great. It has gotten

01:04:50.679 --> 01:04:53.500
a lot better. Now you get, you can install window

01:04:53.500 --> 01:04:55.820
managers. There's a few options and they work

01:04:55.820 --> 01:05:00.460
quite well. But it's very limited, the things

01:05:00.460 --> 01:05:02.539
that you can still do. You can still customize

01:05:02.539 --> 01:05:05.780
it a lot. If you look at my screen. It doesn't

01:05:05.780 --> 01:05:09.400
look like macOS too much. It looks, I don't know,

01:05:09.440 --> 01:05:13.039
like... Let me switch to it real quick. Somewhat

01:05:13.039 --> 01:05:15.400
of a Linux distro or something. I don't know.

01:05:15.500 --> 01:05:19.300
Something strange. There's something going on

01:05:19.300 --> 01:05:23.900
there, people think. But I want that experience

01:05:23.900 --> 01:05:27.159
in Linux. And I've been thinking about trying

01:05:27.159 --> 01:05:30.920
it. You get a lot of advice. People tell you...

01:05:31.820 --> 01:05:34.579
Arch, a lot of people mentioned Fedora, right?

01:05:34.679 --> 01:05:38.579
And I've seen that Fedora is shipped with this

01:05:38.579 --> 01:05:42.380
framework laptops. So I guess it must be stable.

01:05:42.639 --> 01:05:45.679
What are your recommendations? What are your

01:05:45.679 --> 01:05:48.960
thoughts there? Yeah, I mean, if you're looking

01:05:48.960 --> 01:05:53.719
for something that's really stable, Debian stable

01:05:53.719 --> 01:05:56.739
and Ubuntu LTS kind of where you want to be.

01:05:57.260 --> 01:06:01.139
Fedora, it's much more of a... experimental playing

01:06:01.139 --> 01:06:05.179
ground sometimes where they'll introduce new

01:06:05.179 --> 01:06:09.420
features and things that aren't necessarily all

01:06:09.420 --> 01:06:12.400
that well tested. So you will run into that problem

01:06:12.400 --> 01:06:17.800
on Fedora. It's not a rolling release, but sometimes

01:06:17.800 --> 01:06:22.219
they will push out some new features. And basically

01:06:22.219 --> 01:06:26.980
you become the beta tester. It's not something

01:06:26.980 --> 01:06:30.000
that I would say just breaks all the time. But

01:06:30.000 --> 01:06:31.380
you can experience some breakage. I mean, you

01:06:31.380 --> 01:06:33.940
can experience breakage on everything, I guess.

01:06:34.179 --> 01:06:38.440
But yeah, I've run Fedora before. It's a fine

01:06:38.440 --> 01:06:42.159
distribution as well. So which one would you

01:06:42.159 --> 01:06:45.059
choose? Because Debian, well, I could get Debian.

01:06:45.179 --> 01:06:48.440
I could install OBS there, I assume. I don't

01:06:48.440 --> 01:06:50.519
know if it's going to be a really old version

01:06:50.519 --> 01:06:54.599
or... Well, it will be at least two years old

01:06:54.599 --> 01:06:57.500
now because is the new version of Debian dropped?

01:06:58.650 --> 01:07:01.530
You're about to get a new version if you install,

01:07:01.690 --> 01:07:04.570
what is it, Debian 13? What version are they

01:07:04.570 --> 01:07:07.550
on now? The new version of Debian is getting

01:07:07.550 --> 01:07:11.650
close for a release date, though. But yeah, if

01:07:11.650 --> 01:07:14.849
it's not available now, then you've got to install

01:07:14.849 --> 01:07:18.349
the last Debian that came out more than a year

01:07:18.349 --> 01:07:20.090
ago. Yeah, that's not going to be the newest

01:07:20.090 --> 01:07:25.489
version of OBS. But here's the thing. Things

01:07:25.489 --> 01:07:30.750
like snaps, flatbacks, and app images have solved

01:07:30.750 --> 01:07:33.329
that problem. If you need something on Debian

01:07:33.329 --> 01:07:36.550
that you absolutely need to always have on the

01:07:36.550 --> 01:07:40.090
latest version, just install Flatpak and install

01:07:40.090 --> 01:07:42.469
OBS through the Flatpak because I believe the

01:07:42.469 --> 01:07:46.250
OBS team actually builds the Flatpak. It's their

01:07:46.250 --> 01:07:49.809
Flatpak. And that's typically what I try to do

01:07:49.809 --> 01:07:52.710
if they have an official. package that they build

01:07:52.710 --> 01:07:54.750
themselves. I really don't care what format snaps,

01:07:54.969 --> 01:07:57.610
flat packs, app images, whatever. And if I know

01:07:57.610 --> 01:07:59.530
the team behind it built that package, I'll go

01:07:59.530 --> 01:08:02.409
grab that package. So I could, all of those have

01:08:02.409 --> 01:08:04.650
the ability to auto update. So you don't have

01:08:04.650 --> 01:08:08.070
to worry about updating the, the program. Oh,

01:08:08.070 --> 01:08:10.690
it makes sense. Okay. So I could have Debian

01:08:10.690 --> 01:08:14.929
stable and, and still the latest OBS. Okay. And

01:08:14.929 --> 01:08:18.439
the latest of the packages. What's the drawback

01:08:18.439 --> 01:08:21.640
of these flat packs? Are these like containerized

01:08:21.640 --> 01:08:24.279
applications? That's why you can get the latest

01:08:24.279 --> 01:08:26.239
is because they'll have all the libraries and

01:08:26.239 --> 01:08:28.439
everything, all its dependencies contained within

01:08:28.439 --> 01:08:31.020
itself. That way you don't run into the dependency

01:08:31.020 --> 01:08:34.720
hill issue where you have to go compile things

01:08:34.720 --> 01:08:37.340
from source. And then I also need to go compile

01:08:37.340 --> 01:08:39.859
this other thing and the next thing. And then

01:08:39.859 --> 01:08:43.010
all of a sudden you've got. This weird dependency

01:08:43.010 --> 01:08:45.109
loop where this thing depends on this program

01:08:45.109 --> 01:08:47.189
is no longer here, not available, not the right

01:08:47.189 --> 01:08:49.810
version. And then you end up with a situation

01:08:49.810 --> 01:08:53.989
where your system is essentially broken because

01:08:53.989 --> 01:08:57.210
you can't update anything because all the dependencies

01:08:57.210 --> 01:09:01.569
are screwed up. Yeah, makes sense. So are there

01:09:01.569 --> 01:09:03.930
any drawbacks? Is there a drawback? I have not.

01:09:04.310 --> 01:09:08.189
On some programs, I guess there could be if.

01:09:08.909 --> 01:09:11.409
They need to break out of the container to interact

01:09:11.409 --> 01:09:14.890
with certain devices or other programs on the

01:09:14.890 --> 01:09:16.909
system. Sometimes it can be an issue for some

01:09:16.909 --> 01:09:19.770
things. I can tell you OBS is not a problem as

01:09:19.770 --> 01:09:22.609
a flatback. Wonderful. Okay. Because probably

01:09:22.609 --> 01:09:25.109
most people that install OBS probably install

01:09:25.109 --> 01:09:26.869
the flatback because it is an official package

01:09:26.869 --> 01:09:29.350
that they maintain and that they push. They try

01:09:29.350 --> 01:09:31.430
to tell everybody, go install the flatback because

01:09:31.430 --> 01:09:33.800
we're building that. So if there's a problem

01:09:33.800 --> 01:09:36.119
with that package, we built it, so we're responsible

01:09:36.119 --> 01:09:38.159
for it. Don't come and complain that you install

01:09:38.159 --> 01:09:42.699
whatever's in the Debian repo. Okay. Yeah, and

01:09:42.699 --> 01:09:44.939
I'm not into distro hopping. If I'm going to

01:09:44.939 --> 01:09:47.439
install something, it's just going to be what

01:09:47.439 --> 01:09:49.199
I will use. I'm not going to go and try other

01:09:49.199 --> 01:09:52.079
distributions. I don't care, to be honest. At

01:09:52.079 --> 01:09:55.020
the end of the day, they're all the same under

01:09:55.020 --> 01:09:57.960
the hood, depending on your workflow. For me,

01:09:58.020 --> 01:10:02.239
if I'm spending most of my time, in a text editor

01:10:02.239 --> 01:10:05.960
like emacs yep and the terminal yep and interact

01:10:05.960 --> 01:10:08.460
you know for most things i just open terminals

01:10:08.460 --> 01:10:10.979
and run various command line utilities i know

01:10:10.979 --> 01:10:14.539
how to use anyway and no matter what linux distro

01:10:14.539 --> 01:10:17.640
you install you're gonna have the shell and the

01:10:17.640 --> 01:10:22.100
core utils and probably vim will be there you

01:10:22.100 --> 01:10:24.159
go ahead and install neo vim or emacs whatever

01:10:24.159 --> 01:10:28.500
else you want as what i like it becomes It becomes

01:10:28.500 --> 01:10:30.520
pointless to distro hop if you're that kind of

01:10:30.520 --> 01:10:33.659
user because you're getting the exact same experience

01:10:33.659 --> 01:10:35.699
no matter what distro you're running. The only

01:10:35.699 --> 01:10:39.479
difference is the repos of software. Does it

01:10:39.479 --> 01:10:41.220
have all the programs you want and what version

01:10:41.220 --> 01:10:44.600
are they on? On Arch, I'll have the thing that

01:10:44.600 --> 01:10:47.479
came out this morning, which may or may not be

01:10:47.479 --> 01:10:49.680
what you want. On Debian, you'll have the thing

01:10:49.680 --> 01:10:52.000
that came out two years ago, which may or may

01:10:52.000 --> 01:10:54.779
not be what you want. And then there's stuff

01:10:54.779 --> 01:10:57.560
in between those two extremes. You could install

01:10:57.560 --> 01:11:01.859
NeoVim as a flat pack as well in... I would imagine.

01:11:02.159 --> 01:11:06.579
I would imagine you could. I'm not sure if it

01:11:06.579 --> 01:11:08.920
would be something that's all that necessary.

01:11:10.260 --> 01:11:13.420
But I'm sure you could. Okay. I mean, does NeoVim

01:11:13.420 --> 01:11:15.579
have a lot of major changes you'd want to keep

01:11:15.579 --> 01:11:19.859
up with? There's the latest release, 0 .11, I

01:11:19.859 --> 01:11:21.699
think it is. It was, I don't know, a few months

01:11:21.699 --> 01:11:26.079
ago. Yeah. I'm sure they probably have a... Flat

01:11:26.079 --> 01:11:29.279
pack. I would bet they do. Because these days,

01:11:29.300 --> 01:11:33.159
some distributions are trying to basically have

01:11:33.159 --> 01:11:35.140
everything containerized. So even if they didn't

01:11:35.140 --> 01:11:37.300
build a flat pack for it, somebody has built

01:11:37.300 --> 01:11:40.260
a flat pack of neofilms. I'm sure you could find

01:11:40.260 --> 01:11:45.739
it. Okay. Okay. And there's like a rivalry between

01:11:45.739 --> 01:11:50.439
these two communities, Linux and macOS. Well,

01:11:50.579 --> 01:11:53.920
people are switching between. mac os linux a

01:11:53.920 --> 01:11:55.880
lot of the time because they're unix right yeah

01:11:55.880 --> 01:11:58.319
i wouldn't say there's a real rivalry there i

01:11:58.319 --> 01:12:02.159
think as far as for the linux community as far

01:12:02.159 --> 01:12:08.619
as who they dislike microsoft because mac os

01:12:08.619 --> 01:12:12.159
has never really tried to damage linux in any

01:12:12.159 --> 01:12:17.000
way or attack it in any way microsoft has was

01:12:17.000 --> 01:12:19.119
against Linux from the beginning and they tried

01:12:19.119 --> 01:12:22.619
to kill it. And there's a lot, you know, how

01:12:22.619 --> 01:12:25.720
Microsoft and some of their business practices,

01:12:25.800 --> 01:12:27.659
how they treated various open source projects

01:12:27.659 --> 01:12:31.100
over the years before they all of a sudden, we

01:12:31.100 --> 01:12:33.760
love open source. Well, you didn't last month

01:12:33.760 --> 01:12:36.640
when you ran this other open source company into

01:12:36.640 --> 01:12:38.859
the ground, you ran them out of business and

01:12:38.859 --> 01:12:41.640
you called Linux cancer. You know, that was,

01:12:41.640 --> 01:12:45.380
was that Steve Ballmer? Linux is cancer. Yeah.

01:12:45.770 --> 01:12:49.850
He said open source is cancer. He didn't like

01:12:49.850 --> 01:12:51.989
the licensing, I think. Or maybe Linux, because

01:12:51.989 --> 01:12:54.489
it was open source, is cancer. One of those.

01:12:58.010 --> 01:13:01.930
WSL, right? They're all in for WSL. Now everything

01:13:01.930 --> 01:13:05.810
they do is licensed under the MIT license. They

01:13:05.810 --> 01:13:08.229
got on their little homepage, iHeart, Linux,

01:13:08.369 --> 01:13:10.229
Microsoft, Hearts, Linux, or whatever. I'm like,

01:13:10.430 --> 01:13:13.779
yeah. But you know what? I give them credit.

01:13:13.880 --> 01:13:17.239
I give Satya Nadella and the new guys over at

01:13:17.239 --> 01:13:21.840
Microsoft. I actually think that's a good thing.

01:13:21.979 --> 01:13:26.180
And I don't mind when companies that I thought

01:13:26.180 --> 01:13:28.640
were doing the wrong thing in the past start

01:13:28.640 --> 01:13:30.460
doing the right thing, regardless of the reasons.

01:13:30.560 --> 01:13:32.479
The reasons, obviously, is it makes them money

01:13:32.479 --> 01:13:34.960
now, open source, right? They see money in it.

01:13:35.039 --> 01:13:36.600
That's why they're doing it. I don't care about

01:13:36.600 --> 01:13:40.060
their motivation behind it. I'm just happy that

01:13:40.060 --> 01:13:43.659
they're on board. Obviously, they're one of the

01:13:43.659 --> 01:13:45.579
largest contributors to the Linux Foundation,

01:13:46.079 --> 01:13:48.439
the Linux kernel development. They have a ton

01:13:48.439 --> 01:13:52.619
of people on Microsoft's paid staff that work

01:13:52.619 --> 01:13:55.899
on the Linux kernel. Hey, that's all great. I

01:13:55.899 --> 01:13:58.600
can't complain about any of that. What do you

01:13:58.600 --> 01:14:02.680
think life would be? Because before they went

01:14:02.680 --> 01:14:05.920
with their DOS thing, they were Zenix, right?

01:14:06.020 --> 01:14:11.119
And it was Unix -based. What do you think if

01:14:11.119 --> 01:14:14.140
they would still be Unix -based, like Microsoft?

01:14:14.739 --> 01:14:16.819
It would probably still end up in the same place

01:14:16.819 --> 01:14:22.880
it is now. I mean, Unix was a proprietary operating

01:14:22.880 --> 01:14:27.140
system. This was before open source was even

01:14:27.140 --> 01:14:30.220
a thing. You know, the old Unix -y days back

01:14:30.220 --> 01:14:35.640
in the 1970s and 80s. Obviously, it wasn't really...

01:14:36.300 --> 01:14:38.979
Until Richard Stallman in the late 70s kind of

01:14:38.979 --> 01:14:41.399
started the whole free software thing. But really,

01:14:41.439 --> 01:14:44.819
it wasn't until he founded the GNU project in

01:14:44.819 --> 01:14:50.340
the mid 80s. That kind of. Codified this whole

01:14:50.340 --> 01:14:53.119
free and open source software that we know today

01:14:53.119 --> 01:14:57.960
with the GPO license and all of that, the GNU

01:14:57.960 --> 01:15:01.899
manifesto. So, yeah, just because they would

01:15:01.899 --> 01:15:05.439
have adopted like. a proprietary Unix operating

01:15:05.439 --> 01:15:07.500
system instead of creating their own proprietary

01:15:07.500 --> 01:15:10.899
operating system, Microsoft Windows would probably

01:15:10.899 --> 01:15:13.020
still look and function exactly the way it does

01:15:13.020 --> 01:15:15.199
today. Now, they still would have done all the

01:15:15.199 --> 01:15:16.819
things they wanted to do. They just would have

01:15:16.819 --> 01:15:19.319
started with a different base. Yeah. It would

01:15:19.319 --> 01:15:23.020
be in no way compatible with any modern Unix

01:15:23.020 --> 01:15:26.199
-like operating system. Yeah. Very similar to

01:15:26.199 --> 01:15:30.500
Mac OS X. It's based on FreeBSD. It is in no

01:15:30.500 --> 01:15:33.109
way compatible. with anything that FreeBSD is

01:15:33.109 --> 01:15:36.170
doing these days. All right, they've gone completely,

01:15:36.510 --> 01:15:38.529
you know, at some point you got to diverge a

01:15:38.529 --> 01:15:41.909
little bit. And in this case, in your hypothetical

01:15:41.909 --> 01:15:45.569
example of 40 years of diverging, yeah, they

01:15:45.569 --> 01:15:47.609
wouldn't be, they wouldn't remotely look anything

01:15:47.609 --> 01:15:51.149
like Unix. At least you could log into the terminal

01:15:51.149 --> 01:15:54.250
in Windows and run DLS command instead of there.

01:15:54.489 --> 01:15:59.970
Well, now, yeah. Actually, we do have the DIR

01:15:59.970 --> 01:16:04.050
command. In Linux. In Linux? It's actually part

01:16:04.050 --> 01:16:06.949
of the new core utils. Oh. Well, I don't know

01:16:06.949 --> 01:16:10.890
why you would run it because it's basically LS

01:16:10.890 --> 01:16:16.029
with a certain flag. It's a very simple LS. But

01:16:16.029 --> 01:16:18.689
it's there for compatibility reasons, I guess,

01:16:18.729 --> 01:16:22.630
because Windows users, I guess they don't know

01:16:22.630 --> 01:16:27.609
about the LS command. What are your thoughts

01:16:27.609 --> 01:16:31.350
on these other companies like System76 and Framework?

01:16:31.430 --> 01:16:34.130
Because if I get hardware, I don't want to invest

01:16:34.130 --> 01:16:37.609
the time into seeing what's compatible. Maybe

01:16:37.609 --> 01:16:40.170
everything is compatible nowadays. It was not

01:16:40.170 --> 01:16:42.789
back in the day when I played with Linux. And

01:16:42.789 --> 01:16:44.689
I'm talking about, I don't know, 15 years ago.

01:16:45.390 --> 01:16:48.670
It's a lot different now. Yeah. A lot different.

01:16:49.300 --> 01:16:52.579
It's the Linux kernel and all the drivers and

01:16:52.579 --> 01:16:55.020
everything that's baked into it. Of course, people

01:16:55.020 --> 01:16:57.520
complain about the Linux kernel just being millions

01:16:57.520 --> 01:16:59.420
and millions of lines of code. Well, part of

01:16:59.420 --> 01:17:04.300
that is it's very hard to find a machine that

01:17:04.300 --> 01:17:08.199
Linux doesn't run on. It's an easily operating

01:17:08.199 --> 01:17:10.399
system that's going to support the most hardware

01:17:10.399 --> 01:17:13.260
just by the nature of the size of the thing and

01:17:13.260 --> 01:17:15.159
so many people are working on it. The fact that

01:17:15.159 --> 01:17:17.550
it's built for... Servers and desktops, mobile

01:17:17.550 --> 01:17:23.430
devices, IoT, it's built for everything. So yeah,

01:17:23.590 --> 01:17:28.130
15 years ago, I guess it was possible to go find

01:17:28.130 --> 01:17:31.109
machines that didn't quite work right on Linux.

01:17:31.989 --> 01:17:34.949
Or a few things didn't work, like your Wi -Fi

01:17:34.949 --> 01:17:37.869
or some small perks. Wi -Fi was the big one.

01:17:37.930 --> 01:17:41.430
Wi -Fi was the big one. Because the Wi -Fi drivers,

01:17:41.710 --> 01:17:45.890
the chips, the... What was the Wi -Fi chips?

01:17:46.029 --> 01:17:49.529
RealTech. Yep. Those drivers were proprietary

01:17:49.529 --> 01:17:52.310
because they were proprietary. They weren't in

01:17:52.310 --> 01:17:54.149
the Linux kernel, so it's not something that

01:17:54.149 --> 01:17:56.590
would ship out of the box that would just work.

01:17:56.649 --> 01:17:59.609
You'd have to go get that proprietary driver

01:17:59.609 --> 01:18:01.550
yourself and install it however you could install

01:18:01.550 --> 01:18:04.050
it. And how do you download it? I mean, you don't

01:18:04.050 --> 01:18:07.149
have Wi -Fi, right? So it was a pain in the ass.

01:18:07.630 --> 01:18:12.819
But now there's not a lot of that. headache anymore

01:18:12.819 --> 01:18:15.539
as far as like wi -fi chips and graphics drivers

01:18:15.539 --> 01:18:17.380
and things you know like graphics drivers were

01:18:17.380 --> 01:18:19.399
another problem especially like 20 years ago

01:18:19.399 --> 01:18:25.180
um that's that's not a problem anymore but as

01:18:25.180 --> 01:18:27.079
far as the companies you asked about system 76

01:18:27.079 --> 01:18:31.479
uh i've never dealt with them i don't know i've

01:18:31.479 --> 01:18:33.439
never had their hardware never tested anything

01:18:33.439 --> 01:18:37.250
or so I can't comment on them. I think it's great

01:18:37.250 --> 01:18:39.649
that companies are selling devices that already

01:18:39.649 --> 01:18:41.289
have Linux pre -installed, and there's a lot

01:18:41.289 --> 01:18:44.210
of companies that do that now. But I've never

01:18:44.210 --> 01:18:49.170
bought from a company that specifically catered

01:18:49.170 --> 01:18:52.189
to Linux. I won't say that. I have bought from

01:18:52.189 --> 01:18:55.550
a few smaller boutique custom computer shops,

01:18:55.729 --> 01:18:59.689
and they asked me what operating system to put

01:18:59.689 --> 01:19:02.189
on it. I already know I'm going to wipe out Windows.

01:19:02.960 --> 01:19:05.000
if they ship Windows. So I just, hey, don't put

01:19:05.000 --> 01:19:07.239
an operating system on it because I'm going to

01:19:07.239 --> 01:19:08.680
install Linux. Some of them might actually say,

01:19:08.779 --> 01:19:10.819
oh, well, we can install Ubuntu on it. Okay.

01:19:11.880 --> 01:19:14.060
You didn't do that. I'm probably still going

01:19:14.060 --> 01:19:15.779
to wipe out Ubuntu because I'm going to put something,

01:19:15.859 --> 01:19:19.460
you know, but it's less of a headache to hop

01:19:19.460 --> 01:19:22.880
from another Linux than, you know, from Windows

01:19:22.880 --> 01:19:24.880
because Windows, you know, you're going to have

01:19:24.880 --> 01:19:28.199
to go in the iOS and, you know, hey, please let

01:19:28.199 --> 01:19:32.489
me uninstall you. They try to make it impossible

01:19:32.489 --> 01:19:37.210
for you to wipe it out. Okay. Last two questions

01:19:37.210 --> 01:19:39.670
that I have for you. Last two topics that I want

01:19:39.670 --> 01:19:43.229
to cover. One of them, well, three, real quick.

01:19:43.369 --> 01:19:45.829
Let's try to keep it fast. What are your thoughts

01:19:45.829 --> 01:19:52.170
on Windows? Oh, so Windows is another operating

01:19:52.170 --> 01:19:55.210
system that I haven't really spent much time

01:19:55.210 --> 01:19:59.069
in. In the last, say, 16, 18 years. The last

01:19:59.069 --> 01:20:00.989
time I had a machine that ran Windows was, I

01:20:00.989 --> 01:20:05.430
think, in 2008. And I switched to Linux on all

01:20:05.430 --> 01:20:09.449
my machines as far as desktop computers. And

01:20:09.449 --> 01:20:11.989
the little bit I played on servers, you know,

01:20:11.989 --> 01:20:14.430
because I was kind of a nerd even back in the

01:20:14.430 --> 01:20:16.189
90s playing with web servers, especially in the

01:20:16.189 --> 01:20:18.579
early days of the Internet. The birth of the

01:20:18.579 --> 01:20:20.579
World Wide Web, I wanted to be one of those people

01:20:20.579 --> 01:20:22.579
that, man, building websites and things. And

01:20:22.579 --> 01:20:25.420
even back then, a lot of web servers were Linux.

01:20:25.520 --> 01:20:27.800
So I knew what Linux was going back, you know,

01:20:27.800 --> 01:20:31.319
like the mid -1990s. I switched to Linux full

01:20:31.319 --> 01:20:33.500
-time on the desktop in 2008 because I had a

01:20:33.500 --> 01:20:35.899
Windows computer that was running Windows XP.

01:20:36.840 --> 01:20:39.939
It was taken over by ransomware. The hacker took

01:20:39.939 --> 01:20:41.739
over my computer. He wouldn't give it back unless

01:20:41.739 --> 01:20:45.619
I paid him some money. He said, you know what?

01:20:46.170 --> 01:20:50.390
Got this Ubuntu CD, popped it in. So you got

01:20:50.390 --> 01:20:55.770
to thank that guy then. Yeah. I mean, I already

01:20:55.770 --> 01:20:57.989
knew what Linux was. That's why I had the Ubuntu

01:20:57.989 --> 01:21:01.430
CD anyway. Play with Linux anyway. But he gave

01:21:01.430 --> 01:21:04.970
me a reason to, yeah, hey, I'm not paying you

01:21:04.970 --> 01:21:10.050
money for your antivirus to remove your, like,

01:21:10.170 --> 01:21:13.369
there's no way in hell I'm doing that. So, yeah,

01:21:13.470 --> 01:21:16.800
I just. resolved myself to the fact, hey, everything

01:21:16.800 --> 01:21:19.079
on this computer I'm losing. I'm formatting the

01:21:19.079 --> 01:21:22.960
drive right now, put a boom to it, and went on.

01:21:23.619 --> 01:21:28.020
Went on like it never happened. And that was

01:21:28.020 --> 01:21:31.260
in 2008. And even back then, it seems like so

01:21:31.260 --> 01:21:34.060
long ago, it was a really smooth experience for

01:21:34.060 --> 01:21:37.020
me. I really didn't have any headaches or any

01:21:37.020 --> 01:21:39.979
issues. A lot of the software I was using, though,

01:21:40.119 --> 01:21:43.420
I was already using on... Microsoft Windows,

01:21:43.619 --> 01:21:47.500
because even on Windows, I wanted to use open

01:21:47.500 --> 01:21:51.079
source software. I was already using Firefox

01:21:51.079 --> 01:21:53.960
as a browser. I was already using LibreOffice,

01:21:53.979 --> 01:21:56.199
which wasn't LibreOffice then. It was OpenOffice.

01:21:56.199 --> 01:22:00.159
It was before the fork. But open source software,

01:22:00.199 --> 01:22:03.260
I was using GIMP instead of Photoshop and things

01:22:03.260 --> 01:22:05.880
like that. So a lot of that stuff I was using

01:22:05.880 --> 01:22:10.579
on Windows. When I got to Linux, oh, they already

01:22:10.579 --> 01:22:12.869
installed all this. For me, you know, like this,

01:22:12.949 --> 01:22:15.029
their default programs for the most part. So

01:22:15.029 --> 01:22:17.409
it made it a little easier for me or a lot of

01:22:17.409 --> 01:22:21.210
people will have proprietary software that they're

01:22:21.210 --> 01:22:24.170
used to. A lot of times it's Windows only software,

01:22:24.289 --> 01:22:26.949
where if you primarily use open source software,

01:22:27.189 --> 01:22:29.930
there's always a Linux version. Like usually

01:22:29.930 --> 01:22:33.989
they develop it for Linux and maybe they'll port

01:22:33.989 --> 01:22:36.189
it to Windows because Windows has all the market

01:22:36.189 --> 01:22:39.149
share they got eventually. But, you know, we'll

01:22:39.149 --> 01:22:42.710
always have it on Linux usually, though. There's

01:22:42.710 --> 01:22:47.170
just a handful of things I think I've ever come

01:22:47.170 --> 01:22:50.010
across that were open source software that only

01:22:50.010 --> 01:22:51.670
had a Windows version and didn't have a Linux

01:22:51.670 --> 01:22:54.289
version, oddly enough. Proprietary software,

01:22:54.409 --> 01:22:56.609
you run into that problem all the time, but free

01:22:56.609 --> 01:22:58.149
and open source software. Matter of fact, off

01:22:58.149 --> 01:23:00.189
the top of my head, I can only think of one really

01:23:00.189 --> 01:23:02.109
popular program that's free and open source software

01:23:02.109 --> 01:23:04.010
that doesn't have a Linux version. It's Windows

01:23:04.010 --> 01:23:09.109
only, and that's Notepad++. Oh, it doesn't have?

01:23:09.399 --> 01:23:13.920
I guess because it's so tied into the Windows

01:23:13.920 --> 01:23:16.239
operating system in some way. It's designed to

01:23:16.239 --> 01:23:17.939
be a replacement for their text editor and their

01:23:17.939 --> 01:23:22.420
notepad. But it's GPL software and it's Windows

01:23:22.420 --> 01:23:26.659
only. Which is really weird. But that's kind

01:23:26.659 --> 01:23:32.079
of the oddball. We don't need notepad++ on Linux.

01:23:32.140 --> 01:23:38.000
We got a million text editors. True. And do you

01:23:38.000 --> 01:23:40.600
have a special keyboard or what do you use for

01:23:40.600 --> 01:23:43.500
your keyboard? Well, on this computer, I use

01:23:43.500 --> 01:23:47.619
the ZSA Moonlander. Okay. I've got videos about

01:23:47.619 --> 01:23:50.420
a lot of the ZSA keyboards because I bought a

01:23:50.420 --> 01:23:54.960
few of them. I use the Moonlander on this computer

01:23:54.960 --> 01:23:56.640
here, the workstation here at my office where

01:23:56.640 --> 01:24:00.239
I record. At home, I've got the ZSA ErgoDox,

01:24:00.319 --> 01:24:05.029
which I use. Okay. um behind me you probably

01:24:05.029 --> 01:24:08.250
can't see it in this frame i have a zsa plank

01:24:08.250 --> 01:24:10.569
which they've since discontinued it's a little

01:24:10.569 --> 01:24:14.890
uh 40 keyboard i use it sometimes to travel with

01:24:14.890 --> 01:24:17.590
it's actually really great to just plug into

01:24:17.590 --> 01:24:21.289
your phone if you want a real keyboard oh i see

01:24:21.289 --> 01:24:26.550
it here let's see this one okay yeah they don't

01:24:26.550 --> 01:24:30.149
make that one anymore um the latest one they're

01:24:30.149 --> 01:24:34.029
on They do a lot of split keyboards. I really

01:24:34.029 --> 01:24:35.810
like their split keyboards. The Moonlander and

01:24:35.810 --> 01:24:39.789
the ErgoDox, great. They have a new split keyboard

01:24:39.789 --> 01:24:42.270
that they're pushing now that looks really awesome.

01:24:42.569 --> 01:24:46.210
I haven't had the opportunity to buy one yet

01:24:46.210 --> 01:24:48.789
because I've already spent more than $1 ,000

01:24:48.789 --> 01:24:52.890
on these things. The Voyager. Yeah, the Voyager

01:24:52.890 --> 01:24:58.270
is the new. Yeah, yeah, yeah. But great keyboards.

01:24:59.279 --> 01:25:01.460
Cool company. The people there have always been

01:25:01.460 --> 01:25:03.359
nice to me. I made some videos about their products

01:25:03.359 --> 01:25:06.239
in the past, so they know who I am. They like

01:25:06.239 --> 01:25:09.000
that I like their keyboards. I send them some

01:25:09.000 --> 01:25:11.840
business. As a matter of fact, I guess they like

01:25:11.840 --> 01:25:15.539
the fact that I made videos about their products

01:25:15.539 --> 01:25:17.460
so much. One year, I think it was two years ago,

01:25:17.539 --> 01:25:21.640
they sent me a Christmas card. A Christmas card,

01:25:21.699 --> 01:25:23.659
a thank you, and a little gift with it or something.

01:25:24.319 --> 01:25:27.939
It's a small little gift. nice i was like oh

01:25:27.939 --> 01:25:31.380
that's nice that you know because companies don't

01:25:31.380 --> 01:25:33.220
really do stuff like that anymore but you know

01:25:33.220 --> 01:25:38.180
it's a smaller kind of company i guess and okay

01:25:38.180 --> 01:25:42.619
okay and oh well what layout do you use you use

01:25:42.619 --> 01:25:45.760
qwerty or you use one of the exotic you know

01:25:45.760 --> 01:25:50.079
keyboard layouts qwerty because obviously with

01:25:50.079 --> 01:25:52.619
the vim motions and everything i don't want to

01:25:52.619 --> 01:25:59.789
mess all of that up Yeah, me too. Because, yeah,

01:25:59.909 --> 01:26:02.289
I'm not going to move to something like Dvorak

01:26:02.289 --> 01:26:06.789
or Colmac. Because now HJ, KNL, that doesn't

01:26:06.789 --> 01:26:10.069
make any sense anymore. And, you know, I would

01:26:10.069 --> 01:26:12.609
have like a million key bindings in Emacs to

01:26:12.609 --> 01:26:16.789
go back and change. And it's not worth it. Okay.

01:26:17.029 --> 01:26:19.470
What are your thoughts on homelabs? That's the

01:26:19.470 --> 01:26:22.069
final question that I have. Are you into homelabbing?

01:26:22.750 --> 01:26:27.289
I don't have a... Home lab myself as far as,

01:26:27.329 --> 01:26:29.470
you know, this whole home lab thing, I guess

01:26:29.470 --> 01:26:31.229
it's kind of a recent phenomenon. I didn't even

01:26:31.229 --> 01:26:34.970
know the word until about a year or so ago when

01:26:34.970 --> 01:26:36.590
it was like the new buzzword people were talking

01:26:36.590 --> 01:26:38.670
about. It's basically I've got some servers at

01:26:38.670 --> 01:26:41.069
home. Yep. Like, well, I mean, I kind of play

01:26:41.069 --> 01:26:44.329
with that kind of stuff anyway. But now a lot

01:26:44.329 --> 01:26:46.250
of people that do the home lab stuff, I understand

01:26:46.250 --> 01:26:49.609
why they do it. Things like media servers, which

01:26:49.609 --> 01:26:53.130
I'm not really interested in. It doesn't really

01:26:53.130 --> 01:26:56.619
do much for me. Setting up a NAS would be cool

01:26:56.619 --> 01:26:58.300
because of video storage. I wouldn't mind doing

01:26:58.300 --> 01:27:00.800
something like that. Or, I mean, would I really

01:27:00.800 --> 01:27:03.340
want to host my own Nextcloud server? I'd rather

01:27:03.340 --> 01:27:07.340
host that on a proper web host, you know, instead

01:27:07.340 --> 01:27:11.060
of doing that myself. And there's not a lot of

01:27:11.060 --> 01:27:13.180
things I would want locally. What do I do in

01:27:13.180 --> 01:27:15.220
the NAS server, though? NAS server would be cool.

01:27:15.659 --> 01:27:19.819
Yeah, I do have Homelab. It's not complicated

01:27:19.819 --> 01:27:23.310
stuff. I have three. of those micro computers

01:27:23.310 --> 01:27:30.689
that they'll micros let me see if i these are

01:27:30.689 --> 01:27:33.630
pretty small they don't make noise they're wonderful

01:27:33.630 --> 01:27:38.170
so i have three of those and uh 128 gigs of ram

01:27:38.170 --> 01:27:42.529
in total and i do have my storage server set

01:27:42.529 --> 01:27:46.340
up that way i have a cluster cluster Cluster,

01:27:46.340 --> 01:27:49.819
basically. So if I lose one of my three storage

01:27:49.819 --> 01:27:52.600
servers, I have them here. Where are they? VMs.

01:27:52.619 --> 01:27:56.640
These are my storage servers. Storage one, two,

01:27:56.720 --> 01:27:59.159
and three, right? So I can lose one of them and

01:27:59.159 --> 01:28:02.560
I can still keep it working. I know I should

01:28:02.560 --> 01:28:05.220
be using something else like Ceph, but man, that's

01:28:05.220 --> 01:28:07.500
too complicated for me. I just went with cluster.

01:28:07.880 --> 01:28:10.739
Works fine. I use it just as a Samba server,

01:28:11.000 --> 01:28:13.460
basically. So just to store my videos, right?

01:28:13.560 --> 01:28:16.729
Just keep them there. Right. To keep, you know,

01:28:16.750 --> 01:28:20.970
just to store information, basically. But, yeah,

01:28:21.270 --> 01:28:23.750
that's something I should do some some days.

01:28:25.550 --> 01:28:27.310
It's something I've been thinking about really

01:28:27.310 --> 01:28:29.170
since starting the YouTube channel is having

01:28:29.170 --> 01:28:32.770
file server and some storage for my videos. I

01:28:32.770 --> 01:28:36.729
just use Amazon. Oh, AWS. It's reliable for sure.

01:28:37.109 --> 01:28:40.390
And it's so damn cheap. Yeah, I've got, you know,

01:28:40.390 --> 01:28:42.869
terabytes and terabytes of video sitting there.

01:28:43.420 --> 01:28:45.520
And what do they charge? Like a few bucks a month

01:28:45.520 --> 01:28:48.760
for like something crazy small. I was like, you

01:28:48.760 --> 01:28:51.100
know what? There's no, no reason not to use it.

01:28:51.260 --> 01:28:53.340
Yeah. You're right. They're reliable, you know,

01:28:53.359 --> 01:28:56.380
much more reliable than I would be. Yeah. So

01:28:56.380 --> 01:28:58.979
that's for sure. Definitely. That's one of my

01:28:58.979 --> 01:29:02.340
fears, you know, that I'm not as reliable as

01:29:02.340 --> 01:29:05.840
Amazon. So it could all be gone in a couple of

01:29:05.840 --> 01:29:08.899
minutes, you know, compared to Amazon. Yeah.

01:29:08.939 --> 01:29:12.689
I like storing that stuff. Every video I make,

01:29:12.729 --> 01:29:14.829
I always, you know, when I upload it to YouTube,

01:29:14.989 --> 01:29:18.109
upload it to Amazon just as a backup in case

01:29:18.109 --> 01:29:22.210
YouTube deletes a video for unknown reason, deletes

01:29:22.210 --> 01:29:24.590
my channel for some weird reason or just YouTube

01:29:24.590 --> 01:29:27.829
goes away completely. You know, I want all that

01:29:27.829 --> 01:29:31.029
stuff. That's one of the reasons why I'm on Odyssey.

01:29:31.829 --> 01:29:35.010
Oh, it makes sense. It's just I've got all of

01:29:35.010 --> 01:29:37.409
my videos in two different places just in case,

01:29:37.489 --> 01:29:40.770
you know. It's there online for people to go

01:29:40.770 --> 01:29:44.989
watch. YouTube, though, these days isn't too

01:29:44.989 --> 01:29:49.630
bad about accidentally taking videos down for

01:29:49.630 --> 01:29:52.130
no reason. They used to be much worse, especially

01:29:52.130 --> 01:29:55.449
in the Linux space. When I first started, Linux

01:29:55.449 --> 01:29:58.149
was smaller. It's a community of hackers, right?

01:29:58.210 --> 01:30:03.930
It's evil people. No, but I had there was one

01:30:03.930 --> 01:30:06.970
year in the first or second year of me after

01:30:06.970 --> 01:30:10.520
I started the channel. Where I had probably 100

01:30:10.520 --> 01:30:13.420
straight videos that were instantly demonetized

01:30:13.420 --> 01:30:17.880
as soon as I uploaded them. For no reason. As

01:30:17.880 --> 01:30:20.539
soon as you upload it, it's demonetized. And

01:30:20.539 --> 01:30:23.699
you got to go appeal. And then they'd always

01:30:23.699 --> 01:30:25.640
overturn it because there's no reason for these

01:30:25.640 --> 01:30:28.100
things to be. What am I doing? Writing some bash

01:30:28.100 --> 01:30:30.539
script, writing some Python. Configuring a tiling

01:30:30.539 --> 01:30:34.960
window manager. Ooh, evil. So you got to appeal

01:30:34.960 --> 01:30:37.140
and they always overturn it. Like two or three

01:30:37.140 --> 01:30:39.300
days later, take them a couple days. Well, what

01:30:39.300 --> 01:30:42.579
happens when you upload a video? When do most

01:30:42.579 --> 01:30:45.159
of the views come in? Yeah, when you upload it.

01:30:45.479 --> 01:30:47.979
Yeah, first day or two. So after a couple days,

01:30:48.159 --> 01:30:50.399
you monetize my video. Well, thank you. Everybody's

01:30:50.399 --> 01:30:53.380
already watched the damn thing. Yeah, definitely.

01:30:54.020 --> 01:30:58.840
Have you had any strikes in YouTube? Nothing

01:30:58.840 --> 01:31:01.579
that was a real strike, but yeah. There's some

01:31:01.579 --> 01:31:05.470
things you appeal and they get overturned. So,

01:31:05.470 --> 01:31:07.470
I mean, that's unfortunate that you get some

01:31:07.470 --> 01:31:10.550
false strikes on occasion. I had two or three,

01:31:10.649 --> 01:31:15.350
again, that weren't anything. Hell, I don't typically

01:31:15.350 --> 01:31:17.989
use like foul language or anything on my videos.

01:31:18.050 --> 01:31:21.710
Nothing to actually really strike me for. But

01:31:21.710 --> 01:31:25.930
I've had a couple of, I guess, something tripped

01:31:25.930 --> 01:31:28.850
up the algorithm in some way. And it's like,

01:31:28.930 --> 01:31:31.550
hey, you can appeal. They give you a little link

01:31:31.550 --> 01:31:34.039
and you just say. Whatever it is you're saying

01:31:34.039 --> 01:31:37.020
I did here, it really didn't happen. And then

01:31:37.020 --> 01:31:38.840
I guess a human being is supposed to go look

01:31:38.840 --> 01:31:42.460
at the video. And if they do, they always overturn

01:31:42.460 --> 01:31:44.420
it. It's like, yeah, they take them off then.

01:31:44.819 --> 01:31:51.100
Yeah. OK, great. All right. Any anything else?

01:31:51.140 --> 01:31:54.399
I already took a lot of your time. And, you know,

01:31:54.460 --> 01:31:57.460
thanks for all this. This was fun. Yeah. I mean,

01:31:57.460 --> 01:32:00.760
I had a busy morning this morning because I had

01:32:00.760 --> 01:32:03.819
a. I actually run a second YouTube channel that's

01:32:03.819 --> 01:32:06.960
not Linux related. Oh, really? You want to share?

01:32:07.060 --> 01:32:11.899
Trading related. Yeah, it's DT Options. DT Options.

01:32:12.060 --> 01:32:15.899
It's about options trading. Oh, this one? Yeah,

01:32:15.960 --> 01:32:20.659
I hold a little group session there on most days,

01:32:20.739 --> 01:32:23.880
Monday through Friday, in a trading Discord group

01:32:23.880 --> 01:32:26.939
that I run. I was doing that this morning, and

01:32:26.939 --> 01:32:31.260
then I was also working on... Trying to get the

01:32:31.260 --> 01:32:34.560
latest ISO of the Linux distribution I've been

01:32:34.560 --> 01:32:37.979
working on here recently, DTOS, which essentially

01:32:37.979 --> 01:32:40.199
you saw on camera is what I'm essentially running

01:32:40.199 --> 01:32:46.920
here. Oh. Trying to work on that. Oh, yeah. I

01:32:46.920 --> 01:32:49.000
had a lot going on this morning. I know it probably

01:32:49.000 --> 01:32:52.000
was running a little later than what you wanted

01:32:52.000 --> 01:32:54.140
as far as jumping on this call and getting this

01:32:54.140 --> 01:32:58.789
done. No, it was. Hopefully it worked out. You

01:32:58.789 --> 01:33:00.689
know, and I really want to thank you for your

01:33:00.689 --> 01:33:03.670
time. Really appreciate it because I know it's

01:33:03.670 --> 01:33:07.029
a lot of work. You must be pretty busy. So thanks

01:33:07.029 --> 01:33:09.750
for taking the time and joining the call. Any

01:33:09.750 --> 01:33:11.449
final words, anything you want to share before

01:33:11.449 --> 01:33:15.670
we finish the call? Just thanks for having me.

01:33:15.750 --> 01:33:18.029
This was a fun discussion. And if you ever want

01:33:18.029 --> 01:33:20.609
to do it again or want to come on my channel,

01:33:20.729 --> 01:33:24.310
you know, we expose you to a bigger audience.

01:33:24.840 --> 01:33:27.880
Oh, that would be awesome. Well, hit me up. You've

01:33:27.880 --> 01:33:31.479
got my email now. Yeah. Appreciate it, Derek.

01:33:31.720 --> 01:33:34.140
All right. All right. Nice talking to you. Bye.

01:33:34.659 --> 01:33:35.039
Bye.