HomeVideos

Luke talks RAM Pricing, Tech Youtube and LTT Developer hiring process | The Standup

Now Playing

Luke talks RAM Pricing, Tech Youtube and LTT Developer hiring process | The Standup

Transcript

2255 segments

0:00

Today we have a very special episode of

0:02

the standup. We have with us Luke from

0:04

Linus Tech Tips. Say hi.

0:06

>> All right. There he is. Right there. We

0:08

have

0:08

>> I thought it was Luke Tech Tips. Is Was

0:11

I right? New

0:12

>> to not be confused with LT. He has LTT.

0:14

This is LT, not LT.

0:15

>> Okay. Different LT. Got it. LT. Okay,

0:17

that makes sense. Thank you.

0:19

>> There's some other guy who no one knows

0:20

who's like a co-host or something on

0:22

that. The main channel, I think. I don't

0:24

know. But Luke's the main dude.

0:25

>> Luke's does the heavy lifting.

0:26

>> That's real.

0:27

>> All right. Thanks for the intro

0:28

interruption. Yeah.

0:33

Uh, anyways, sorry. Also with us is Tee

0:36

and I interrupt things.

0:39

>> Thank you. Yep. TJ, you're wearing a a

0:42

sweater that can no longer be bought. It

0:43

must be very exclusive.

0:45

>> Arch, by the way,

0:46

>> Arch forever.

0:50

>> TJ already has children, so it's okay.

0:52

Um, all right. Well, anyways, today

0:54

we're going to be about you have Can I

0:56

just say though, you have to get married

0:58

and have kids before you install.

0:59

Otherwise, it's GG, boys. Your line,

1:02

your family line is finished. Okay, your

1:04

ancestors are disappointed. They hunted

1:07

and gathered for nothing. You ended the

1:09

line just because of your operating

1:10

system. Wait till you have kids before

1:12

you start Arch. Thanks.

1:14

>> That's just the PSA for today.

1:15

>> That's a good PSA. Honestly, I think

1:17

more people need to hear that. Um, all

1:19

right. So, uh, today we're going to be

1:21

talking about RAM prices. get some

1:23

thoughts where we think it's going along

1:25

with probably SSDs and some other

1:26

things. Is there any other unknown costs

1:29

coming in? And then after that, I'm

1:30

going to probably ask Luke a little bit

1:31

about running Linus Tech Tips, what it's

1:33

like hiring people, all the good stuff.

1:35

Uh what does he kind of experience in

1:37

today's age of AI and such, especially

1:40

in the YouTube scene? Uh just because

1:42

it's a much different set of technology

1:44

and how you develop stuff and kind of

1:45

the software you run for. Uh very

1:47

curious about all that stuff. So, let's

1:48

start off obviously with the maiden

1:50

flagship topic, which is RAM prices. I

1:53

don't know about you, but the moment I

1:55

heard that AI loves RAM, the first thing

1:57

I did is went out and bought MU, uh,

1:59

which is a stock, Micron, which

2:01

exclusively does, uh, RAM. And guess

2:03

what? It was my best investment I have

2:05

ever made in my entire lifetime. And so,

2:08

there's there must be something there.

2:10

If the stock market says there's

2:11

something there, there must be a there

2:12

there. And so,

2:14

>> number go up.

2:15

>> The number does go up. Now, there's only

2:16

one person in this call that I know for

2:18

a fact can not only build the PC, but

2:21

also knows how to order a GPU from the

2:23

internet, which is an impossible task

2:25

these days. I have no idea how to order

2:27

a GPU. So, I figured that we'd bring

2:29

Luke on and he could uh kind of give us

2:32

some of his thoughts about this whole

2:33

RAM price debacle and where he kind of

2:36

thinks it going, where he thinks it's

2:37

kind of going and maybe inform us uh

2:40

uneducated non-GPU buyers about the

2:43

hardware market. the permanent

2:45

underclass. Permanent underclass right

2:47

here.

2:47

>> Sure. Yeah. I um I'm not surprised by

2:50

certain moves like uh like Micron's

2:54

Crucials. Uh so it was Crucial is owned

2:56

by Micron. Uh Crucial stepped out of the

2:58

RAM market. That was not too surprising.

3:01

I think they've honestly wanted to do

3:03

that for a long time. If you look at how

3:06

honestly somewhat specifically DDR5 was

3:09

even designed, it was not designed from

3:11

a consumer standpoint. was designed from

3:13

a enterprise standpoint. The goal has

3:16

been enterprise for a long time. This is

3:20

mostly a convenient and high profit exit

3:24

from the consumer space for Crucial. Um,

3:28

and I don't personally suspect that

3:30

prices are going to come down from

3:32

supply being super high for a pretty

3:35

considerable amount of time. It takes a

3:37

really long time to get fabs online. Um

3:40

and they are also going to resist the

3:42

fall of the price because they want it

3:44

to be high. Some of the like most

3:46

collusion in effectively like any market

3:50

anywhere has been in RAM. Uh these

3:53

companies love working together to price

3:55

fix. They love working together to um

3:58

keep prices not too high to not increase

4:01

fab capacity too much. That's another

4:03

thing they do to um I don't know if you

4:06

can say artificially or not. There you

4:08

go. Nice. Uh

4:09

>> I'm listening. I'm listening.

4:11

>> This is super well documented if you're

4:13

if you're interested in it. Um it

4:15

there's been a lot of legal suits over

4:17

it. Um it's it's not even a secret at

4:20

this point, let alone an open secret. So

4:21

you can it's Yeah, you can dive into it

4:24

if you're interested.

4:25

>> Commish, you got to listen to me.

4:27

>> Oh no. Now one more comment from you.

4:29

I'm done rebasing your mistakes. You're

4:30

on junior CSS duty until further notice.

4:33

>> Commish, you can't do this to me.

4:34

>> Keep talking and you'll be doing store

4:36

procedures for a month now. Get out of

4:38

here. Take him with you.

4:43

>> Fun fact, CSS is actually touring

4:46

complete.

4:58

>> Larry, Gary, Tango, Mary, I'm just

5:01

pulling your request. It looks good to

5:03

me. You're clear to ship. Thanks. You're

5:05

welcome. Next.

5:08

It's an awfully big PR

5:10

>> for an intern.

5:11

>> Well, I just bumped some dependencies.

5:13

It's nothing major.

5:16

>> Hey, can I get a quick stamp on this?

5:19

>> Yeah, don't worry about it.

5:21

>> Quick approval. Oh, not on my watch. I'm

5:24

on your disc like a pee on slur. Not

5:27

this again. It's literally just a hex

5:29

code change. Just to prove it. Just to

5:31

prove it. Squish. Perf resisting review.

5:34

Oh, I know you're the tipler. I've seen

5:36

vibe coding, but that AIN'T IT.

5:38

>> MERGE COP. NO,

5:44

>> I hate merge cop. He always makes

5:46

reviewing take forever. We have Code

5:48

Rabbit. Oh, come on. I wasn't even

5:50

merging the prod. It was a hex code

5:52

change. We have Code Rabbit. We don't

5:54

need real people reviewing such simple

5:56

changes. Code Rabbit can do it for us.

5:58

Our engineers time is better spent

6:00

solving problems for customers. You can

6:02

try it too at codrabbit.ai.

6:05

>> Next week on Merge Cop.

6:07

>> Now my plan to merge a dip so big you're

6:10

the dipler and I always knew it.

6:16

>> They have also worked together to yeah

6:17

not increase fab capacity. Now right now

6:20

there is enough demand that yeah they're

6:22

looking into fabs. There's partnerships

6:25

from from at least one brand to work

6:28

with a much smaller fab company to try

6:30

to increase their capacity and and

6:32

throughput. There's one happening in

6:34

Taiwan. Um,

6:36

but it's going to take a while for us to

6:38

really see the benefits of that. I think

6:41

the thing that might happen first, and I

6:43

could be wrong here, is a

6:47

slowing down of investment in

6:50

um in data centers and the a need for

6:54

RAM. Um I don't see that coming anytime

6:56

soon. I don't personally necessarily see

6:58

a like massive market crash that some

7:01

people are predicting for AI happening

7:04

super soon. uh due to a lot of the

7:06

companies that are really driving this

7:08

forward being hugely profitable

7:11

regardless of AI. Um

7:14

but yeah, I guess that's my like my

7:18

quick thoughts. Quick question. You said

7:21

that DDR5 was designed more for

7:23

enterprise, less for consumer. I have no

7:26

idea what that could possibly mean. Can

7:28

you say a little bit more about that for

7:30

me? Like what does it have like parental

7:32

controls or what? Like

7:34

>> I also just to be fair I think DDR

7:36

stands for Dance Dance Revolution. So

7:38

like that's how much I know about RAM.

7:39

So I'm like I'm very far

7:41

>> number five. Sick. I thought they'd have

7:42

more editions out by now. But that makes

7:44

sense.

7:45

>> It's a very popular game.

7:46

>> It is it is disappointing that they

7:48

don't have more Dance Dance Revolution

7:49

editions. Um no there's a there's a

7:52

really good video from

7:55

sorry um from Wendell from Level One

7:58

Text. if you check out his YouTube

8:00

channel and scroll down a bit because

8:02

it's not very new. Where is it? Hold on.

8:05

Uh, it's not that old either. Um, it's

8:07

it's called your DDR5 memory could be at

8:09

risk. All about DDR5. Um, 20 minutes

8:13

long deep diving what the heck is going

8:15

on with DDR5. I think it's interesting

8:17

that he has that video about issues that

8:21

we're finding especially in the consumer

8:22

space but definitely on the enterprise

8:24

space with with uh DDR5 and also um Lus

8:28

Tvoltz was on our channel not that long

8:30

ago and he was mentioning that he thinks

8:32

a lot of the problems that users have

8:34

with Windows is actually users with bad

8:37

RAM. um which was which was very

8:40

interesting and part of these two

8:42

discussions in my opinion merged

8:44

together because of one of the points

8:46

that come from it being designed

8:49

enterprise first is it's not really

8:51

designed for what most of us have in our

8:54

like desktop chassis. um which is

8:57

honestly not a ton of air flow,

9:00

especially compared to a like server

9:02

environment where you don't care about

9:04

uh fan noise, you don't care about um

9:08

much to be honest. You just want the

9:10

performance and ideally low power draw,

9:12

but that's often a uh an afterthought.

9:15

Um, so a lot of desktop DDR5 is like

9:19

overheating or having various other

9:21

problems and Wendell and some of the

9:23

level one tech forum crew and whatnot

9:25

have designed these like I don't know if

9:28

you were into desktops back in the like

9:31

DDR3 Corsair Dominator era where they

9:34

had those metal fan brackets where you'd

9:36

have those little tiny fans that would

9:38

go over your RAM. Um, well those might

9:40

actually like matter now. Um, and

9:43

they're the the community is making 3D

9:45

printed uh shrouds for their RAM so that

9:48

they can then mount like small I think

9:50

it's 80 mm, but it's been a while since

9:52

I've looked into this. Um, little tiny

9:55

fans and point them directly at the RAM

9:57

up close um to get more air flow on

9:59

there, then they're getting um less

10:02

errors, less problems. Um because if

10:07

if it's doing error correction like on

10:10

the actual stick before it gets to the

10:13

CPU, all that type of stuff, and it's

10:15

overheating, that's not going to perform

10:17

as well, and you might have more issues

10:18

is my like fairly not amazing

10:22

understanding of what's going on in

10:23

there.

10:24

>> So, hold on. I just want to rewind that

10:26

for a second. Mhm.

10:27

>> You were telling me that some of the

10:29

Windows issues I have not

10:31

>> Before you say that though, it's the

10:33

stand up. Can you say we're going to

10:34

circle back on that? That's a little bit

10:36

more work appropriate. We don't rewind

10:39

here.

10:40

>> Please, I don't want to boil the ocean

10:41

right now. Okay.

10:42

>> Okay. Thank you.

10:44

>> But okay, because I I can't my uh my

10:46

ability to maximize Windows decided to

10:49

no longer work anymore. And so that's my

10:51

life as a Windows user right now is the

10:53

ability to only have Windows one size.

10:55

Uh, so that's RAM.

10:57

>> Yeah, that's all that's all RAM. That's

10:59

all RAM.

11:00

>> What?

11:01

>> Probably not RAM.

11:02

>> Yeah, this is crazy. I thought again, I

11:05

thought I was a good programmer. Wind

11:06

>> is just bad. Okay.

11:07

>> Okay. Okay, fair.

11:08

>> There's only so much we can do.

11:10

>> Yeah.

11:11

>> All right.

11:14

>> I do like that though. I I like I like

11:17

Microsoft coming out and saying,

11:18

"Actually, what you guys need is little

11:20

fans on your RAM. that's going to fix

11:24

it out yourself.

11:26

>> Yeah. No, I think it's more like

11:27

crashes, blue screens, um application

11:30

crashes, application errors. If you look

11:32

into stuff in event log and there's like

11:34

things going wrong, uh it might be

11:36

related to that, but it it shouldn't be

11:37

like a a random function not working

11:39

like be able to full screen windows

11:43

>> that obviously.

11:43

>> Have you asked Cortana and or Copilot to

11:47

full screen it? It might work that way

11:48

instead. I actually haven't, but I am

11:51

very curious about doing it. I did have

11:53

>> Please record it. Please record it. I

11:55

need to see I need to see the results.

11:56

>> Yesterday I actually did give my first

11:58

AI swing of like a of of a application

12:01

and uh I noticed that Gemini has been

12:03

added to all Google Chromes and uh

12:05

Windows. So I was like, "Oh my gosh, uh

12:07

I can't log into Frame.io and so I want

12:10

to delete this site's cookies." So I

12:12

clicked on Gemini and said, "Delete this

12:13

site's cookies." And it said, "I can't

12:15

do that." And that was like my that's

12:16

been my only experience thus far,

12:19

>> which is very disappointing.

12:23

>> I just wanted the cookies gone. So then

12:24

I had to go and ask Gemini on uh on

12:28

what's it called on Google. Truly,

12:30

>> it is a futuristic AI then though

12:33

because it's like it is denying your

12:35

requests. That's what the end game is

12:37

for AI, right? So they they achieved it.

12:40

>> They achieved it. Yeah. Lore accurate

12:41

for AI. So

12:43

>> that's funny. Uh, so we are like uh

12:45

we're year one effectively into the the

12:47

great ramming. Uh,

12:49

>> I'm not

12:50

>> That's a Oh my god, that's a great

12:51

title.

12:53

>> Thank you. I just made that up right

12:54

now. But anyways, the great ramming is

12:56

happening right now.

12:57

>> How long do you think this can go before

12:59

RAM prices level out? Because I was

13:01

looking at it and MU and Western

13:03

Digital, which is SSDs, they are up 300%

13:07

in their stock price. So like people are

13:09

obviously pricing in what they think

13:11

this you know this value is going to be

13:14

and it it has not looked like it's

13:16

slowing down at all on the stock market.

13:17

Is this reflective of what RAM prices

13:19

will be? Are we going to see a 3x cost?

13:22

>> Aren't they already pretty much at that?

13:25

>> As per usual, this is not financial

13:26

advice, but

13:28

>> is the stock market predictive of

13:30

anything these days? Um, I mean, you you

13:32

had a good guess with with investing in

13:34

MU early, which is why you own the

13:36

office building you're sitting in right

13:37

now.

13:38

>> Thank you. Thank you.

13:39

>> But but it's like

13:40

>> he's leasing. Okay, Luke, don't don't

13:42

let him get out of

13:43

>> smart with my money. Okay, I lease

13:47

>> commercial real estate's terrible.

13:49

>> Yeah. Yeah. Um,

13:52

yeah. I don't know. I I mean, I think I

13:53

think the demand and price is going to

13:55

be high for a long time. I think that's

13:57

one of the main things that I meant with

13:58

my like little intro thing there. um is

14:01

that I I don't think it's just going to

14:02

randomly come down. Um I think for the

14:06

last few years we've been seeing a

14:09

general all computer hardware shift

14:12

towards enterprise and when you do that

14:14

and and consumer becomes more and more

14:16

of an afterthought, uh consumer gear is

14:18

going to be more price performance

14:21

expensive for what you're getting. Uh we

14:23

saw Intel recently talk about this where

14:25

they're like Intel just openly was like

14:28

you know what we've been giving the

14:29

consumer market like too much attention.

14:31

We're going to focus more on

14:32

hyperscalers. Uh we're we're not

14:35

interested in that anymore. You're

14:36

seeing crucial step out of the market.

14:38

You're seeing Nvidia like

14:40

>> almost like begrudgingly still talk

14:42

about GeForce cards. There's like these

14:44

these companies are are seeing the bag

14:47

that is um working with enterprise. It

14:50

was actually I mean even for me like

14:52

being in the hardware space

14:54

predominantly it was it was fascinating

14:56

not that long ago to find out that like

14:58

a lot of these water cooling companies

15:00

that I thought of as these like scrappy

15:02

little consumer water cooling brands

15:05

sold the vast majority of their revenue

15:08

of products through enterprise doing

15:10

water cooling for servers and data

15:12

centers. Um, it's it's an interesting

15:14

world and there's a lot more money in it

15:16

than like um, you know, uh, us like

15:21

waiting for deals on freaking New Egg or

15:24

whatever. Uh it's it's yeah it's a it's

15:26

a totally different thing when you when

15:28

you're willing to buy like just some

15:30

incredible amount of uh of of money

15:34

worth of like if I don't know some of

15:36

these reservations for even during coin

15:39

mining some of these massive operations

15:42

were buying pallets and pallets and

15:44

pallets of GPUs and if they had issues

15:46

with them kind of like almost shrugging

15:48

it off. Um, whereas consumers, like, you

15:51

know, if you have an issue with it,

15:52

there's a there's a Reddit thread with

15:54

7,000 upvotes and you're screaming from

15:56

the mountains and all this kind of

15:57

stuff. Like, why why deal with us

15:59

annoying low people who lack money uh

16:03

when you can deal with the the

16:04

hyperscaler

16:06

boys with all of the money and and less

16:08

of the problems. Yeah. You know, it's

16:11

funny you should say that because if you

16:12

have looked at OpenAI's kind of oraoris

16:14

investing, uh, Nvidia has promised

16:17

they're going to pay them a progressive

16:18

amount up to one or hundred billion

16:20

dollars and OpenAI's apparently one of

16:23

their agreements. I was really trying

16:24

confused trying to find out the exact

16:26

number and the only number I found was

16:28

they're going to pay them back 10

16:29

gawatts worth of purchases. And I was

16:32

like, I don't know what that number

16:33

means cuz typically I use USD. I'm not

16:36

used to whatever this AI money currency

16:38

is. But a gigawatt appar again this is

16:40

Chad GPTI ask like what the hell's a

16:42

gigawatt what the hell's a gigawatt and

16:44

it said one nuclear power plant worth of

16:46

energy. So I was just like oh my gosh

16:48

that's how much they're going to be

16:50

buying is 10 nuclear power plants and

16:52

then I was like did they make this deal

16:53

elsewhere and then apparently with

16:55

Oracle their 300 billion will also

16:57

result in 6 gawatt of data center or six

17:00

nuclear and I like 16 nuclear power like

17:03

that's first off that sounds like a

17:04

metal band. Second off, the United

17:06

States has 39 total. Like that's half

17:08

that's like 50% of the entire power grid

17:10

worth of

17:12

>> new nuclear power plants. And I'm

17:13

probably not even saying nuclear.

17:14

Correct.

17:15

>> So

17:16

>> it's nuclear.

17:17

>> Nuclear.

17:18

>> It's nuclear.

17:19

>> Nuclear power. Yeah.

17:20

>> Nuclear.

17:21

>> Nuclear power.

17:22

>> Nucleular.

17:24

>> Nuclear.

17:25

>> There's a lot of

17:26

>> nuclear. Yeah.

17:27

>> I don't know if you want me to inject

17:28

some random technical stuff in here or

17:30

not. Yes, please. Certainly can. Okay.

17:32

So, I don't study any of this stuff.

17:35

Like, hardware is definitely not my

17:37

monkeys and not my zoo. I just look at

17:40

it and go like, look, the worse the

17:41

hardware is, the better is for people

17:43

like me who like to talk about

17:44

programming performance because it just

17:46

means you have to be better, right? So,

17:48

I'm fine with like go great. If there's

17:49

a if you have to start programming for a

17:51

10-year-old laptop, I'm happy about

17:54

that. But

17:56

>> yeah, actually a typical data center, my

17:59

understanding is that you're in the like

18:01

100 to 200 megawatt range for the data

18:04

center. Like like a typical modern data

18:07

center, that's what you would be looking

18:09

at for the total number of megawws.

18:12

Whereas AI data centers are like 10x

18:14

that for power consumption. So when

18:16

they're building those, they're looking

18:17

at things like gigawatt or, you know,

18:20

mult mult like up to over one gawatt

18:24

worth of inflow of power to this data

18:27

center, right? That's how much it

18:28

consumes. So when they talk about

18:30

gigawatts, they're literally talking

18:31

about like, okay, 10 gigawatts might be

18:35

five data centers or something like

18:36

that. Five new data center buildouts

18:39

worth or something like this, right? if

18:40

I'm just like ballparking those numbers

18:43

based on what I've seen. Uh so when you

18:47

think about that when they're

18:48

guaranteeing that kind of purchase, I

18:50

mean that's an ungodly number of GPUs,

18:52

right? You know, think think literally

18:54

five data centers or something or more

18:57

worth of these racks upon racks of

18:59

Nvidia Rubin like you know slotted

19:02

things or whatever you know they're on

19:03

at that point.

19:05

And so that's just I mean I don't know

19:08

we'd have to go break out a calculator

19:10

to even try to figure out what kind of a

19:12

outlay that is for Nvidia but it's

19:13

massive right like it's a massive

19:15

amount.

19:17

Um tying that back though to the thing

19:19

we're actually talking about which is

19:21

memory. My understanding was that OpenAI

19:23

actually signed some kind of nutso deal

19:26

where they were going to buy up to

19:29

900,000

19:30

wafers a month of DDR memory. What's a

19:35

wafer and how much memory's on a wave?

19:39

>> Uh, that's a Okay, so again,

19:42

>> not my monkeys, not my zoo. I'm doing my

19:45

best.

19:45

>> It's classified prime. It's classified.

19:47

>> And

19:50

it is if you actually want to know the

19:54

the yield per wafer,

19:56

>> like they have the number of like bits

19:57

per wafer. These are things you pay

19:59

analyst firms to get and they very they

20:02

they are constantly moving around

20:04

because people are trying to increase

20:05

their yield and so on.

20:07

>> A wafer is a piece of silicon. It's

20:10

circular. You've seen them.

20:11

>> Is that the circular one that we talk

20:13

about?

20:14

>> Yep.

20:15

>> So they're just buying circles.

20:17

>> Yep.

20:19

>> They're buying the output of the

20:21

circles.

20:21

>> Yeah.

20:22

>> Okay. I was about to say I don't know

20:23

how to take a circle and turn it into a

20:25

stick. Like that's very difficult.

20:26

Casey, I've never seen a GPU that's

20:28

round. So, I don't know if I believe

20:30

this.

20:31

>> Well, there are some uh the the uh

20:33

there's people who make wafer who make

20:35

wafer scale. They're kind of prototypes,

20:37

but they make wafer scale AI

20:38

accelerators, and they are circular.

20:40

>> That's pretty cool.

20:41

>> Yeah. But that's just nutso stuff. I

20:44

mean, I don't

20:44

>> They're designed after Sam Alman's orb.

20:46

>> Yeah.

20:46

>> So, it's like it's circular.

20:48

>> You can only do it.

20:50

>> I think technically uh technically

20:52

Prime, you're more right. You were

20:54

trying to make a joke, but you're more

20:55

right than you think you are. I believe

20:57

the Open AI deal is literally for uncut

21:01

wafers. They have been patterned, but

21:04

they are uncut and they are going to be

21:08

like controlling where that gets shipped

21:10

to and how it ends up getting stacked

21:12

and packaged was like the last time I

21:15

read it, they were uncut patterned

21:18

wafers, not cut and packaged, which is

21:20

very unusual. I could be wrong, but

21:22

don't say it. My recollection.

21:24

>> No, it sounds like you're right. I

21:25

didn't actually realize.

21:26

>> I believe I am. Yeah. Yeah.

21:28

>> I'm thinking about a Sam Alman as

21:30

Scarface right now.

21:31

>> Yep.

21:33

>> Just uncut wafers all over his desk.

21:38

>> Um, so

21:39

>> again to give a really bad explanation

21:41

because I'm the wrong guy to give this

21:42

expl you really want to get like, you

21:44

know, uh, Dev Patel.

21:46

>> What about the guy's name for Dylan

21:48

Patel? Dylan Patel from um semi analysis

21:52

or something. You want to get him, he

21:53

would know, right?

21:54

>> It depends. Yeah. Like we're we're more

21:56

on the consumer side of things. Like I

21:57

don't I don't get way into this too

21:59

often. I do know that like the the

22:01

difficult part is making the wafer. Um

22:04

like there's there's somebody online who

22:06

made their own stick of of computer

22:09

memory um using using chips they got

22:13

from you know somebody else. Um, so it's

22:16

not like it's not crazy surprising that

22:19

they bought just the wafers. I just

22:21

thought they would, you know, cut to the

22:23

chase and get them to actually hand them

22:25

over like functioning sticks, but um,

22:28

>> well, they're not sticks is the problem,

22:29

right? Because they are using HBM. So,

22:32

>> Oh, right. Yeah. I mean,

22:33

>> what happens? Yeah. So,

22:35

>> for us normies,

22:36

>> okay, so, uh,

22:40

>> this is again way out of my league. and

22:42

I both have to guess what bandwidth for.

22:44

>> Yeah. So, what it is,

22:46

>> okay,

22:46

>> what it is is like if you think about

22:48

normally how memory works, right, it's

22:50

it's on a stick and you basically have

22:52

these the the individual DRAM chips that

22:55

have been fabricated are like on a line

22:57

of the chip and then the the like, you

22:59

know, the connection is the you know the

23:02

little pins it slots in and that's how

23:04

it's talking to CPU. So, if you think

23:06

about it, you've got like essentially

23:08

the CPU is on a package, the DDR is on a

23:12

package on a little thing. You've got

23:14

those connections. They go through the

23:16

PCB, right, your motherboard. And

23:19

there's like some small number of

23:21

connections connecting them, right? So,

23:23

that there's like traces on the PCB that

23:26

are going to drive over to those like,

23:27

you know, places you slot them in. So

23:31

GDDDR,

23:33

right, which is the graphics graphics

23:36

DDR, not the kind you slot into your

23:38

thing, right? So the kind that goes on a

23:40

on a on a GPU

23:42

is a little bit different. That one is

23:45

like welded right on like it's like

23:48

soldered onto the motherboard and

23:49

directly connected. And the re and

23:51

closer and the reason for that is they

23:54

it's basically the same kind of memory

23:56

for all intents and purposes as far as I

23:59

know but the signaling is much much

24:02

faster. So they they drive the data rate

24:05

up the the band total bandwidth they

24:07

drive up by increasing the speed at

24:10

which it can transfer things back and

24:12

forth. And so it has like basically

24:14

higher quality sign physical signaling

24:17

to get things back and forth. But

24:18

otherwise, same basic idea as the kind

24:21

you would slot

24:22

>> into your motherboard. Otherwise, not a

24:24

huge difference. Beyond that,

24:26

>> some people were asking for visual

24:28

representation. And if you if you look

24:30

up if you if you wiki I don't know if I

24:32

can share my screen on this thing, but

24:34

uh if you wiki high bandwidth memory,

24:36

there is a very good photo if you scroll

24:39

down to the interface section um that

24:41

shows how it's like 3D stacked as well.

24:44

Um so you can

24:45

>> Well, we haven't gotten HBM yet.

24:47

>> Okay. totally different than both of

24:49

these. Totally different than these two

24:51

things.

24:52

>> So HBM is completely different from

24:55

those two things.

24:56

>> Completely different.

24:58

>> It's the same sort of memory. Like it's

25:01

still the idea is still that there's a

25:04

capacitor and a transistor per cell of

25:06

memory. Like so the actual thing you're

25:08

fabbing is somewhat similar, but it's

25:11

very different in two very important

25:12

ways. One, like Luke just said, it's

25:15

stacked. And in order to stack it, it

25:18

needs to be uh manufactured with this

25:20

sort of different kind of uh

25:22

connectivity. It's got these things

25:24

called TSVs or through silicon VAS.

25:26

They're like these connections that go

25:29

through the stacks so that you can kind

25:31

of like have each stack is talking to

25:32

the next stack. It like and and they

25:34

tunnel through, right? So it's wider,

25:38

right? It's a wider. It's like the

25:40

actual physical footprint for the same

25:42

amount of memory is a little bit bigger

25:44

because it's got to have space for this.

25:46

The normal DRM can be doesn't have to

25:49

have those, right? Those TSVs. So,

25:52

that's a thing. But the much bigger

25:54

thing, I mean, although that's that's uh

25:57

obviously a slight difference there, the

25:59

much bigger thing is the stacking and

26:02

packaging is just a way harder problem.

26:05

So, first you have to be able to stack

26:08

them and this reduces yield apparently

26:11

for I don't know the reasons why but

26:13

like

26:13

>> again can you explain yield?

26:16

>> I I forget just like a quick like

26:18

oneliner. Why do you not like

26:20

>> percentage of stuff coming out based on

26:22

what you put in?

26:23

>> Like just because some of it's bad. It

26:25

just comes out like broken. So they're

26:27

just like this wafer is broken, bro.

26:29

>> We're different levels quality.

26:31

>> Yeah.

26:31

>> Yeah. Computer chip small hard to make.

26:34

We mess up times sometimes bad. That's

26:38

>> okay. Okay. Okay.

26:39

>> The answer is that's what I needed.

26:41

That's what I needed. Okay. Thank you.

26:42

>> The answer is I don't know. Normally

26:45

when we talk about yield, I understood

26:46

it fairly well from the old like what's

26:49

the yield on a wafer? Cuz you figure you

26:51

make a wafer, there are defects on the

26:53

wafer. So you you know, you imagine

26:54

you're patterning this thing and you've

26:56

got defects. some of the defects or

26:58

maybe could be, you know, some kind of

27:00

impurity or something went wrong or

27:02

maybe when you were patterning the light

27:04

just hit something or there was one

27:05

little speck of dust in there or

27:06

whatever. So, you have certain things

27:09

that didn't quite work as well as they

27:11

should on this wafer. And so, some

27:14

number of the things that you put on the

27:16

wafer aren't are just going to fail. And

27:18

so normally when you talk about yield,

27:21

you talk about like all right, if

27:23

there's n number of defects on a wafer,

27:26

we expect those to fall fairly randomly.

27:28

Sometimes they're they're distributed

27:30

differently like more towards the

27:31

outside than the center because of the

27:33

way the reticles work or all these other

27:34

sorts of things. Who knows? But so you

27:37

only get a certain number of those

27:38

chips, right? Only a certain number of

27:40

them will work or a certain number of

27:42

them will perform better than others for

27:44

certain reasons. All those sorts of

27:46

things. And all that goes into what you

27:48

call your yield, right? And bin. So bin

27:51

is right the process where you say like

27:53

some of these chips work better than

27:54

others for whatever reasons, run at

27:56

higher clock rates, things like that.

27:58

Others are like they literally don't

28:00

work. There's a defect on them. We can't

28:02

get it working at all. And yet others

28:04

are designed to like have certain things

28:07

constructively turned off. think GPU

28:09

where it's like okay there's this many

28:12

processing units on the GPU and they're

28:14

designed to have some of those fail and

28:16

be turned off right so it's like okay

28:18

this just has less cores now and it gets

28:20

slotted as a different thing blah blah

28:22

blah that's the normal way that like I

28:26

have heard yield talked about for this

28:30

apparently when you you have to like

28:32

grind down the silicon and like stack it

28:34

on top of each other and all the and I

28:36

guess there's a separate yield loss that

28:39

happens. It has nothing to do with

28:41

whether the original chips were working

28:43

or not, maybe. But then there's also the

28:46

fact that I got the sense when I tried

28:48

to look at this stuff cuz um I knew we

28:50

were doing this podcast. So, I was like,

28:51

"Let me go see like what what are they

28:53

talking about with some of these memory

28:55

things?" And I wasn't really able to

28:57

understand it because I wasn't sure if

28:59

what they were talking about was yield

29:01

loss from we stack these wafers on top

29:04

of each other and that process produces

29:07

problems or if what they were talking

29:09

about is we can't test the memory prior

29:13

to the stacking for some reason. Let's

29:15

say I'm making that up. I don't know.

29:18

And so when we stack eight things on top

29:20

of each other, we just multiplied our

29:22

total failure rate by eight because if

29:24

one of them's bad, they're all bad,

29:26

right? Because the VAS won't work or who

29:28

knows what. So I don't know which of

29:30

those are talking about, but what I've

29:31

seen put out for numbers is when you're

29:34

making one of these HBM modules, your

29:38

your yield rate is awful compared to

29:41

normal. They said three times as much

29:44

wafer space is required for the same

29:47

amount of HBM memory as for regular DDR5

29:51

or something like that. So the same

29:54

number of bits stored if you're storing

29:56

them in HBM, you required three times

29:59

the input wafer size and patterning to

30:01

get that out. And that's a huge yield.

30:04

Like that's massive, right? I mean just

30:07

think about that number. It means you're

30:09

doing all the same work, but you end up

30:11

with three times more chips for DDR5 if

30:15

you were producing the R5 as if you did

30:17

HBM.

30:18

Make sense?

30:19

>> Okay, that does make sense. So, that

30:22

sucks, right? That that is really really

30:24

bad. And it means that the price of

30:26

those things has to be much higher

30:28

because you're doing a ton more work for

30:30

each one. You're doing three times more

30:32

work to get the same amount of bit

30:34

storage. So if you want a gigabyte of

30:37

HBM versus a gigabyte of just the random

30:40

GDR or DDR that we're sticking in the

30:42

computer,

30:43

>> it's it's right.

30:45

>> Sorry just am. Okay,

30:47

>> just to finish this ridiculous tangent

30:49

on how it works.

30:50

>> So the thing about HBM is what I tried

30:53

to get to at the the beginning before we

30:55

went into that yield thing is it doesn't

30:58

go outside the chip. It's not connected

31:01

to the chip in this sort of way that we

31:04

think of like with GDDR that's like SL

31:06

on the PCB or DRM which is slotted in.

31:09

It's on the package. So the way that it

31:12

works is you literally, you know, you

31:14

think about I don't know if you guys

31:15

have ever seen like die shots of

31:17

something like a modern AMD processor

31:18

where there's chiplets. There's like

31:20

little chiplets in there. So it's like

31:22

you delid the processor. There's like

31:23

two, you know, CPU dyes and something on

31:26

there, right?

31:28

That's how HBM works. It's on the

31:31

package. So, the CPU and the memory are

31:33

all together in one module. They're not

31:36

out. They don't they're not things you

31:37

plug in or put on a PCB. Does that make

31:40

sense? Is this uh like

31:44

>> this could be way off, but some of the

31:46

stuff with like Mac minis and all these

31:48

some of the new Mac stuff where they

31:49

have like the unified memory, which is

31:51

why a bunch of people are using them for

31:53

running local LLM stuff because they

31:55

have this higher bandwidth connection to

31:57

CPU that actually lets you run like

32:00

local models at reasonable speeds. Is is

32:02

this related at all? I don't know.

32:04

>> I'm just asking.

32:05

>> I am not sure. I I want to say that

32:09

there may be I thought there was a uh

32:13

>> I'm not I'm not sure. I don't want to

32:14

say because I'm not sure about that. I

32:16

know that there's uh there are some like

32:18

A series uh chips I think that use on

32:21

chip memory which is very different and

32:24

super duper duper fast, way faster than

32:26

even HBM. Um but that's a different

32:29

thing which we could go into later but

32:31

it's not relevant to a DRM shortage at

32:32

all.

32:33

>> Yeah.

32:35

>> Yeah. They're they're expanding cash in

32:37

in a lot of ways, but like you said,

32:39

that's not really related.

32:41

>> Yeah, it's a different type of it's a

32:42

completely different it's it's SRAM.

32:44

It's not even the same kind of

32:46

>> Can I Can I ask a dumb question?

32:49

>> Yes, please.

32:50

>> I have been asking dumb questions the

32:51

entire time because this stuff, like I

32:52

said, not my monkeys, not my zoo. And

32:54

you look into it and you're like, Jesus

32:55

Christ. Like it's just like this huge

32:57

morass of stuff where you're like, oh

32:59

god. Okay,

33:00

>> so

33:01

>> me the consumer, I don't just want a

33:04

wafer. I want it like nicely packaged

33:06

and then have like little LEDs on top of

33:08

it. And then I want NZXT or something

33:12

LEDs.

33:13

>> You're not an LED. Come on.

33:15

>> Dude, I have LEDs right now, baby, with

33:17

my with my little rings.

33:18

>> Oh, no.

33:19

>> Just like, you know, the whole nine

33:20

yards, right? And that's me as a

33:22

consumer. So, why in the world as a

33:26

producer would I ever sell to consumers

33:29

ever for any reason if Samuel Jippity

33:31

Alman is just like, "Give me the

33:33

circles. I don't even want like I don't

33:36

even want you to put LEDs on them. I

33:38

just want I just want the circles.

33:40

>> And

33:40

>> that's the that's that's the short. You

33:42

just described the shortage. Yes.

33:44

>> Yeah. That's what's happening, right?

33:46

You nailed it, Prime.

33:47

>> Good job.

33:48

>> Very done.

33:50

>> Episode's over. We can all go home. So,

33:52

we're like literally never

33:53

>> crucial was the the consumer,

33:55

specifically consumer side of Micron.

33:59

And they were just like, "Yeah, screw

34:00

it. Why do I want to deal with you guys?

34:02

I can just sell to the to the

34:03

hyperscalers. Um there is if you look at

34:05

the amount of companies that are

34:07

actually making wafers um versus the

34:10

amount of companies that are selling in

34:12

in you know the most consumer side of

34:14

things, the sticks of RAM. There's an

34:17

incredible amount of companies selling

34:18

sticks of RAM. Uh there are very very

34:21

very few actually making wafers. Um the

34:24

the hard part is the the making of the

34:27

wafers, not the making of the sticks. um

34:30

or in the in the HBM sense, uh it

34:33

continues to be hard the whole way

34:34

through. Um we're we're we're

34:36

specifically talking in this case about

34:38

about the sticks. You were talking about

34:39

putting LEDs. You're not putting LEDs on

34:41

HBM. Um so I'm I'm talking about sticks,

34:44

but

34:44

>> they're missing out.

34:45

>> They're missing it out. Data center

34:48

them things that like, you know,

34:50

primarily coolers that go on top of of

34:53

HBM or something like that. But uh

34:55

that's probably what you might see. But

34:57

>> when Razer gets into the HBM market and

35:00

there we go.

35:02

>> I'm I'm imagining

35:04

>> when I get my CHBT subscription, there's

35:07

an additional tier and I get like a live

35:09

video feed into the data center and I

35:11

have like my rack and it has my cool

35:14

LEDs on it for an additional price. Like

35:16

they're missing out on these secondary

35:18

effects that they could be selling, you

35:20

know?

35:20

>> I like that. Yeah. So that means the,

35:23

you know, the AI future always shows

35:24

these data centers that are like glowing

35:26

with bright lights. So Sam's not going

35:28

for that style of LED future. He's going

35:31

for like the dark scary one.

35:34

>> Yeah. Yeah.

35:35

>> Okay. And we don't need light where

35:36

we're going. Okay. That's pretty

35:37

interesting. So does this is there is

35:39

there any computer part that's protected

35:41

from this AI revolution? Like is there

35:44

anything that's going to remain normal

35:45

priced or am I just screwed? Because I

35:47

have to buy a new computer here soon.

35:48

Um, I don't I should probably buy it

35:51

sooner than later. Is it It seems like

35:53

But also, is there like anything that's

35:54

going to be cheap or is it all Is it all

35:57

gone?

35:59

>> Well, I mean, one kind of sort of nice

36:02

thing is that the whole RAM situation is

36:06

sort of creating this nice bottleneck.

36:09

So it's unclear like

36:12

it's unclear how much CPU prices would

36:14

be affected long term because TSMC so

36:17

TSMC okay so there is a way in which the

36:23

production capacity for things like CPUs

36:27

is implicated by this but I don't fully

36:31

know how to what extent so when you do

36:35

these HBM modules the stack that stack

36:38

stack that we were talking about. The

36:40

bottom of that stack is not memory. So

36:44

the things that are like up the whole

36:46

way, that's memory, but the bottom is

36:49

actually a logic die. So it's kind of

36:51

like one logic layer and then a bunch of

36:53

like memory cell layers. And that bottom

36:57

die supposedly is actually like advanced

37:03

process logic process. So, my

37:05

understanding is that TSMC actually is

37:08

going to be fabbing a lot of like the

37:11

for HBM4 or something. They're actually

37:15

going to be fabbing the bottom layer.

37:17

So, it's like TSMC fabs the bottom layer

37:20

of the stack. SKH Highex, Micron, and

37:23

Samsung, if their stuff ever works, will

37:25

be fabbing the other layers, and then

37:28

they get like packaged together and then

37:31

stuck on the the, you know, chip, the

37:33

the wafer, the COS

37:37

packaging thing or whatever they're

37:38

going to be using at that point. And so

37:41

I suppose that could have some negative

37:44

consequences and that that adds more

37:45

stress to the TSMC side, but I don't

37:47

know like to what extent that competes

37:49

with things like you know the logic dice

37:52

for CPUs and stuff. So it seems like if

37:54

you're sitting around waiting for memory

37:56

all the time because you're memory

37:57

supply constrained then that would mean

38:00

that like the the fab processes that are

38:03

used for CPU and GPU dies that aren't

38:06

the parts that aren't the memory. That

38:08

part seems like it wouldn't necessarily

38:10

go up, right? Cuz they're they just have

38:12

extra capacity at that point because you

38:14

can't make new accelerators without the

38:15

memory and you need a lot of that memory

38:17

and they just don't have the fabulous.

38:19

So that could be someone out there has

38:22

done that analysis but I again it's

38:23

probably something you have to pay for

38:24

the research.

38:25

>> Yeah, there's a lot of analysts. I think

38:27

like theoretically pretty much

38:29

everything could be impacted to a

38:31

certain degree. Like if we're if we're

38:32

building all this stuff, basically

38:35

everything in a consumer computer, those

38:37

brands, a lot of them, not all of them,

38:39

uh are are also in the hyperscaler

38:42

space. But the amount of impact on like

38:45

a company that makes uh you know, server

38:49

chassis and desktop computer cases is

38:52

going to be effectively nothing because

38:53

you can scale that up no problem. Um,

38:56

and there's a lot of potential

38:57

manufacturing in that space. So, it's

38:59

just kind of whatever. Um, the amount of

39:02

things impacted is going to be like a a

39:05

computer fan, for example. Uh, they

39:07

might have lots of fans, but who cares?

39:09

You can make tons of fans all the time

39:11

basically everywhere. There's there's

39:12

there's not really going to be any

39:14

actual real impact there. Um, so it'll

39:17

it'll probably stay mostly with um, you

39:21

know, the things on or attached to or

39:24

very close to the board. Um, which is

39:27

mostly impact that we've already seen.

39:28

But I I do agree. I think it's

39:30

bottlenecked.

39:34

Casey, so are you saying since we have

39:37

to pay a lot of money for memory and our

39:38

CPUs are just going to be waiting all

39:40

the time, JavaScript is so back. Is that

39:42

like CPU doesn't even matter? We're just

39:44

waiting around.

39:46

We're just waiting around. It doesn't

39:47

even matter how long it takes anymore.

39:49

It's just chilling out in memory.

39:50

>> Or other way around. You'll only be able

39:52

to like new machines will only have 512

39:55

megabytes of memory cuz that's all

39:56

you'll be able to afford. Like each year

39:58

the memory will go down and down and

40:00

down until eventually you're running

40:01

like the Commodore 64 is like roughly

40:04

what you get. You 64K. That's all you

40:07

you know you plebs can afford.

40:08

>> I've trained normies are not allowed to

40:10

use graphical gigabyte. You don't get a

40:14

gigabyte of memory. What are you

40:15

talking? What are you? You think you're,

40:16

you know, some kind of uh the president

40:19

or something? You don't get a gigabyte.

40:22

>> Maybe uh maybe Bill Gates's old fake

40:24

quote was actually right, but it wasn't

40:25

right because it's most of what we need.

40:27

It'll be right because it's most what we

40:28

can actually get.

40:29

>> Yeah. It's like that's what you get.

40:30

>> I like this.

40:31

>> 640K will be enough

40:34

>> for anybody because it is all you will

40:37

get. Yeah. Yeah.

40:38

>> All right. So, the final question,

40:39

>> own almost nothing and be happy.

40:44

All right. So, the followup question I

40:45

think is um is pretty interesting

40:47

because uh Google Stadia obviously they

40:49

they killed Google Stadia. Uh Netflix

40:52

actually went into this whole idea of

40:54

doing um games on the server and they're

40:57

they're doing it quite successfully. Uh

40:59

a lot of these places it kind of seems

41:01

like we're moving more and more to the

41:03

server. Uh does this mean that within

41:05

the next 5 years we could see something

41:08

along the lines where consumers are

41:10

getting so priced out that it's better

41:12

just to rent uh your workstation. It's

41:15

better just to rent your time on some

41:17

sort of server computer cuz I know

41:18

there's a lot of this being pushed with

41:19

like VS Code and GitHub and everything

41:21

where you can just you rent out your

41:23

development environment as opposed to

41:25

you actually owning your development

41:26

environment. You're just like I can

41:27

program anywhere now on any you know I

41:29

just need a terminal and boom you're up

41:31

and running. And so, um, is this like a

41:34

future that we're kind of forcing people

41:35

into being like, "Oh, you want a

41:36

computer, brother? That's $20,000. Like,

41:39

you you better just go rent one for

41:41

life."

41:43

>> I think there's some desire there from a

41:45

variety of companies. But I I think when

41:47

we're looking at um at least some of the

41:50

comms that I'm seeing from these like

41:53

RAM wafer companies and stuff like that

41:55

is that they they want to scale up

41:57

because of this, like they would like

41:58

both markets. Um I but I don't know. I

42:03

mean there's a there's a Twitch chatter

42:05

mentioning Chinese manufacturers

42:06

covering to the the memory market. Like

42:08

there we might also start seeing

42:10

competition like that. Um I wouldn't be

42:14

too surprised if the gap between what

42:16

the enterprise has available to them and

42:18

what the consumers have available to

42:20

them or at least what the consumers

42:22

reasonably have available to them

42:24

continues widening. um for for a while

42:28

there the unless you're looking at like

42:31

what was that the name of that CPU like

42:32

knights able or whatever um unless

42:35

you're looking at like the extreme end

42:37

of of server specific compute hardware

42:40

uh consumers were pretty interested in

42:42

that stuff for a long time and now we

42:43

have GPUs that are just mind-blowingly

42:46

expensive and CPUs that are

42:47

mind-blowingly expensive on the extreme

42:49

high end um that just in a lot of cases

42:53

while those things are relevant isn't

42:55

going to be super necessary on the

42:57

consumer side of things. Um, so

43:01

yeah, I I don't think that's necessarily

43:03

going to happen because

43:05

there will always be a section of the

43:07

market where someone could make money

43:09

selling to those people. Um, and I think

43:11

the the Chinese who are both getting

43:13

into CPU, not both, but uh all getting

43:16

into CPU, memory, GPU, all that type of

43:18

stuff, uh, they might come for that

43:20

market. Someone else might, not sure.

43:22

But yeah, I don't I don't think that's

43:23

going to happen.

43:24

CXMT is supposedly not far behind modern

43:28

memory standards like right now. Um, and

43:32

so they're kind of predicted to be able

43:34

to ship at least like DDR4.

43:36

>> Yes.

43:36

>> Style memory, right? Or something like

43:38

this. So they're they're not

43:40

>> Chinese memory manufacturers aren't like

43:43

way behind. And so it's very possible

43:46

that especially if you start talking

43:48

about well you know no one can afford

43:49

DDR5 so you know maybe you could ship a

43:52

cheaper thing uh or a less good thing

43:54

and that would be fine right

43:56

>> and maybe you're you're you're not able

43:58

to buy as high performant computers or

44:00

relatively as now or whatever but maybe

44:02

Casey's stuff gets more popular and

44:05

programming goes more more uh you know

44:07

efficiency and performance and stuff

44:09

like that we start making Roller Coaster

44:10

Tycoon again.

44:11

>> Yeah.

44:11

>> Um

44:12

>> there we go. Yeah,

44:14

>> it really consumer desktop is just like

44:16

gone. Uh or consumer compute, I should

44:19

say.

44:21

>> I was going to say it's actually really

44:22

uh this this whole kind of crunch on

44:24

everything and and not being able to buy

44:26

the next greatest MacBook uh MacBook Pro

44:29

every single six months from the Silicon

44:30

Valley. Uh it is actually kind of a

44:32

positive thing because people might

44:33

actually start experiencing the uh the

44:35

crap they make on devices that aren't

44:37

the premium of the premium. followup

44:38

question, which is will when do you

44:41

think or do you think this is going to

44:42

hit phones soon? Because I kind of

44:44

realize like people buy phones fairly

44:46

frequently in America.

44:47

>> Mhm. Like at what point does Verizon

44:50

say, "Yeah, sorry. We're not giving you

44:52

a phone with a 2-year contract anymore.

44:54

It's just like too damn expensive now."

44:56

Like is there is there a world where

44:57

this is coming soon? Because I assume

44:59

all those parts are equally susceptible

45:01

to whatever is happening. The rammoning.

45:05

Yeah,

45:06

>> it would make sense that it would. Um, I

45:08

haven't really seen it happen yet. Uh,

45:10

you you've seen it a lot of other

45:11

worlds. I don't know if that's because

45:13

like they have contracts far enough out

45:16

that it hasn't really impacted their

45:17

their available stock at this time. Um,

45:20

so I I don't know when that would

45:22

happen, but it it Yeah, it would

45:24

absolutely make sense to me that it

45:25

would.

45:26

There's also like supposedly and this is

45:29

kind of I I don't know to what extent

45:32

they're talking about this but I guess

45:34

the AI buildout doesn't only affect DRAM

45:38

it also affects like NAND flash storage

45:41

and things like this like apparently

45:43

like you know these machines that

45:45

they're prepping I don't know what a

45:46

typical AI data center machine looks

45:48

like but it's not like oh it just has

45:50

high bandwidth memory it also has DDR5

45:54

regular And it also has nan flash like

45:57

SSD. So they're taking capacity for all

46:01

of those things. And I think the memory

46:04

side is what we talk about probably most

46:06

because that HBM stuff has such the bad

46:10

yield stuff and all that. So probably

46:11

like that hit first. But the other qu

46:13

the other sort of storage technologies

46:16

are also just facing limited supply for

46:19

the same reason. Like AI just wants to

46:21

buy a lot of it and there weren't enough

46:23

people. there wasn't enough slack like

46:26

to pick that up. So, I would imagine

46:28

that phones will have all of these same

46:30

problems. Like they'll in a year or two

46:33

when their pre, you know, when their

46:35

aotments have run out, uh, they will be

46:39

like, "Oh crap." Like the flash storage

46:41

is more expensive. The memory is more

46:43

expensive. About the only thing that

46:45

won't get more expensive probably is

46:46

that SRAMM part that's on chip memory

46:50

like in a in a Bionic like in a um Apple

46:54

A series chip or whatever, right? Um but

46:56

they, you know, that's just part of

46:58

their memory architect. They still have

46:59

the other parts, so they're still going

47:00

to have problems with that.

47:02

>> Yeah.

47:03

>> The Western Digital, uh, which does a

47:05

lot of, I assume that Nan Flash, they're

47:07

also up just an absurd amount in the

47:09

last 6 months, they're up 300 plus

47:11

percent. Uh, just today they're up over

47:13

10%. Like they're obvious they're

47:14

actually they actually have risen faster

47:16

than Micron as far as

47:17

>> That was because of the podcast, by the

47:19

way.

47:20

>> Huh.

47:20

>> That's because of the podcast, by the

47:22

way.

47:24

>> We got the motion. Uh, all right. Well,

47:27

I mean, I this could be a good time to

47:30

kind of jump off some of the hardware

47:31

stuff, unless if Luke, you have anything

47:33

else you want to talk about because I I

47:34

I do have some questions about YouTube

47:36

and tech and all that kind of stuff for

47:37

you as well.

47:39

>> Can I make two stupid jokes before we go

47:40

to the next one? Because I had some, but

47:42

I just didn't get a chance to put them

47:43

in. People were saying smart things.

47:45

When we were talking about yield, I

47:47

really wanted to ask Luke what his

47:48

thoughts were about roundabouts.

47:51

>> That's pretty good. Cuz you have to

47:53

>> Oh, round. I like roundabouts.

47:55

>> Okay, cool. Nice.

47:56

>> That didn't That didn't go as well as I

47:58

thought.

47:58

>> You don't have to yield. You don't have

47:59

to

47:59

>> yield. You have to yield at them instead

48:01

of stop. That's

48:02

>> I mean, if you're just confident enough,

48:04

you don't

48:04

>> No, I like I love roundabouts.

48:06

Personally, that's a great point.

48:08

Self-driving cars, baby. They just all

48:10

They just do the thing. It's fine.

48:12

>> In my experience, people stop for me.

48:17

>> It's done.

48:18

>> That's just cuz you put the LTT thing on

48:19

the side and it's coming through.

48:22

Yeah. Yeah.

48:22

>> I wasn't going to be able to focus for

48:24

the rest of the episode. Okay. It was

48:25

just in my head the roundabout joke

48:27

mostly. So, you had to be there.

48:29

>> Yeah.

48:30

>> Yeah.

48:31

Had to be there. Well, looks like we all

48:33

got to be there. That was very

48:34

fantastic. Thanks.

48:35

>> Brian, ask your next question. That'd be

48:37

sweet.

48:38

>> All right. All right. we should shift a

48:40

little bit of gears and talk more about

48:41

kind of uh LT cuz you you guys obviously

48:44

have uh some developers on board and all

48:46

that and you're doing I assume the tech

48:49

and the things that you're building is

48:51

much different experience than say

48:52

something like Netflix where they've

48:54

just been working on one product and

48:55

ancillary products for 20 years or

48:57

Google 20 right like all these companies

48:59

have been just working on the thing

49:00

they're doing well Google kills a bunch

49:01

of projects too but imagine a company

49:03

that doesn't kill a bunch of things

49:04

they've been doing one thing and that's

49:06

it uh I kind of like even though AI's

49:09

had a uh there's a lot of negative

49:11

impacts to things. How has it impacted

49:13

kind of this hiring what work looks

49:16

like? Do you guys feel like you're doing

49:17

more things? Like the positives, the

49:19

negatives? I'm I'm curious.

49:21

>> I don't feel like it's changed like

49:25

I don't know. Hiring has gotten really

49:27

weird. Um hiring has gotten extremely

49:29

strange. Uh, I mean, being like as

49:34

public as we are, I guess, um, the

49:37

hiring has always been a little bit odd.

49:39

Uh, I've I've always been fairly open to

49:42

hiring remote devs. Um, so even like I

49:45

don't know, six years ago, putting up a

49:48

position for remote dev, we'd get 2,000

49:49

applicants. Um, and and a lot of them

49:52

are, you know, um,

49:56

people who are not prepared and are just

49:58

like, I want to put an application. and

50:00

I'll mop your floors. I don't care. Blah

50:01

blah blah blah.

50:02

>> It's like, okay, but I actually just

50:04

need a an experienced developer. I'm

50:06

sorry. Like, I don't know. Um,

50:09

>> the camera pans around and there's like

50:11

13 people mopping this one tiny piece of

50:13

floor. It's like, guys, we don't need

50:15

anymore.

50:16

>> Come on, write code. Come on. U so you

50:20

can sift through a lot of them pretty

50:21

fast but like it's it has really taken

50:24

like I think especially over the last

50:25

year um the influx of what are like

50:29

obviously just garbage like crapped out

50:33

AI written um AI submitted applications

50:36

has gotten crazy u and then sifting

50:39

through that it was already difficult

50:42

because we had so many applicants for

50:44

certain certain positions um if if it's

50:47

like hyper local and specialized it's we

50:49

don't get that many. Um Canada doesn't

50:52

have all that many people. Uh and then

50:54

this area is quite expensive to live in.

50:55

So it's it's a little bit, you know, if

50:57

it's if it's a local position, it's not

50:58

that much. If it's global, it's it's a

50:59

ton. Um but yeah, sipping through them

51:02

trying to find the stuff that's actually

51:03

real has gotten more difficult. And the

51:05

temptation to like counter sort

51:08

basically by okay, well, you're spamming

51:10

me with AI applications. Let me sort

51:12

through it with AI is high. Um, but then

51:15

the error rate there would suck if you

51:17

lose someone who's really good because

51:19

they got AI sifted out. Um, that would

51:21

be very unfortunate. So, there's some

51:23

tension there. Um, we have a a coding

51:26

test that we do for incoming applicants

51:29

of of every type of developer that we've

51:32

hired, which is a decent range. Uh,

51:34

we've had to make different ones. uh but

51:36

they're made in-house and we've ran that

51:41

coding test in a bunch of different

51:44

models to try to see what that output

51:47

looks like. Um and we try to

51:51

kind of detect how hard someone leaned

51:53

on it. I don't personally care like if

51:56

you look at the coding test and you get

51:58

AI assistance and you make the best

52:00

result out of everyone.

52:02

>> I think you made the result out of

52:04

everyone. um it doesn't really matter to

52:06

me too much, but there is a little bit

52:08

of sussing that I want to do to figure

52:10

out like did did you just take its

52:12

output and just slap it in and not even

52:14

uh in in Tea's situation review it

52:17

properly? Um did you just did you just

52:19

throw it through? Um, and if that's

52:21

true, then you know, I'm not that

52:22

interested because the even if it did

52:25

even if it did one shot super

52:27

effectively. Um, I'm concerned about

52:31

your ability to maintain things and keep

52:35

them good over time. Um, so yeah, hiring

52:38

is definitely changed. It was difficult

52:41

and now it's way harder.

52:44

So I I've been reliably informed by Sam

52:46

Alman that uh the problems of AI will in

52:49

fact be solved by AI. And so you're

52:52

telling me that you you aren't solving

52:53

your AI problems with AI?

52:55

>> No. Yeah, not so much. Not right now. Um

52:59

you know, we'll see if that happens

53:00

eventually, but I kind of doubt it.

53:01

There's there's there like there's the

53:03

basically inherent error rate and for

53:05

certain things that's uh frustrating to

53:08

deal with. All right. So, I actually do

53:09

want to ask a real question here, which

53:11

is that Okay, so I think

53:12

>> Wait, what were all Wait, what were all

53:13

the other questions?

53:14

>> Fake questions all those are all those

53:17

answers to get to get riled up and go on

53:20

a graphic 10-minute rant.

53:22

>> Oh god.

53:23

>> All right,

53:24

>> get wrecked, by the way. Okay, so the I

53:27

think the obvious elephant now in the

53:29

room, and I'm sure a lot of people would

53:31

appreciate this in the audience, which

53:33

is okay, I am stuck in effectively elo

53:36

hell, right? like you're playing League

53:37

of Legends except for it's with your

53:39

career and you're a junior and you're

53:40

trying to figure out how to get out of

53:42

ELO hell because everybody is just dog

53:44

piling in and quitting Midame. So, how

53:47

do I stand out at least in your process

53:51

without giving away too many? Because

53:53

then the AI will be like, "Got it." But

53:55

like, how would you make yourself stand

53:56

out in a sense that when reviewing you

53:59

go, "Oh, this is actually really good."

54:02

Um, the application I guess is how I'll

54:05

take this instead of the the code.

54:07

>> I assume the application is the

54:08

beginning of ELO hell, right? That

54:10

that's the bronze level right there.

54:11

>> Yeah, that's how I took that.

54:12

>> Would would it be possible just for

54:13

those of us who don't who aren't that

54:14

familiar with it? Also, what exactly

54:16

like what kind of people are you trying

54:18

to hire? Exactly. These are programming.

54:20

These are primarily programmers and

54:21

programmers for

54:23

what kind of stuff?

54:25

>> A pretty fairly surprising to most

54:27

people variety of things. So, so we have

54:30

multiple websites. Um, so we have

54:31

flplane.com which is the the the first

54:35

like thing that we made which is a

54:38

>> uh like patreones but video first um you

54:42

know creators support platform uh where

54:46

people can upload videos have their own

54:47

channel and get direct funding from

54:48

fans. We also have ltlabs.com

54:52

which is where a lot of our

54:55

I don't even know if I can say a lot.

54:56

Some of our testing data from our local

54:58

uh testing lab gets put up on there and

55:01

you can do comparison runs and and all

55:03

these other types of things which is

55:05

kind of neat. Uh then we have somebody

55:07

in chat pointed out LGT store. That

55:09

one's a lot more basic because it's on

55:13

top of Shopify. It's not just like our

55:15

own thing. Um but then we have tied that

55:18

in with like a system that we have which

55:21

is currently called merch messages but

55:22

it might be renamed where if we are on a

55:24

live stream and you are buying something

55:27

on the store as you're checking out you

55:30

can leave a a message and that message

55:32

will go to the stream to be go to a

55:34

stream dashboard. So, it can be curated

55:36

and then selected and then um the

55:39

producer can just respond to them in

55:41

line and then they'll show up in like

55:43

the the lower third banner at the bottom

55:45

>> or they can curate them and then Linus

55:47

or myself or whoever is hosting the

55:48

stream um can respond to them directly

55:52

through like voice. So, we have that tie

55:54

in. We have a couple other things like

55:55

that. Flip plane and the LT store link

55:57

together for like exclusive sales and

55:59

blah blah blah blah blah. Um that's most

56:03

of our web development. We also have

56:04

internal tools development um which

56:07

ranges through a bunch of things. We've

56:09

done a bunch of uh you know

56:12

internal development on top of snipet

56:15

for inventory stuff. We we wrote a guey

56:19

for whisper back in the day because our

56:20

editors didn't like doing command line

56:22

stuff. Um we helped automate things

56:26

around the office. Just little things

56:28

like that. And then the lab itself also

56:31

has a pile of developers um that work on

56:33

like data ingest uh both for handling

56:37

data from um well it's entirely for

56:40

handling data from like benchmarking and

56:42

testing of computer components but then

56:44

also making sure that like the website

56:46

receives the right stuff and not the

56:47

embargoed things and whatnot. Um, and

56:51

also making a variety of benchmarking

56:53

tools like Markbench is the the name of

56:56

one of the the tools that we have which

56:58

does a bunch of automations for testing

57:01

hardware. So like you you put a new

57:02

graphics card on a test bench. You run

57:04

Markbench. Markbench will kind of try to

57:07

verify that everything is set up

57:09

correctly and then automatically go

57:11

through run all the benchmarks. It'll

57:13

it'll set up the gain, make sure the

57:15

settings are correct, scroll through the

57:18

settings. um and take screenshots so

57:20

that if something is strange, if we're

57:23

looking at the results, we're like,

57:24

"This result seems really weird." We can

57:25

go back through and check, okay, was

57:28

G-Sync enabled on the on the computer?

57:30

It's a fairly common um you know, when

57:33

you're trying to test things um error

57:36

vector. Um is is this random setting in

57:39

the game wrong? Um like is this a game

57:41

where we had to manually select the

57:42

settings and and the person clicked

57:44

beside the drop down instead of on it?

57:45

Uh so it didn't actually select the

57:47

thing that they wanted. uh or whatever

57:49

else because the most frustrating thing

57:51

is like, okay, we have five days to like

57:53

fully test this suite of new graphics

57:55

cards. We're on day four, everything is

57:58

done. We notice this one result is super

58:00

weird.

58:02

>> Why?

58:02

>> Right?

58:03

>> Like, is it that one result is super

58:05

weird or is it all the other ones are

58:06

super weird and this one result is the

58:08

real one? So being able to go through

58:10

and figure out like dive through all the

58:13

information make sure everything's all

58:16

correct is super valuable. We also do um

58:20

some amount of like AI checking to

58:23

verify results. We only use that as an

58:26

early warning system. So that's running

58:27

as test results are coming in based on

58:30

our expectations. Um and that will try

58:32

to tell us if it thinks something is

58:34

wrong early. But that hasn't removed any

58:36

human checks. um to to verify all the

58:39

data as well. U so we have developers

58:41

working on on that tube. So we we have a

58:44

a fair bit of range of of people that

58:46

we're hiring in the development space.

58:48

Um and you asked uh what stands out for

58:52

me. It's the same thing personally. It's

58:54

the same thing that has kind of always

58:55

stood out. Uh my focal point keeps

58:57

moving. Sorry about that. Um I changed

58:59

my camera setup last night. Very smart.

59:02

Um but it it it it's been portfolio

59:05

stuff for me always. Like my my

59:09

first major specifically developer hire

59:13

was very very largely off of portfolio.

59:15

They had no post-secary experience at

59:17

all. They had no work experience, but

59:19

their portfolio was just insane. And I

59:22

gave them a way too difficult project.

59:24

We've we've drawn this back a lot since

59:26

back then, but we gave them a way too

59:28

difficult take-home project and they

59:29

just nailed it. My Oh man, I am evil for

59:33

this. Uh, but my first like take-home

59:35

project was make a game um and and

59:38

submit it. And I had I had some more

59:40

details than that, but it was brutal. It

59:42

was very brutal. And he made a um

59:46

>> it was actually really fun going through

59:47

those submissions. It was very fun. But

59:49

it was it was if I remember correctly,

59:50

it was it was I attempted to tone it

59:52

down so it wasn't like way too

59:54

>> AAA game 1 million in sales.

59:56

>> No back.

59:58

>> It was supposed to be web boost. I think

59:59

it was supposed to be Amal. Oh man,

60:03

>> roughly GTA,

60:05

buddy.

60:06

>> I know.

60:06

>> Yeah. Speaking of wanted levels in GTA,

60:09

you really didn't try hard enough.

60:11

>> Yeah. Well, it's I I don't remember the

60:13

exact details, but it was web based and

60:14

there was like some some stuff that

60:16

tried to keep it relatively relaxed, but

60:19

my god, that was way too crazy of a

60:21

scope. So that Yeah, that never happened

60:22

again. But he made a uh competitive

60:25

asteroids game. Um, and he set up a a

60:29

little bot that set off an alarm in his

60:31

house when I joined the lobby. Um, so I

60:34

I like loaded the website and joined the

60:35

lobby and it like went off and he ran to

60:38

his computer and then like fought

60:39

against me and there was chat in the

60:41

sidebar. So we like talked about the

60:42

game and I was just like this is insane.

60:45

This has to be the the guy. This is

60:46

crazy. Um, so

60:49

>> the alarm that is so brilliant of him to

60:52

actually create a a physical alarm. Like

60:54

that alone is like okay yeah you're

60:55

hired. That was a great That's a great

60:57

>> The whole thing is just nuts. I'm like I

60:58

already knew from his portfolio that I

61:01

was like very sold on this person and

61:03

then that happened. I was just like, "Oh

61:04

my god,

61:06

>> you already knew." And then you said,

61:07

"Go make a game." I mean, look.

61:11

>> I was, you know, I have changed. I've

61:13

reformed aware of this. Did you

61:17

>> Is he about to get a new lore drop? When

61:19

this thing comes out, it's going to be

61:21

really

61:21

>> Yeah.

61:22

>> Do you So, I was strictly out of

61:23

curious. Do you pay? Well, can we poach

61:25

this guy? Sounds pretty good.

61:28

>> I'm not I'm not going to disclose who it

61:30

was. We

61:31

>> We're not Yeah,

61:32

>> we try to do what we can. We're not

61:35

super competitive with It's It's tough,

61:37

man. The YouTube space is very different

61:38

than like Silicon Valley. If uh if

61:41

people want to like

61:43

>> really really push and be in like hyper

61:45

competitive environments, there's more

61:46

money out there. Um

61:47

>> Yeah, I was joking.

61:49

>> Yeah. Yeah.

61:50

>> It's just I've been joking, but also

61:52

seriously, what's his name? But also, if

61:54

you happen to tell me who it was, I

61:55

might pass.

61:56

>> But also, I have a game.

61:58

>> I might pass him along to some people.

61:59

I'm not saying

62:00

>> he's still on our team. I'm happy about

62:02

that.

62:04

>> Nice. All right. So, uh, a question I

62:06

really am actually very curious about,

62:08

which is I I don't know how to explain

62:09

this. I sent TJ a frantic message last

62:12

night and I've just been feeling it for

62:13

months on end about this, which is I

62:16

feel a change coming in the specifically

62:18

more in the tech YouTube space, but I

62:21

don't know what that change is, but I

62:23

know it's happening.

62:24

>> Wait, what?

62:25

>> Well, mean

62:27

the means in which people uh consume

62:29

content, what their expectations of what

62:31

content should look like,

62:33

>> what like all those things coming in. I

62:35

just feel like there's a change coming,

62:36

but I just don't know what it is more in

62:38

the tech space. just because there's a

62:40

big influx of people. Uh, you know, I

62:42

think there's

62:43

>> who knows what's going to happen. And so

62:44

I'm I'm actually very curious on your

62:45

thoughts and really I don't know how

62:47

much of the T you can spill on LT, but

62:49

if you do I think the second T does span

62:52

stand for T, but if like what is your

62:54

guys' thoughts about this next year or

62:55

these next two years? Is it business as

62:57

usual or do you think that there is like

62:59

some pivots you may have to make or

63:01

changes you have to make to remain more

63:03

competitive?

63:04

>> Yeah, I can talk pretty openly about

63:06

that. Um, one thing question that I

63:08

would throw back at you real quick is

63:09

that I often hear the the the software

63:12

dev space referred to as tech YouTube.

63:15

Um, because of you guys talking about

63:17

being in tech um for for tech YouTube is

63:21

usually like hardware stuff. Um, so when

63:25

you're talking about the change you're

63:27

feeling in tech YouTube, are you talking

63:29

more on the like development side or the

63:31

like uh consumer electronics and and

63:34

server stuff and whatnot side?

63:36

>> I would say either or honestly because I

63:37

think I think there is a just a general

63:40

uh going to be something is going to

63:41

happen here in this space that's just

63:43

going to kind of change maybe how people

63:45

consume information. I'm not really sure

63:47

yet. Yeah, I mean I can talk about some

63:49

of the like history of of LTT and and

63:52

the the change that we are still going

63:54

through uh which has been kind of from

63:56

the beginning. So when when Lattis and I

63:58

first started working together, we were

63:59

part of a computer shop up in Canada

64:00

called NCX. Um we would show up to to

64:05

like a filming day and in this in the

64:08

studio in a corner would just be a a

64:10

mountain of products. like it would it

64:13

would they the the logistics guys would

64:15

just throw them in the corner and they

64:17

would literally like pile up sometimes

64:19

up like to near the top of the windows.

64:21

Like it was it was a lot and we could

64:24

just like old school Linusectives videos

64:26

and even some of the old school NCX tech

64:28

videos um were just like

64:34

okay pull something out of the mountain

64:36

talk about it while taking it out of the

64:38

box end video upload. Uh, and back then

64:43

we've kind of retroactively defined that

64:45

as like productdriven video where there

64:49

was so much product is coming out so

64:51

often you're getting a new major

64:52

graphics card launch every nine months,

64:54

something like that. Um, you could

64:57

really just lean on the products are

65:00

interesting. Let's talk about the

65:01

products. Let's show you the products.

65:02

and that that is your content. Around

65:07

2015ish

65:09

maybe, um it started we started having

65:12

these conversations internally about

65:14

like we kind of have to

65:17

make the story now. Um that's when we

65:20

started filming things like Scrapard

65:21

Wars, which is like a series Scrapard

65:23

Wars like 2013, I think. Um, but we we

65:26

kind of saw the writing on the wall a

65:27

little bit early, but that Scrapped Wars

65:29

is a series where you have a fixed

65:32

budget and you go and you try to buy

65:33

used hardware and you compete against

65:35

each other to who can have the better

65:37

system. And that was us trying to like,

65:39

okay, let's create a story, let's create

65:42

an interesting thing instead of the

65:43

interesting thing being the name and the

65:45

title that is the new product that's

65:46

coming. Um, and

65:48

>> was that shift driven by necessity or

65:51

was that just you guys saying we could

65:53

expand or were you saying like no, we're

65:55

like the products aren't that

65:56

interesting anymore or there's too many

65:58

people doing this? Like how did why did

65:59

you decide to do that?

66:00

>> Yeah, it's a good question. It's it was

66:02

definitely both. Um, so we were you were

66:04

detecting a you know a wider release

66:08

cadence and kind of less interesting

66:10

product releases. Both of those things

66:11

kind of happening at the same time. And

66:13

also, you know, this is our full-time

66:16

thing now. Originally, when we were part

66:18

of NCX, this was I was going to school.

66:20

Uh, Lionus had a a job as a a a product

66:24

manager um or a guy who buys product. I

66:28

don't remember what his uh that's a

66:30

little different than a product badger.

66:31

>> Yeah. Yeah. Yeah.

66:32

>> At least on tech, you would buy like

66:34

SSDs and sell them through the store or

66:36

what.

66:37

>> Got it. Yeah.

66:39

So, this was our part-time thing. So,

66:41

there's only so much we could put into

66:42

it. And unboxing stuff was was, you

66:45

know, approachable. Now, when we're

66:47

doing this full-time, that's that was

66:48

probably the main starter for for

66:51

something like Scrapard Wars was like,

66:52

"Oh, we have time. We could do this

66:54

interesting thing." And we always wanted

66:56

to promote uh you know, you can buy

66:58

stuff used. You don't have to buy the

67:00

super flashy things all the time. And

67:01

it's been a little bit frustrating for

67:02

us forever that like the the you know

67:05

the 5090 video is going to get all of

67:07

the views and the card that people are

67:10

actually buying is not going to get

67:12

branded at all because people want to

67:14

see the we call it Lamborghini content.

67:16

People want to see the the big expensive

67:18

Halo products. Um and from there they'll

67:21

go like well I this card is really

67:23

interesting therefore I want Nvidia and

67:25

then they'll go buy the thing that they

67:26

can actually afford. Um,

67:29

so we wanted to find a way to make it

67:31

more entertaining

67:33

to see content that is about not just

67:37

blowing your wallet on everything. Um,

67:40

so that was the main reason for that.

67:41

But then the reason why we really

67:43

continued doing it, not only did it get

67:45

a ton of views, but was because there

67:47

wasn't a lot of other content we could

67:48

as easily make. Um, GPU timelines for

67:51

example.

67:52

>> Yeah,

67:52

>> I said nine months. That was around when

67:54

I first started doing content. Now it's

67:56

like two years. Um, so that has been a

67:59

sliding scale the whole time. Um, and

68:02

also it's

68:05

I I find the releases are getting a lot

68:07

less interesting. Um, like when the 8800

68:10

series GPUs came out, like oh the the

68:13

like performance expansion that happened

68:14

was mind-blowing and then now it's like

68:17

uh well you're paying 50% more dollar

68:20

and you're getting 50% more performance.

68:22

Hooray. Um

68:23

>> if even

68:25

>> Yeah, exactly. So it's like it's it's

68:27

it's not nearly as interesting. Um so

68:29

now we have to try to yeah create

68:31

stories, do weird projects, do stuff

68:33

like that. Um and I the the

68:36

competitiveness of it

68:40

maybe a bit. Um Lionus like notoriously

68:43

just like doesn't watch YouTube of

68:44

almost any form. Um, so like the seeing

68:48

what other people are doing and then

68:49

doing is

68:51

>> not so much of a a thing. Um, he'll read

68:54

comments on videos but like doesn't

68:56

really watch them which has gotten him

68:58

in trouble a couple times but uh you

69:00

know um it's I mean I watch a lot of

69:04

YouTube but um

69:06

>> yeah I don't think like what other

69:09

creators in the tech space are doing has

69:10

really driven a lot of

69:13

a lot of what we do. Um, there are plans

69:16

for the future. We want to resurrect

69:17

some channels that we have on hiatus.

69:19

Uh, we want to start making more videos

69:21

again. Um, but a lot of it's like, man,

69:25

if the products aren't there, we're

69:26

going to have to make something. Um,

69:28

that just is what it is. And if you're

69:29

trying to release, like if we want to

69:31

get back to say six videos a week, for

69:33

example, which is what we did for a

69:35

decade, um,

69:37

>> the vast majority of those are going to

69:39

have to be not, uh, you know, new

69:42

product review. maybe is product focus

69:44

but not new product review type videos

69:46

because there just isn't enough

69:48

interesting stuff.

69:48

>> Very good. Sorry, I was just thinking

69:50

about it. I was

69:50

>> like waiting for a response or did he

69:53

like the answer? Did he hate it? I don't

69:55

know. I can't tell.

69:57

>> Well, the mustache did not move. It

70:00

stayed completely stationary.

70:02

>> I thought maybe I I identified with uh

70:05

Lionus quite a bit cuz I I too

70:06

notoriously have been known for not

70:08

watching YouTube. Uh, true. It is a It

70:10

is a thing that

70:11

>> And I And I like watching YouTube. I can

70:13

relate a lot to you, Luke. I can relate

70:15

a lot.

70:15

>> Yeah, I know. TJ's my Luke. Uh,

70:18

>> there you go. Nice.

70:19

>> Also, the the important one in the

70:21

group, too. Uh, so uh

70:24

>> Okay. Okay. That's that's interesting.

70:25

Um, I'm just I was just curious about it

70:28

just because there's so much content now

70:31

that's getting pumped out and things are

70:34

even like you know the so much Jeypity

70:36

content that's getting uh put out right

70:38

now that's even getting millions of

70:39

views which is crazy that people are

70:41

just watching these kind of these I mean

70:43

I guess again I don't watch YouTube so

70:44

what am I saying? Why am I even saying

70:46

it's crazy right? Uh, good for them.

70:48

They're getting all that kind of stuff.

70:49

But I wonder like how that changes

70:51

people their perception how like they're

70:53

going to interact with videos. Does it

70:55

need to be a non-stop flow of factoids?

70:57

Is it going to be how does it optimize?

70:59

What is it going to be like? Is there

71:01

going to see something? I don't know. I

71:02

just I was just very curious about how

71:04

you guys are going to approach that,

71:05

especially more in uh you're not tech

71:07

YouTube. Obviously, you're hardware

71:08

YouTube.

71:09

>> Tech.

71:11

You guys might find tech differently.

71:12

But

71:12

>> I think we're test YouTube. No, it's I

71:14

mean it's interesting, right? Like

71:15

YouTube, in my opinion, is trending

71:17

towards extremes. Uh we we've talked

71:19

about this a little bit publicly where

71:21

we we feel like YouTube channels like

71:26

the the Mr. Beasts of the world are

71:28

doing super well. The NFL channel on

71:30

YouTube, those types of things are doing

71:32

extremely well. And then smaller, more

71:35

specified niche channels are also doing

71:37

really well because, and this does kind

71:39

of make sense to me because if you think

71:40

about what viewers would go for, they're

71:43

either going for the most like kind of

71:45

brain turn off

71:48

>> absorb fun thing uh content or they want

71:51

to like learn about something and really

71:53

really dive into something. Um, and

71:55

we've traditionally kind of floated in

71:58

the middle, uh, which on YouTube was

72:01

pretty good for a long time, um, and is

72:04

getting a little bit less good now. So,

72:06

that's kind of informing some of our

72:07

choices. Like I mentioned, we're looking

72:09

into resurrecting some channels. Um,

72:12

>> and there is some planning going on of

72:14

like trying to have

72:17

channels that are more

72:20

uh, more specialized. LT has always been

72:23

a generalist channel. Um,

72:26

>> Lattis will will review a phone and then

72:28

he'll make a a seven gamers, one CPU

72:31

computer. Uh, like it's it's a huge

72:33

range of stuff, right? And that's just

72:35

less rewarded in the current YouTube

72:37

ecosystem. We're also finding that

72:39

channel momentum is less important now

72:42

than it's like almost ever been. Uh,

72:44

which is a very weird space, very uh

72:47

uncertain space to be in. um where like

72:50

back in the day if you did like we would

72:53

go to CES, Consumer Electronic Show,

72:55

we'd release 30 videos um and they would

72:58

all do a little bit worse than normal

72:59

because we're just flooding the channel

73:01

and the impact of that would be lower

73:04

views for a while and we'd see our view

73:06

curve kind of go up over time because

73:08

we're kind of recovering that um that

73:11

kind of base. And these days that

73:12

doesn't happen, which is good and also

73:15

really terrifying. It's it's good

73:17

because if you release one bad video,

73:19

it's not going to negatively affect your

73:21

your future videos as much, but it's

73:23

really bad because the predictability of

73:26

how well your videos are going to

73:27

perform. Thus, your ability to, you

73:30

know, um

73:31

>> yeah,

73:32

>> have sponsors and and all these other

73:34

types of things be confident in your

73:35

like product, which is your ability to

73:37

release videos, um is going to go down.

73:40

It makes monetization less reliable.

73:42

makes big companies like ours a little

73:44

bit more sketched out because, you know,

73:46

we have 120 mouths to feast. So, um, if

73:49

if the if the ad rev or whatever slips

73:52

because we have a few videos in a row

73:55

that don't do super well, that can

73:57

impact us a lot, which is again one of

73:58

those reasons why we want to get back to

74:01

more video releases because,

74:03

you know, if you release once every two

74:05

weeks and it really doesn't hit and it

74:09

performs really, really terribly, that

74:11

impact on you is going to be really

74:12

high. If you're releasing all the time,

74:13

it can hopefully come out in the wash.

74:16

Uh but it's difficult to release that

74:18

much content effectively. We have a we

74:20

have a big team of editors. We have a

74:22

big team of writers. But um as we get

74:25

away from product review focused

74:27

content, the content is harder to make.

74:29

Um you have to dive deeper into things.

74:31

You have to come up with better ideas.

74:32

You have to come up with ideas that take

74:34

a lot of work, etc. Um

74:38

so it's yeah, we're trying to scale

74:41

towards that, but it's a it's a tough

74:43

problem. YouTube's always been that way,

74:45

though. the the landscape is constantly

74:46

changing, what the algorithm favors

74:48

constantly changing and and if you want

74:50

to survive, you have to kind of ride

74:51

that wave. So, it is what it is.

74:53

>> Great.

74:54

>> Yeah, it is interesting.

74:55

>> Yeah, I think like you just sort of see

74:58

now on the like uh the momentum for a

75:01

channel doesn't matter as much. Like

75:02

sometimes you just put out a really good

75:04

video and it just does really well and

75:06

it's like which is awesome and like

75:09

you're saying terrifying cuz you're like

75:10

okay well it's really hard to predict

75:12

what next week videos are going to do

75:15

right in terms of like what's going to

75:17

happen next. But it is fun because it

75:20

does feel a lot of times like when you

75:22

know a video is going to be good it does

75:24

like hit well which is fun. Uh which

75:26

makes the game pretty pretty fun to do.

75:28

I don't know what I prime I feel like

75:31

yesterday though I'll just say as well

75:33

you were just reading too much anthropic

75:35

blogs bro

75:38

>> oh my gosh I get I'm I'm I'm a big time

75:41

mirror and so uh if I hang out with

75:43

people that are really sad I feel more

75:45

sad and if I hang out with people that

75:47

are more like happy I I become more

75:49

happy I like hanging out with TJ he's

75:51

always smiling it makes me always smile

75:52

too it's also why I like hanging out

75:54

with Twitch chat they uh

75:57

>> they tend to be golden retrievers and it

75:59

makes me look at Luke's face right

76:01

there. Oh my god.

76:03

>> And so, uh, it's very, very exciting.

76:04

I'm just a simple farmer, right? But,

76:06

uh, but I started reading Dario's blog

76:10

>> and it's just I'm sitting there

76:11

thinking, man, like

76:12

>> also it's just like I just got

76:14

blackfilled so hard for like 30 minutes

76:16

of my life there and I was just like,

76:17

dang, man. This Daario guy, he walked I

76:20

just now I have a whole new opinion

76:22

about everything. Uh, but

76:24

>> that's okay. I sent him a happy message

76:25

afterwards and he was right back. voice.

76:27

We're so

76:28

>> right back. I just needed just a little

76:29

bit of so upgrade. Anyways, yeah, sorry.

76:32

The the AI stuff got me down hard last

76:33

night, but now I'm back. We're so back.

76:35

>> To jump back to the spiky views topic

76:37

for a section for a second, this section

76:39

of our channel I I I find very

76:42

interesting. If you if you go to our

76:43

channel, go to video, scroll down a

76:44

little bit, and you see the the Steam

76:46

Machine won't cost what you think video

76:48

from two months ago.

76:49

>> Yeah.

76:50

>> That got 2.8 million views.

76:52

>> The next video got 547,000.

76:56

So, like boom, it slammed down. And then

76:59

the next one got 848. The next one got

77:02

5.3 million.

77:04

>> Next one got 1.6. Next one got 900,000.

77:07

It's just like whoa. Like it it really

77:10

really depends on just how the audience

77:12

resonated with that video. Um, and there

77:15

is there's some informing of the

77:17

algorithm for your channel and what type

77:19

of content you make and what who they

77:20

might first seed it to and all that type

77:23

of stuff. Like there is some influence

77:24

there.

77:25

there's no momentum. Um, but dang. Yeah,

77:29

it's uh it's really it's a it's a very

77:33

different world these days.

77:34

>> I think they picked the wrong year to

77:36

release the Steam machine.

77:38

If they want to put any RAM in it, I

77:40

think is like to tie it back to our

77:42

original topic, it's going to have like

77:44

256K,

77:46

it's going to be like here's the here's

77:47

the Steam machine, guys. It's

77:50

>> $500 with no memory.

77:52

bring your own.

77:53

>> I've really been hoping that they

77:54

already have their a lotment. That's

77:56

who knows. I had no idea, but I've

77:58

really been hoping that's true because I

77:59

I want it to do well. I think like I

78:02

suspect everyone in here is at least a

78:03

little bit Linux build. Um

78:05

>> and it would be it would be nice to have

78:07

like a a

78:08

>> quite mainstream product like that. I

78:11

think Steam Deck has done like

78:15

>> immeasurable good for the like year of

78:18

the Linux desktop movement.

78:19

>> Absolutely.

78:20

>> Yes. that produced PewDiePie, which

78:22

PewDiePie produced a Linux video, and

78:24

that

78:24

>> that's huge. That was massive.

78:26

>> Glorious SSH.

78:30

>> But, uh, yeah, I mean, I think Steam

78:32

Machine can only move that forward. So,

78:34

hopefully it's good. Hopefully, it's

78:36

affordable.

78:37

>> We'll see.

78:38

>> We're actually doing a conference this

78:40

year about year of the Linux desktop. I

78:42

can't say anymore live because there's

78:44

some details still getting closed, but

78:46

it's pretty exciting.

78:48

>> Cool. Nice.

78:49

>> Yeah. All right.

78:50

>> Right, Brian. We're going to That's why

78:51

I'm wearing this.

78:52

>> I don't want Yeah. I don't I don't want

78:53

to say anything more. We're going to You

78:54

got to be quiet.

78:55

>> No, I'm hoping that you leak and then I

78:57

can uh I can yell at you.

78:59

>> You'll be like, "Gosh dang it. Why did

79:01

you say this explicit thing right here

79:03

that I'm now repeating? I'm not going to

79:05

do it."

79:06

>> Um All right. Well, Luke, thanks for

79:09

joining us on this. This was an awesome

79:10

standup. Learned a lot. So, if you want

79:12

to enjoy the whole episode, go to

79:13

Spotify for all the extras. Uh but the

79:16

main story, of course, is always on

79:17

YouTube. Thanks so much for joining us,

79:19

Luke. Thank you so much. Uh, is there

79:20

anywhere special people can find you?

79:23

>> Uh, the internet. Uh, no. Yeah, Linus

79:25

Tech Tips. Great point. Um, WAN show in

79:28

general,

79:30

>> I'm I'm around. Yeah.

79:31

>> All right. Awesome. And of course, Tee

79:34

and Casey, thank you very much for

79:35

joining us. Thank you everybody for

79:37

watching.

79:38

That is the standup. I've never We I

79:40

don't know. We don't really have like a

79:41

signoff line.

79:42

>> Yeah, I'll try and get better jokes next

79:44

time. Sorry Chad. I I missed a few this

79:46

time. Hey, no blockers. Galactis. Love

79:48

Galactis.

79:49

>> Byebye.

79:54

>> Errors on my screen.

79:58

Terminal coffee

80:00

and

80:02

living the dream.

Interactive Summary

Luke from Linus Tech Tips joins the panel to discuss the current state of hardware markets, focusing on the rising costs of RAM and SSDs driven by the AI boom. The conversation covers technical aspects of High Bandwidth Memory (HBM), the shift from consumer-focused products to enterprise-grade technology, and how AI is impacting the developer hiring process. Finally, Luke shares insights into the changing landscape of tech YouTube, emphasizing the move from simple product reviews to story-driven content as hardware release cycles slow down.

Suggested questions

5 ready-made prompts