Linus' Next Big Thing
Apr 13, 2025
Apple's software is going rotten, while Linux sneaks up as the better Mac. Linus grumbles through Git's 20th birthday, and we spot a hardware window Linux better not slam shut.
Sponsored By:
- Tailscale: Tailscale is a programmable networking software that is private and secure by default - get it free on up to 100 devices!
- 1Password Extended Access Management: 1Password Extended Access Management is a device trust solution for companies with Okta, and they ensure that if a device isn't trusted and secure, it can't log into your cloud apps.
- ConfigCat Feature Flags: Manage features and change your software configuration using ConfigCat feature flags, without the need to re-deploy code.
Links:
- 💥 Gets Sats Quick and Easy with Strike
- 📻 LINUX Unplugged on Fountain.FM
- Tailscale Community Meetup Seattle — Calling all Tailscale users, homelabbers, and networking enthusiasts! We’re bringing the community together for a casual, community focused meetup in Seattle.
- POLL: Would you tune into a Saturday LFNW Live Stream?
- Celebrating Git's 20th anniversary with creator Linus Torvalds — Discover the origins of the open-source version control system, why he handed over the reins a few months in, and what he thinks about adding new programming languages to Git.
- Two decades of Git: A conversation with creator Linus Torvalds - YouTube
- uemacs - Linus Editor — Random version of microemacs with my private modificatons
- Yes Linus' uemacs is pacakged in Nix
- Debian APT 3.0 Stable Released With New Package Solver & Refined Text UI — This new version introduces a significantly refined command-line interface and a completely new package solver.
- I Want a Better Mac, so I’m Cheering for a Better Linux — "Apple needs a real competitor, one alternatives such as GNOME on Linux could actually be, if only the hardware rose to the occasion."
- I'd love to see someone help Linux take the next step
- outdoorgeek's laptop sleep optimized NixOS config
- Rust is easy? Go is… hard?
- Pick: chat-gipitty: Terminal client for getting answers from LLMs — Chat Gipitty (Chat Get Information, Print Information TTY) is a command line client for ChatGPT. It allows you to chat with your chosen model of ChatGPT in a terminal and even pipe output into it.
- moreutils' sponge — soak up standard input and write to a file.
- GitHub - pgdr/moreutils — a growing collection of the unix tools that nobody thought to write long ago when unix was young.
- Pick: ALttP VT Randomizer — Each playthrough shuffles the location of all the important items in the game. Will you find the Bow atop Death Mountain, the Fire Rod resting silently in the library, or even the Master Sword itself waiting in a chicken coop?
- spannerisms/ALttPNG
Transcript
WEBVTT
00:00:18.784 --> 00:00:19.764
My name is Wes. this.
00:00:59.104 --> 00:01:00.284
Thanks for being here.
00:01:00.844 --> 00:01:05.724
Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris.
00:01:06.364 --> 00:01:07.544
And my name is Brent.
00:01:08.084 --> 00:01:12.844
Hello, gentlemen. Today we'll talk about Linus grumbling through 20 years of
00:01:12.844 --> 00:01:18.864
Git, a hardware window that may be opening up for Linux, and a look at App 3.0.
00:01:18.984 --> 00:01:23.404
Then we'll round it out with a really useful pick, some great boosts, and a lot more.
00:01:23.664 --> 00:01:27.504
So before we get into all of that, let's say time-appropriate greetings to our
00:01:27.504 --> 00:01:29.824
virtual lug. Hello, Mumble Room.
00:01:30.344 --> 00:01:32.684
Hello, Simon. Hello, Brent.
00:01:33.884 --> 00:01:36.664
Hello, y'all. Nice to see you up there, and hello, everybody up there in the
00:01:36.664 --> 00:01:39.704
quiet listening that's just quietly saying hello this morning.
00:01:40.024 --> 00:01:43.544
I see some old friends up there. It's nice to see you. The Mumble Room is open
00:01:43.544 --> 00:01:47.604
for every show, and it gives it kind of like this live vibe.
00:01:47.764 --> 00:01:51.244
Like what's really happening now and eventually it makes us have to start the
00:01:51.244 --> 00:01:52.684
show too. So there's that as well.
00:01:53.084 --> 00:01:55.324
Details at jupiterbroadcasting.com slash mumble.
00:01:58.228 --> 00:02:03.668
And a big good morning to our friends over at TailScale. Head over to TailScale.com
00:02:03.668 --> 00:02:07.288
slash unplugged and get it for free up to 100 devices and three users.
00:02:07.688 --> 00:02:11.008
TailScale is the easiest way to connect devices and services to each other wherever
00:02:11.008 --> 00:02:15.648
they are. They solve the problem of networking. The internet never quite got there.
00:02:16.048 --> 00:02:20.928
TailScale is modern networking that builds a flat mesh network protected by...
00:02:20.928 --> 00:02:22.108
Why do you got to keep saying that?
00:02:22.328 --> 00:02:25.108
You put your nodes on there, it doesn't matter if they're in multiple different
00:02:25.108 --> 00:02:29.128
VPS providers or if they're on your homeland or if it's a mobile device,
00:02:29.708 --> 00:02:33.628
Tailscale brings them all together secure, and it is really fast.
00:02:33.788 --> 00:02:37.468
It's privacy for individuals and every organization out there.
00:02:37.788 --> 00:02:42.828
Intuitive and easy to deploy, and the great thing is, with 100 devices and three
00:02:42.828 --> 00:02:47.588
users, when you go to tailscale.com slash unplugged, you get a genuine sense of the service.
00:02:47.748 --> 00:02:50.968
And when you're ready, you might suggest it to your buddies at work.
00:02:51.128 --> 00:02:53.708
I mean, that's kind of what we did. We started on our personal plans,
00:02:53.748 --> 00:02:55.808
and we expanded to using it here at Jupyter Broadcasting.
00:02:56.308 --> 00:02:59.368
Thousands of companies out there now use Tailscale the same way.
00:02:59.488 --> 00:03:01.588
So go try it out for yourself or for a business.
00:03:02.108 --> 00:03:06.248
See why we love it so much. Go to Tailscale.com slash unplugged.
00:03:06.508 --> 00:03:13.748
And by the way, special little PSA for you. Tailscale has a meetup coming in May, and it's May 8th.
00:03:13.888 --> 00:03:16.848
We'll have a link in the show notes. It's one of their first community meetups,
00:03:16.908 --> 00:03:18.088
and it's right here in Seattle.
00:03:18.548 --> 00:03:22.068
We may even have a guest speaker of our own there at the meetup, perhaps.
00:03:22.388 --> 00:03:25.588
It should be a lot of fun. Mm-hmm. So if you're in the Seattle area and you
00:03:25.588 --> 00:03:27.948
want to go to one of their first Tailscale community meetups,
00:03:28.088 --> 00:03:32.668
check out the link and support the show by going to tailscale.com slash unplugged.
00:03:35.124 --> 00:03:38.144
One little bit of housekeeping before we get going.
00:03:38.384 --> 00:03:42.284
We're kind of on the fence about doing a Saturday live stream,
00:03:42.424 --> 00:03:43.984
the first full day of LinuxFest.
00:03:44.144 --> 00:03:47.424
I put out a poll last week, and it hasn't gotten very many votes.
00:03:47.564 --> 00:03:50.804
It's 60% yes, but 40% nay.
00:03:51.184 --> 00:03:54.024
It's a little close for the amount of work we're going to be putting in.
00:03:54.304 --> 00:03:58.424
So send us a boost or go vote in the poll and let us know if you'd like a live
00:03:58.424 --> 00:04:03.124
stream from LinuxFest the day, Saturday, before our Sunday show.
00:04:03.624 --> 00:04:07.704
We're thinking about doing a little different this year if we do this we've
00:04:07.704 --> 00:04:10.964
always done it at a booth before at linux fest and we're kind of thinking maybe
00:04:10.964 --> 00:04:15.384
this year the live stream will actually be anchored from lady joops the rv on the parking lot do.
00:04:15.384 --> 00:04:16.724
Things in the wrong order right.
00:04:16.724 --> 00:04:20.644
Some advantages to that you know it means we have a little more control over
00:04:20.644 --> 00:04:24.684
the technical and the audio and the internet and based on prior tests we think
00:04:24.684 --> 00:04:30.104
it makes for a better live stream and then what we do is along with our commentary
00:04:30.104 --> 00:04:33.384
of the event what's going on chatting with guests, inviting people out to come out to us.
00:04:34.244 --> 00:04:37.964
We send a couple of men in on the scene like a, you know, like a Brent Noah
00:04:37.964 --> 00:04:39.724
tag team or a me and you tag team.
00:04:39.804 --> 00:04:42.644
And we go out there and we interview folks and presenters in the booth and we
00:04:42.644 --> 00:04:44.264
stream that back to the live stream.
00:04:45.024 --> 00:04:51.404
And if we can, big caveat there, but if we can stream select audio talk as well.
00:04:52.284 --> 00:04:55.524
So that's kind of our ambitious plans if we do a Saturday stream,
00:04:55.644 --> 00:04:58.024
but we only want to do it if you're going to listen.
00:04:58.144 --> 00:05:00.664
So boost in or go vote in the poll we have in the show notes.
00:05:01.064 --> 00:05:02.404
It's a straw poll. It's real easy.
00:05:03.124 --> 00:05:10.904
And let us know if you would tune in Saturday, which is going to be April 20, no, 26th, right?
00:05:11.884 --> 00:05:13.664
April 26 on a Saturday. That's, woo.
00:05:14.684 --> 00:05:16.464
It's coming up real fast. So please let us know.
00:05:19.844 --> 00:05:25.964
Some big, big milestones recently, and one of them was Git turning 20 years
00:05:25.964 --> 00:05:28.304
old, of course, created by Linus Torvalds.
00:05:29.104 --> 00:05:35.344
And to celebrate, GitHub did an interview with Linus, which is kind of interesting
00:05:35.344 --> 00:05:39.544
because Linus hasn't always been the biggest GitHub fan. He's obviously a big Git fan.
00:05:40.164 --> 00:05:43.344
But they have a kind of a wide-ranging interview. I don't know if either of
00:05:43.344 --> 00:05:48.164
you had a chance to read it, but it wasn't, I think, anything too new that we didn't already know.
00:05:48.744 --> 00:05:51.524
Linus is always so humble about his participation in Git.
00:05:58.604 --> 00:05:59.764
Yes, yes, yes.
00:06:11.404 --> 00:06:14.824
Yeah, in the interview, he talks about basically all the Git functionality he
00:06:14.824 --> 00:06:15.904
needed was there in a few months.
00:06:16.624 --> 00:06:18.964
And then it was just everybody kind of adding what they needed.
00:06:19.504 --> 00:06:23.824
So that was interesting. And then, like you said, he had a video interview with GitHub.
00:06:24.684 --> 00:06:27.564
And so the text interview is with GitLab, to make this clear.
00:06:27.784 --> 00:06:29.184
The video interview is with GitHub.
00:06:30.064 --> 00:06:34.124
And the title was Two Decades of Git, a Conversation with Creator Linus Torvalds.
00:06:34.164 --> 00:06:36.904
And we'll link to the full video in the show notes. It's, I don't know, about a half hour.
00:06:37.664 --> 00:06:42.944
And first of all, it's nice just to see Linus outside the LinuxCon conference
00:06:42.944 --> 00:06:46.024
Dirk-style interview scene. It's been a while since we've seen anything but that.
00:06:47.691 --> 00:06:50.371
And one of the things they touch on at the end of the interview is,
00:06:50.571 --> 00:06:53.791
what is the next big success for Linus?
00:06:54.211 --> 00:06:57.891
He seems to have a cadence of every 20 years or so, he has these major projects
00:06:57.891 --> 00:07:01.651
that he releases that change the world, like the Linux kernel and like Git.
00:07:02.051 --> 00:07:05.471
And you can tell Linus hates this question, and I thought his answer was fascinating.
00:07:06.011 --> 00:07:09.431
On schedule, Linux came about 34 years ago.
00:07:12.331 --> 00:07:14.131
Yeah, Git 20.
00:07:14.131 --> 00:07:18.071
Which involves maybe the worst CAPTCHA system ever devised.
00:07:18.311 --> 00:07:22.151
And so maybe five or so years overdue for the next big thing. No, no.
00:07:22.431 --> 00:07:27.651
I see the other way around. All the projects that I've had to make, I had to make because...
00:07:27.651 --> 00:07:30.151
Yeah, and if you don't want it, it's better because you can quit when you're bored.
00:07:30.271 --> 00:07:34.871
I couldn't find anything better that somebody else did. But I much prefer other
00:07:34.871 --> 00:07:37.051
people solving my problems for me, right?
00:07:37.851 --> 00:07:42.171
So me having to come up with a project is actually a failure of the world,
00:07:42.771 --> 00:07:47.331
right? And the world just hasn't failed in the last 20 years for me.
00:07:49.891 --> 00:07:53.051
I started doing Linux because I needed an operating system.
00:07:53.191 --> 00:07:56.931
Will you say it like that? It almost sounds like it shouldn't work.
00:07:57.171 --> 00:08:01.191
And yet this was like a super ultimately reliable method to have it work.
00:08:01.231 --> 00:08:07.191
Well, no longer my DiveWard software. But that was so specialized that it never took off in a big way.
00:08:07.731 --> 00:08:17.431
And that solved one particular problem. but my computer use is actually so limited
00:08:17.431 --> 00:08:21.451
that I think I've solved all the problems.
00:08:22.371 --> 00:08:29.051
Part of it is probably I've been doing it so long that I can only do things in certain ways.
00:08:29.051 --> 00:08:34.811
I'm still using the same editor that I used when I was in college because my
00:08:34.811 --> 00:08:40.131
fingers have learned one thing and there's no going back. And I know the editor is crap.
00:08:40.691 --> 00:08:44.211
And I maintain it because it's a dead project that nobody else uses.
00:08:44.511 --> 00:08:49.551
So I have a source tree and I compile my own version every time I install a new machine.
00:08:50.851 --> 00:08:54.831
And I would suggest nobody ever use that editor. But I can't.
00:08:55.251 --> 00:09:00.471
I've tried. I've tried multiple times finding an editor that is more modern
00:09:00.471 --> 00:09:06.511
and does fancy things like colorize my source code and do things like that.
00:09:06.511 --> 00:09:12.851
And every time I try it, I'm like, yeah, these, these hands are too old for this.
00:09:13.771 --> 00:09:21.571
Right. So, so I really hope there is no project that comes along that makes me go, I have to do this.
00:09:21.891 --> 00:09:24.291
Yeah. Well, on that note.
00:09:24.471 --> 00:09:26.631
There's a couple of things in there that stood out to me that,
00:09:27.031 --> 00:09:31.031
you know, he really only has to build something when the world hasn't solved that problem for him.
00:09:31.091 --> 00:09:35.151
And so it's kind of a good thing if, you know, he hasn't had to build anything. Yeah, right. Right.
00:09:49.303 --> 00:09:53.323
Not only did we have to get Brent with the game installed, we had to teach Brent
00:09:53.323 --> 00:09:55.003
how to play. Mostly, me too.
00:09:56.283 --> 00:10:00.623
Yeah. And then the other thing that jumped out to me in there is that he said
00:10:00.623 --> 00:10:04.343
he has this horrible, horrible text editor that he uses.
00:10:04.663 --> 00:10:07.143
Yeah. Yeah, it's a very...
00:10:17.623 --> 00:10:20.123
Oh my god you,
00:10:22.823 --> 00:10:29.463
i will say i hope i hope this was um satisfying for producer jeff uh because
00:10:29.463 --> 00:10:33.743
he has been trying to get us to play some StarCraft for way too long,
00:10:33.743 --> 00:10:35.243
so it's on us for taking so long.
00:10:35.463 --> 00:10:35.863
You gave it a go.
00:10:36.383 --> 00:10:39.283
He rightfully pointed out at one point that, you know, Brent,
00:10:39.403 --> 00:10:42.903
if you'd listened to him earlier, you would have been upskilled on StarCraft.
00:11:01.643 --> 00:11:07.563
So you whoa really that's a whole new kind of trapped in the editor.
00:11:13.183 --> 00:11:17.863
It is actually pretty legit a great little hack for live presentations.
00:11:22.223 --> 00:11:25.883
What a mind what a mind job it is that one of the most advanced important software
00:11:25.883 --> 00:11:29.383
projects in the world is being run by that editor,
00:11:52.826 --> 00:11:58.046
Brent, 20 years into Git, it feels like Git, and especially GitHub,
00:11:58.446 --> 00:12:03.466
are such monumental successes that they're just fully integrated into most of
00:12:03.466 --> 00:12:04.646
the open source world now.
00:12:04.886 --> 00:12:09.506
I mean, when's the last time you worked on a project that wasn't using Git?
00:12:09.866 --> 00:12:13.266
Like, everybody's using it, it seems. Although I did find it interesting to
00:12:13.266 --> 00:12:16.186
look at a little bit of the history of version control, and it seems like every
00:12:16.186 --> 00:12:18.966
decade, decade and a half, there's a new one that comes around.
00:12:19.846 --> 00:12:24.266
Maybe Git's the exception of that because it's just integrated so deeply into
00:12:24.266 --> 00:12:25.966
every project, it seems, these days.
00:12:27.086 --> 00:12:31.246
But who knows? Maybe there's an opportunity here. I mean, I think,
00:12:31.246 --> 00:12:34.766
is there a reason to come up with something else?
00:12:34.806 --> 00:12:37.226
And a lot of people, when I was learning Git, said, yeah, yeah.
00:12:37.326 --> 00:12:38.426
On a fastest map.
00:12:38.866 --> 00:12:41.746
Can be better. And there are other projects, like Mercurial,
00:12:41.826 --> 00:12:43.466
for instance, that are trying to do things better.
00:12:43.826 --> 00:12:49.166
But you'd have to be so much better, right? I think the quintessential question
00:12:49.166 --> 00:12:51.766
is, could you have a Git scale success today?
00:12:52.466 --> 00:12:56.946
In 2028 or by 2030, could something else come along that could be the scale
00:12:56.946 --> 00:12:58.846
of GitHub with Git behind it?
00:12:58.946 --> 00:13:01.266
I don't think we can ever see that again.
00:13:24.286 --> 00:13:33.266
Yeah, you were really keyed in on building the society, which was kind of fun.
00:13:33.426 --> 00:13:35.986
There's a lot to build. I just...
00:13:48.729 --> 00:13:53.009
I think it's the one-two combo of you can start your life with Git.
00:13:53.209 --> 00:13:56.689
You can never be bothered with the cloud or any kind of a remote service.
00:13:56.849 --> 00:13:58.129
You can just use Git on your laptop.
00:13:58.809 --> 00:14:02.029
And then one day you start working with a project that's on GitHub,
00:14:02.029 --> 00:14:04.629
and a lot of those skill sets just immediately translate.
00:14:04.929 --> 00:14:09.309
And that is such a powerful network effect. And that's one of the things we
00:14:09.309 --> 00:14:13.949
see in technology over and over again is the network effect is the item we don't
00:14:13.949 --> 00:14:16.409
really account for that just seems to be entrenchable.
00:14:16.409 --> 00:14:19.809
And I don't know, the more I think about it, I don't think you could have a
00:14:19.809 --> 00:14:23.349
Git and GitHub combo success story today. I don't think it's possible.
00:14:28.149 --> 00:14:30.349
Boost in and tell us what you think out there or what else it might be.
00:14:40.049 --> 00:14:43.329
Yeah, yeah. Yeah. So even on its own.
00:14:44.609 --> 00:14:49.689
But I was looking at the Git repo, and they have 1,750 contributors,
00:14:49.989 --> 00:14:52.329
so on a bit of a different scale these days.
00:14:52.829 --> 00:14:56.089
Yeah, I suppose so. Something else is on a different scale.
00:14:57.049 --> 00:15:02.709
Apt, Debian Apt 3.0 stable has been released, which means we should see it in
00:15:02.709 --> 00:15:05.729
Debian 13 and Ubuntu 2504.
00:15:06.069 --> 00:15:10.469
And Apt 3.0 is one that actually is getting a bit of attention because it has
00:15:10.469 --> 00:15:12.869
a significantly refined command line interface, they say.
00:15:13.329 --> 00:15:18.429
A completely new package solver, and rather noticeable UI enhancements,
00:15:18.509 --> 00:15:22.749
including colorized text, a new layout style, and just a clearer formatting
00:15:22.749 --> 00:15:27.149
overall of the results, making it, I guess they say, easier to understand.
00:15:27.969 --> 00:15:30.969
And I guess at a technical level, they've upgraded Solver 3,
00:15:31.629 --> 00:15:35.489
which is a fully new backtracking system that avoids promoting manually installed
00:15:35.489 --> 00:15:39.149
packages for removal and handles the auto-removal more aggressively.
00:15:39.889 --> 00:15:43.289
So, Wes, you spelunked into App 3.0. yeah that's,
00:15:58.573 --> 00:16:02.773
Yeah. Oh, good. Yeah, really.
00:16:12.733 --> 00:16:13.953
Brent's a survivor.
00:16:35.033 --> 00:16:36.253
Oh, that's good to hear, yeah.
00:16:43.033 --> 00:16:46.273
So, but the thing I keep hearing about is this new colored output,
00:16:46.513 --> 00:16:50.453
this new columnar display or whatever they call it. Did you notice that kind of stuff?
00:16:58.573 --> 00:17:03.173
Yes.
00:17:27.753 --> 00:17:34.253
I hate to say this, but I bet that kind of thing had it been in place when Linus
00:17:34.253 --> 00:17:36.453
NumNuts was testing Pop!
00:17:36.593 --> 00:17:40.233
OS and he uninstalled his entire desktop, and then he basically slammed the
00:17:40.233 --> 00:17:42.393
distribution for him being the one to uninstall stuff.
00:17:42.873 --> 00:17:47.613
If it had been in big red text jumping out at him, he might have been more inclined to catch it.
00:18:01.233 --> 00:18:02.553
You,
00:18:32.133 --> 00:18:37.173
You could search, maybe. Hmm, yeah, I installed this when we were monkey-ing around with XYZ.
00:18:44.766 --> 00:18:48.746
It reminds me of get commit comments just to tie the story, two stories together,
00:18:48.946 --> 00:18:51.686
which actually are super helpful when you go back a month, a year,
00:18:52.026 --> 00:18:54.406
five years, and you're like, what did I do again?
00:18:58.166 --> 00:19:03.506
Onepassword.com slash unplugged. That's the number one password.com slash unplugged.
00:19:03.586 --> 00:19:04.506
And that's all lowercase.
00:19:04.746 --> 00:19:09.526
One password lets you secure every app, every device, and every identity,
00:19:09.766 --> 00:19:11.026
even the unmanaged ones.
00:19:11.166 --> 00:19:14.626
Let me ask you a question because I've been there. I know how this works.
00:19:14.766 --> 00:19:18.386
Do your end users always, and I mean always without exception,
00:19:18.586 --> 00:19:21.846
work on company-owned devices and IT-approved apps?
00:19:22.806 --> 00:19:26.866
I didn't think so. No, I mean they really can't these days. There's just so much coming at them.
00:19:27.006 --> 00:19:30.726
So the next question naturally is how do you keep your company's data safe when
00:19:30.726 --> 00:19:35.126
it's sitting on unmanaged apps, unmanaged devices, and all these types of things?
00:19:35.946 --> 00:19:39.926
Well, 1Password has the answer to this question. It's extended access management.
00:19:39.926 --> 00:19:44.646
One Password Extended Access Management helps you secure every sign-on for every
00:19:44.646 --> 00:19:49.926
app on every device because it solves the problems that traditional IAMs and
00:19:49.926 --> 00:19:52.646
NDMs just, well, they weren't built to touch.
00:19:53.166 --> 00:19:56.806
That's the beauty here. So you know password management is so important.
00:19:56.986 --> 00:20:00.706
And One Password has the most user-friendly and thus user-successful password
00:20:00.706 --> 00:20:01.706
manager application out.
00:20:01.806 --> 00:20:06.126
They're trusted by millions of users, over 150,000 businesses from IBM and Slack.
00:20:06.686 --> 00:20:10.646
But they're going beyond passwords. With extended access management,
00:20:10.806 --> 00:20:17.326
you're securing every app, every device, every identity, even contractor and unmanaged ones.
00:20:18.126 --> 00:20:23.606
That's the real power here, all from one dashboard. So go to 1Password.com slash unplugged.
00:20:23.646 --> 00:20:26.446
That's all lowercase. You can support the show. Check it out. Get more information.
00:20:27.266 --> 00:20:30.986
It's 1Password.com slash unplugged. And go there and see how this could make
00:20:30.986 --> 00:20:32.726
a real difference for you and your organization.
00:20:33.146 --> 00:20:36.086
I know it would have made a huge impact for me. So one more time,
00:20:36.206 --> 00:20:39.066
it's 1password.com slash unplugged.
00:20:41.996 --> 00:20:46.536
Timothy R. Butler over at Open for Business recently wrote a post titled,
00:20:46.796 --> 00:20:48.956
Apple Needs a Snow Sequoia.
00:20:49.316 --> 00:20:54.216
In non-Mac speak, that is to say, Apple needs an upgrade to macOS Sequoia that's
00:20:54.216 --> 00:20:58.216
like its earlier Snow Leopard upgrade to the Leopard OS.
00:20:58.796 --> 00:21:04.556
An upgrade that's all about how little it added and how much it's focused on fixing things.
00:21:05.016 --> 00:21:07.756
This is a call you hear in the Mac community every few years.
00:21:07.876 --> 00:21:10.396
Apple, stop adding features and just fix things.
00:21:11.216 --> 00:21:16.536
Apple has been transitioning toolkits and architectures basically since the iPhone launched.
00:21:16.756 --> 00:21:21.556
And so it has kind of led to certain apps getting restarted,
00:21:21.976 --> 00:21:26.056
recreated, or getting updates maybe that are meant to work on multiple platform
00:21:26.056 --> 00:21:28.036
types that are not ideal for macOS.
00:21:28.576 --> 00:21:32.756
And there has been this growing chorus of concerns about the quality of Mac software.
00:21:32.916 --> 00:21:39.496
And Timothy's article here, his first one, was it just took off like crazy in
00:21:39.496 --> 00:21:43.176
the Mac community. and it was really just criticizing the quality of Mac software
00:21:43.176 --> 00:21:45.536
and saying that Apple needs to do a better job.
00:21:46.316 --> 00:21:50.316
The funny thing is, is he came up with a follow-up while that was still getting
00:21:50.316 --> 00:21:54.196
rolling, saying, I want a better Mac, so I'm cheering for better Linux.
00:21:54.736 --> 00:21:58.516
And it says, like, by the way, what about Linux, Mac users? Gotcha.
00:21:59.716 --> 00:22:03.096