WEBVTT - AI Made Everything Expensive (ft. GamersNexus)

0:00:02.440 --> 0:00:03.560
<v Speaker 1>Also media.

0:00:05.880 --> 0:00:09.320
<v Speaker 2>Hello on, welcome to Better Offline. I'm your host ed Zitron.

0:00:21.680 --> 0:00:24.000
<v Speaker 2>Subscribe to the newsletter, joined the subway and buy a

0:00:24.040 --> 0:00:25.599
<v Speaker 2>T shirt. All the links are in the notes. And

0:00:25.640 --> 0:00:27.400
<v Speaker 2>here's a joke to kick us off. What do you

0:00:27.440 --> 0:00:30.000
<v Speaker 2>call the CEO of a French RAM company? That's right,

0:00:30.320 --> 0:00:33.440
<v Speaker 2>Immanuel Micron, And that's what we're here to talk to

0:00:33.479 --> 0:00:36.400
<v Speaker 2>Steve Burke of Gamers. Next is about today, Steve, Welcome

0:00:36.400 --> 0:00:37.239
<v Speaker 2>back to the octagon.

0:00:37.600 --> 0:00:38.880
<v Speaker 1>Emmanuel Micron.

0:00:39.360 --> 0:00:43.600
<v Speaker 2>Yeah, before we started, yeah, because you would have killed

0:00:43.640 --> 0:00:46.440
<v Speaker 2>me before I read it on the But look, we're

0:00:46.479 --> 0:00:49.000
<v Speaker 2>here to talk about RAM. So we'll start with a

0:00:49.040 --> 0:00:52.640
<v Speaker 2>simple question. Why is RAM so expensive? Right now? What

0:00:52.840 --> 0:00:53.519
<v Speaker 2>is doing this?

0:00:56.080 --> 0:00:59.600
<v Speaker 1>I mean, the reason it's so expensive is not grounded

0:00:59.640 --> 0:01:04.120
<v Speaker 1>and reac I think you know, it's the surface of

0:01:04.160 --> 0:01:06.600
<v Speaker 1>it is that all the data center build out is

0:01:06.600 --> 0:01:10.080
<v Speaker 1>consuming all the memory and therefore, you know, the price

0:01:10.160 --> 0:01:13.280
<v Speaker 1>higher because everyone wants it. But I do think there's

0:01:13.280 --> 0:01:14.160
<v Speaker 1>a little bit more to.

0:01:14.080 --> 0:01:18.039
<v Speaker 2>It than that, right So from what so when you

0:01:18.120 --> 0:01:20.760
<v Speaker 2>build chips We're going to really simplify this one for

0:01:20.800 --> 0:01:23.240
<v Speaker 2>the audience because it's pain in the US to explain otherwise.

0:01:23.520 --> 0:01:26.120
<v Speaker 2>But when you build chips. You have something called a waifer.

0:01:26.200 --> 0:01:29.280
<v Speaker 2>You have the silicon out, and then you entch it

0:01:29.400 --> 0:01:34.119
<v Speaker 2>using a lithograph machine. But you can make less high.

0:01:34.280 --> 0:01:37.520
<v Speaker 2>So there's the high bandwidth memory that they use inside GPUs,

0:01:38.240 --> 0:01:40.280
<v Speaker 2>and then there's the regular DRAM that they use in

0:01:40.319 --> 0:01:43.000
<v Speaker 2>everything else. Right, is that it's a simplification.

0:01:43.040 --> 0:01:46.840
<v Speaker 1>But is that failure? I think like the the most

0:01:46.840 --> 0:01:49.800
<v Speaker 1>base level stuff to know is that memory, some form

0:01:49.800 --> 0:01:54.040
<v Speaker 1>of RAM or memory is in almost everything. A common misconception,

0:01:54.320 --> 0:01:56.800
<v Speaker 1>I'm not sure. I think your audience is like fairly technical,

0:01:56.840 --> 0:02:01.120
<v Speaker 1>but a layperson misconception is that storage is the same

0:02:01.120 --> 0:02:04.600
<v Speaker 1>as memory. They'll use it interchangeably. If storage is like

0:02:04.640 --> 0:02:07.320
<v Speaker 1>your drive that you you know, you put data on,

0:02:07.400 --> 0:02:10.880
<v Speaker 1>like photos or whatever, and then memory is is a

0:02:10.919 --> 0:02:13.799
<v Speaker 1>temporary form of storage of volatile storage, like it's wiped

0:02:13.840 --> 0:02:17.000
<v Speaker 1>when it's not actively being used when you restart and.

0:02:16.960 --> 0:02:19.320
<v Speaker 2>It's and when they put stuff in memory, that's where

0:02:19.880 --> 0:02:23.600
<v Speaker 2>that's like RAM and such where they like, that's where

0:02:23.600 --> 0:02:25.160
<v Speaker 2>you put the stuff that you gonna need quickly.

0:02:25.560 --> 0:02:28.880
<v Speaker 1>Right, Yeah, so yeah, memory is much faster than storage,

0:02:28.919 --> 0:02:31.600
<v Speaker 1>permanent storage, and so it acts as the sort of

0:02:31.639 --> 0:02:35.000
<v Speaker 1>transactional buffer to help get things to you quickly, So

0:02:35.280 --> 0:02:39.560
<v Speaker 1>memories and phones, refrigerators these days, cars, there's all kinds

0:02:39.600 --> 0:02:43.760
<v Speaker 1>of different grades of memory, and it's it's used in

0:02:43.760 --> 0:02:46.720
<v Speaker 1>pretty much everything to do some kind of quick like

0:02:46.760 --> 0:02:50.120
<v Speaker 1>in a car, Uh, maybe you need to retrieve something

0:02:50.240 --> 0:02:53.520
<v Speaker 1>related to like if there's a built in map on

0:02:53.600 --> 0:02:55.919
<v Speaker 1>the screen or something like that, or in a refrigerator.

0:02:56.080 --> 0:02:58.480
<v Speaker 1>Who the fuck knows, honestly, but I think that's I

0:02:58.560 --> 0:02:59.200
<v Speaker 1>think so that.

0:02:59.080 --> 0:03:01.679
<v Speaker 2>You can have a giant, horrible screen on your Samsung

0:03:01.760 --> 0:03:05.840
<v Speaker 2>fridge that displays you adds occasionally, yes, exactly, yeah, and

0:03:05.880 --> 0:03:08.679
<v Speaker 2>so so yeah, to go to your wafer count. Yeah,

0:03:08.720 --> 0:03:12.560
<v Speaker 2>there's different types of sort of production for memory, and

0:03:14.440 --> 0:03:17.200
<v Speaker 2>you'll find DRAM is used in all of it in

0:03:17.240 --> 0:03:19.920
<v Speaker 2>some capacity for the most part. So you'll find DRAM

0:03:20.639 --> 0:03:24.600
<v Speaker 2>dies in HBM like inside of an HBM package. But

0:03:25.280 --> 0:03:29.440
<v Speaker 2>data center high end GPUs will use high bandwidth memory,

0:03:30.040 --> 0:03:34.760
<v Speaker 2>and basically every consumer device uses something called GDDR, which

0:03:34.800 --> 0:03:39.320
<v Speaker 2>is just a lower bandwidth kind of more normal solution

0:03:39.880 --> 0:03:43.040
<v Speaker 2>that's not as overboard on the performance for a consumer application.

0:03:43.440 --> 0:03:47.040
<v Speaker 2>But they all kind of come from the same place,

0:03:47.080 --> 0:03:50.240
<v Speaker 2>which is a wafer. They're all cut from right so

0:03:51.320 --> 0:03:55.400
<v Speaker 2>right now, they're taking up more, they are using more

0:03:55.440 --> 0:03:57.240
<v Speaker 2>of the how much of the compacity are they actually

0:03:57.320 --> 0:03:59.400
<v Speaker 2>using to build high bandwidth memory? So the stuff that's

0:03:59.400 --> 0:04:00.440
<v Speaker 2>going to the GP use.

0:04:01.560 --> 0:04:04.680
<v Speaker 1>It appears to be an awful lot. I mean, so,

0:04:06.280 --> 0:04:10.760
<v Speaker 1>I know that the recent class action lawsuit or complaint

0:04:10.760 --> 0:04:15.360
<v Speaker 1>I should say that was filed notes that the profitability

0:04:15.520 --> 0:04:21.200
<v Speaker 1>the plaintiffs attorneys claimed that the profitability of traditional conventional

0:04:21.240 --> 0:04:25.760
<v Speaker 1>DRAM is greater than the profitability of HBM. That was

0:04:25.800 --> 0:04:30.000
<v Speaker 1>one of their claims. And yet they sort of argue

0:04:30.080 --> 0:04:32.400
<v Speaker 1>that it seems like their evidence is good, but they

0:04:32.520 --> 0:04:37.200
<v Speaker 1>argue that why would you shift more and more capacity

0:04:37.279 --> 0:04:40.839
<v Speaker 1>to producing this lower margin thing HBM? Right of like

0:04:40.920 --> 0:04:45.159
<v Speaker 1>the easier thing to make is potentially higher margin, And

0:04:45.200 --> 0:04:47.120
<v Speaker 1>so it does seem like more of it's shifting over there.

0:04:47.440 --> 0:04:47.640
<v Speaker 2>You know.

0:04:47.680 --> 0:04:51.039
<v Speaker 1>Open AI cause that sort of big kerfuffle previously when

0:04:51.360 --> 0:04:56.640
<v Speaker 1>they claimed forty of just all DRAMs globally though yeah

0:04:56.640 --> 0:04:58.480
<v Speaker 1>it didn't have it was all like basically.

0:04:58.320 --> 0:05:00.840
<v Speaker 2>One of the most insane just I mean sane story.

0:05:00.880 --> 0:05:02.680
<v Speaker 2>By the way, just last year, for those of you

0:05:02.720 --> 0:05:05.240
<v Speaker 2>who don't remember, open A story came out the open

0:05:05.279 --> 0:05:08.360
<v Speaker 2>A I was buying thirty five to forty percent of

0:05:08.560 --> 0:05:12.560
<v Speaker 2>all the world's dram wafers. It never happened, Yeah, but

0:05:12.600 --> 0:05:14.960
<v Speaker 2>we just talked about it like like we did, like

0:05:15.000 --> 0:05:15.440
<v Speaker 2>it did, but.

0:05:16.000 --> 0:05:17.320
<v Speaker 1>Now it did affect the price.

0:05:17.920 --> 0:05:21.719
<v Speaker 2>It did. But here's the question, So why is everything

0:05:21.800 --> 0:05:25.000
<v Speaker 2>so expensive that like is it? Is it the because

0:05:25.880 --> 0:05:27.719
<v Speaker 2>are they just jacking the price up?

0:05:29.320 --> 0:05:31.680
<v Speaker 1>I think so? I mean so, yeah, there's a couple

0:05:31.640 --> 0:05:35.159
<v Speaker 1>of things here a layout like some of the highlights,

0:05:35.160 --> 0:05:37.240
<v Speaker 1>and we can you can figure out how you want

0:05:37.240 --> 0:05:39.040
<v Speaker 1>to go through them. But sure one of them is

0:05:39.160 --> 0:05:43.880
<v Speaker 1>the memory industry has convictions actually in its past of

0:05:44.000 --> 0:05:48.120
<v Speaker 1>price fixing, collusion and as the DOJ dubbed it, cartel

0:05:48.200 --> 0:05:51.360
<v Speaker 1>like behavior. So this goes the early two thousands, there's

0:05:51.360 --> 0:05:53.479
<v Speaker 1>a bus to twenty sixteen, twenty eighteen. There was an

0:05:53.480 --> 0:05:57.520
<v Speaker 1>attempt at a similar lawsuit in the early nineties. The

0:05:57.560 --> 0:06:02.560
<v Speaker 1>memory manufacturers were talking about how they thought their competitors

0:06:02.600 --> 0:06:05.279
<v Speaker 1>were price fixing and colluding and so this is a

0:06:05.360 --> 0:06:08.400
<v Speaker 1>long and story to history where they and now there's

0:06:08.400 --> 0:06:12.599
<v Speaker 1>an active lawsuit, putative class action for price fixing. So

0:06:12.800 --> 0:06:16.560
<v Speaker 1>there's that antitrust aspect, which that obviously you know, prices

0:06:16.560 --> 0:06:19.800
<v Speaker 1>would be higher if you're just doing illegal things to

0:06:19.800 --> 0:06:22.440
<v Speaker 1>make the prices higher. There's also the sort of physical

0:06:22.440 --> 0:06:29.240
<v Speaker 1>manufacturing side, which is that to make memory, it's not

0:06:29.400 --> 0:06:32.559
<v Speaker 1>quick to get another fab online, and the companies seem

0:06:33.279 --> 0:06:35.679
<v Speaker 1>to sort of signal to each other through earnings reports

0:06:36.480 --> 0:06:41.120
<v Speaker 1>whether they're going to expand capacity or maintain capacity of

0:06:41.160 --> 0:06:45.320
<v Speaker 1>their fabs, which are factories for memory. So there's that aspect,

0:06:45.360 --> 0:06:49.080
<v Speaker 1>which is if there's a real or not a sudden

0:06:49.080 --> 0:06:51.840
<v Speaker 1>increase in demand, there's going to be a long latency

0:06:51.880 --> 0:06:54.200
<v Speaker 1>to react to that with more supply, if they even

0:06:54.279 --> 0:06:57.160
<v Speaker 1>want to. So the current projections are twenty twenty eight

0:06:57.240 --> 0:07:01.120
<v Speaker 1>or twenty thirty for getting like more fabs online. The

0:07:01.200 --> 0:07:03.440
<v Speaker 1>other reason it goes up, though, is really simple, which

0:07:03.480 --> 0:07:06.599
<v Speaker 1>is that in a server that goes in a data center,

0:07:07.279 --> 0:07:09.600
<v Speaker 1>some of Nvidia's newer solutions will use one and a

0:07:09.640 --> 0:07:13.840
<v Speaker 1>half terabytes of system memory. So that's d RAM they'll use.

0:07:14.240 --> 0:07:17.280
<v Speaker 2>Well they use this, they don't. They also use the

0:07:17.320 --> 0:07:20.640
<v Speaker 2>same RAM as we find in smartphones as well.

0:07:20.960 --> 0:07:26.040
<v Speaker 1>Yeah, LPDDR typically Yeah, yeah, so so Grace will use

0:07:26.200 --> 0:07:28.160
<v Speaker 1>I think it's five X I think is what they're on.

0:07:28.640 --> 0:07:31.960
<v Speaker 2>Yeah, I pulled the numbers and it's something like twenty

0:07:32.080 --> 0:07:34.880
<v Speaker 2>terabytes for an NVL seventy two, which is seventy two

0:07:34.920 --> 0:07:35.600
<v Speaker 2>GPU rack.

0:07:36.560 --> 0:07:42.280
<v Speaker 1>Yeah, so they do. The single blade for the Big

0:07:42.320 --> 0:07:46.680
<v Speaker 1>Boy is one and a half terabytes of system memory alone.

0:07:46.800 --> 0:07:51.680
<v Speaker 1>And you know, for perspective, a consumer desktop computer might

0:07:51.720 --> 0:07:54.680
<v Speaker 1>have sixteen gigabytes with Windows these days, you probably want

0:07:54.720 --> 0:07:57.440
<v Speaker 1>like thirty two, and they're they're taking one and a

0:07:57.440 --> 0:08:01.680
<v Speaker 1>half terabytes for one, you know, server solution. But that's

0:08:01.760 --> 0:08:05.320
<v Speaker 1>just the system mary. They also have other processors on there,

0:08:05.400 --> 0:08:08.360
<v Speaker 1>like the Blue Point or blue Field I think it's

0:08:08.400 --> 0:08:10.600
<v Speaker 1>called DPU. It takes one hundred and twenty eight gigabytes

0:08:10.600 --> 0:08:13.240
<v Speaker 1>if I remember correctly. The GPUs take hundreds of gigabytes

0:08:13.280 --> 0:08:17.280
<v Speaker 1>to like close to half a terabyte per GPU of HBM,

0:08:17.840 --> 0:08:22.800
<v Speaker 1>and the HBM has a there's kind of a yield

0:08:22.840 --> 0:08:26.040
<v Speaker 1>factor at play where you know you can when you've

0:08:26.080 --> 0:08:29.040
<v Speaker 1>talked about manufacturing, that means you're also talking yield how

0:08:29.080 --> 0:08:31.960
<v Speaker 1>many good products do you get for every bad And

0:08:33.040 --> 0:08:36.040
<v Speaker 1>HBM is more difficult to make. If you have a

0:08:36.120 --> 0:08:41.400
<v Speaker 1>failure in manufacturing, then you're also potentially losing more silicon

0:08:41.520 --> 0:08:42.760
<v Speaker 1>dyes that could have gone.

0:08:43.920 --> 0:08:47.920
<v Speaker 2>And HBM is made by stacking the memory, right, so

0:08:47.960 --> 0:08:51.880
<v Speaker 2>it requires just physically more memory. That's kind of an

0:08:51.920 --> 0:08:52.720
<v Speaker 2>APES description.

0:08:53.440 --> 0:08:57.600
<v Speaker 1>No, No, it's fine. Yeah, So HBM high bandwidth memory

0:08:58.040 --> 0:09:01.600
<v Speaker 1>is literally just really high bandwidth. It's kind of like

0:09:01.679 --> 0:09:04.480
<v Speaker 1>if you were to if you were a city and

0:09:04.520 --> 0:09:07.200
<v Speaker 1>you wanted to solve a public transit problem and you

0:09:07.360 --> 0:09:10.240
<v Speaker 1>just built a shitload of I don't know, let's.

0:09:10.080 --> 0:09:11.280
<v Speaker 2>Take a massive tunnel.

0:09:11.960 --> 0:09:14.040
<v Speaker 1>You build like a bunch of trains. You build a

0:09:14.040 --> 0:09:17.000
<v Speaker 1>ton of trains for passengers, but you don't have enough

0:09:17.040 --> 0:09:19.320
<v Speaker 1>tracks to put those trains on. They can't actually get

0:09:19.320 --> 0:09:22.360
<v Speaker 1>on the track without blocking each other. You haven't really

0:09:22.400 --> 0:09:24.600
<v Speaker 1>solved your problem. And so high bandwidth is trying to

0:09:24.640 --> 0:09:27.000
<v Speaker 1>solve that by saying, Okay, we've got all this capacity

0:09:27.040 --> 0:09:30.200
<v Speaker 1>for passengers, which is the memory itself. Now we need

0:09:30.240 --> 0:09:34.160
<v Speaker 1>something like a bigger road system to actually feed that

0:09:34.240 --> 0:09:37.320
<v Speaker 1>capacity through to access it. And so HBM tries to

0:09:37.320 --> 0:09:41.800
<v Speaker 1>solve that, especially because you look at GPUs that might

0:09:41.880 --> 0:09:46.200
<v Speaker 1>have like twelve plus times the amount of capacity that

0:09:46.240 --> 0:09:49.719
<v Speaker 1>a consumer GPU would have, and so you don't want

0:09:49.760 --> 0:09:54.679
<v Speaker 1>to starve the GPU core of the data that sits

0:09:54.720 --> 0:09:56.680
<v Speaker 1>in the memory by not being able to get it

0:09:56.800 --> 0:10:01.160
<v Speaker 1>fast enough. And so HBM tries to solve that problem. So, yeah,

0:10:01.200 --> 0:10:03.880
<v Speaker 1>to go back to your point of stacking, high bandwidth

0:10:03.920 --> 0:10:08.840
<v Speaker 1>memory is physically vertically stacked, as in, they take silicon

0:10:08.960 --> 0:10:12.600
<v Speaker 1>dyes for memory and they stack them atop each other

0:10:12.640 --> 0:10:15.800
<v Speaker 1>and then they connect them all together, as opposed to

0:10:16.000 --> 0:10:21.040
<v Speaker 1>consumer memory, where it's closer to there's still layers, but

0:10:21.040 --> 0:10:22.560
<v Speaker 1>it's closer to a flat plane.

0:10:23.559 --> 0:10:25.959
<v Speaker 2>Right. But it just means that by virtue of that,

0:10:26.200 --> 0:10:28.440
<v Speaker 2>it takes up more space in the place where they

0:10:28.480 --> 0:10:29.160
<v Speaker 2>build the chips.

0:10:29.400 --> 0:10:33.360
<v Speaker 1>Yeah. Yeah, if you're on a consumer device, then the

0:10:33.640 --> 0:10:37.440
<v Speaker 1>consumer memory you'll need more physical area to put the

0:10:37.440 --> 0:10:41.280
<v Speaker 1>same amount of capacity, whereas with the high end server

0:10:41.360 --> 0:10:44.679
<v Speaker 1>stuff you just stack that capacity vertically. And then it's

0:10:44.720 --> 0:10:50.640
<v Speaker 1>also hbm's really significant advantage is that it's very low

0:10:50.679 --> 0:10:53.760
<v Speaker 1>power comparatively, right, Yeah.

0:10:54.040 --> 0:10:55.880
<v Speaker 2>But just to be clear, it takes up more space

0:10:55.920 --> 0:10:57.320
<v Speaker 2>on the fabricator itself.

0:10:57.960 --> 0:11:00.920
<v Speaker 1>Oh yeah, yeah, if you're talking about the space, then yes,

0:11:01.080 --> 0:11:05.160
<v Speaker 1>HBM requires a lot more space for a few reasons.

0:11:06.080 --> 0:11:09.120
<v Speaker 1>In terms of manufacturing area. In terms of like footprint

0:11:09.240 --> 0:11:11.839
<v Speaker 1>on a product, it's less, but in a fab it's more.

0:11:12.040 --> 0:11:17.559
<v Speaker 1>And why is that in the fab One of the reasons.

0:11:17.720 --> 0:11:21.120
<v Speaker 1>So there's a few, but one is that HBM requires

0:11:21.120 --> 0:11:27.000
<v Speaker 1>additional silicon pieces to be able to function. So with

0:11:27.280 --> 0:11:31.840
<v Speaker 1>GDDR consumer GPU memory, you pretty much you have the

0:11:31.880 --> 0:11:34.959
<v Speaker 1>memory module. It looks like a black rectangle, and then

0:11:35.080 --> 0:11:38.280
<v Speaker 1>if you were to use like acid or something to

0:11:38.280 --> 0:11:40.960
<v Speaker 1>etch away the black plastic part, you'd be left with

0:11:41.440 --> 0:11:44.360
<v Speaker 1>pretty much a singular silicon die underneath. That's all it

0:11:44.440 --> 0:11:48.760
<v Speaker 1>is for consumer. For HBM, you also need a logic dye,

0:11:48.920 --> 0:11:52.240
<v Speaker 1>So there's another piece of silicon that interfaces with the

0:11:52.280 --> 0:11:55.600
<v Speaker 1>memory and the stack of memory, because you need something

0:11:55.640 --> 0:12:01.520
<v Speaker 1>to kind of to command and control and understand, you know,

0:12:01.559 --> 0:12:03.840
<v Speaker 1>the vertical tower you've got of memory. And then you

0:12:03.880 --> 0:12:08.480
<v Speaker 1>also need an interposer die, which sits underneath everything. So

0:12:09.040 --> 0:12:12.320
<v Speaker 1>this is a solution that will sit under your GPU core,

0:12:12.440 --> 0:12:15.360
<v Speaker 1>which is a very large piece of silicon and is

0:12:15.440 --> 0:12:19.680
<v Speaker 1>shared with the HBM stacks. So all of your your

0:12:19.720 --> 0:12:22.760
<v Speaker 1>core and all your HBM is stacked on top of

0:12:22.800 --> 0:12:25.280
<v Speaker 1>the same it's called an interposer. It looks like a

0:12:25.480 --> 0:12:28.640
<v Speaker 1>PCB and they all communicate through that. So that's another

0:12:29.040 --> 0:12:32.880
<v Speaker 1>piece of silicon. And so for this these reasons alone,

0:12:33.080 --> 0:12:35.559
<v Speaker 1>there's also others, but you know these alone. Now you're

0:12:35.600 --> 0:12:39.400
<v Speaker 1>involving more fabs. There's more logistics shipping things around, and

0:12:39.440 --> 0:12:44.120
<v Speaker 1>there's more fab or fabrication plant area allocated. Even if

0:12:44.160 --> 0:12:46.400
<v Speaker 1>you're just talking about making someone's got to make the

0:12:46.400 --> 0:12:50.480
<v Speaker 1>logic dies TSMC makes the interposers, right. Yes, there's just.

0:12:50.480 --> 0:12:52.720
<v Speaker 2>More moving parts and that kind of takes up more

0:12:52.720 --> 0:12:58.319
<v Speaker 2>space exactly. Yeah, So why So to my early question,

0:12:58.720 --> 0:13:01.640
<v Speaker 2>so this stuff is obviously lower margin, but they seem

0:13:01.679 --> 0:13:04.160
<v Speaker 2>to be able to sell an absolute shit ton of it.

0:13:04.240 --> 0:13:07.120
<v Speaker 2>So is that potentially why they're doing this that just

0:13:07.679 --> 0:13:11.000
<v Speaker 2>they know there is insane demand on a level that

0:13:11.640 --> 0:13:13.560
<v Speaker 2>for a high well, I guess they can charge what

0:13:13.600 --> 0:13:15.600
<v Speaker 2>they want for it as well. I'm just having trouble

0:13:16.520 --> 0:13:19.000
<v Speaker 2>trying to work out what it is they're doing other

0:13:19.040 --> 0:13:20.480
<v Speaker 2>than just filling their boots.

0:13:20.760 --> 0:13:22.800
<v Speaker 1>Have you try to asking the chat GPT.

0:13:23.920 --> 0:13:27.400
<v Speaker 2>No, I could ask my cat and get an answer

0:13:27.400 --> 0:13:30.800
<v Speaker 2>of respect, but it's genuine. But it's genuinely because it

0:13:30.920 --> 0:13:35.240
<v Speaker 2>seems the unless I'm misunderstanding here, that these micro and

0:13:35.360 --> 0:13:38.760
<v Speaker 2>eske High Inex and Samsung they're just kind of cranking

0:13:38.840 --> 0:13:41.720
<v Speaker 2>up the price of regular RAM because they can.

0:13:43.040 --> 0:13:45.440
<v Speaker 1>I mean to some extent. Yeah, So I think this

0:13:45.480 --> 0:13:49.439
<v Speaker 1>is where the price fixing allegations come into I don't know,

0:13:49.480 --> 0:13:51.480
<v Speaker 1>if you try it, if you try to take their side,

0:13:51.520 --> 0:13:52.920
<v Speaker 1>which I really don't want it.

0:13:52.960 --> 0:13:54.200
<v Speaker 2>I'm trying. I'm trying.

0:13:54.360 --> 0:13:58.720
<v Speaker 1>Yeah, if you try to, I think their argument, whether

0:13:58.720 --> 0:14:02.240
<v Speaker 1>it's for truthful or not, but would be We've got

0:14:02.280 --> 0:14:05.960
<v Speaker 1>this crazy high demand for HBM. These are guaranteed customers.

0:14:06.080 --> 0:14:12.360
<v Speaker 1>I can sell terabytes of it to Jensen, and it's

0:14:12.480 --> 0:14:15.640
<v Speaker 1>it's one point of contact. It all moves quickly and easily.

0:14:16.280 --> 0:14:18.920
<v Speaker 1>And this there's this data center demand right now, and

0:14:18.960 --> 0:14:20.400
<v Speaker 1>we don't know if it's going to be here forever.

0:14:20.440 --> 0:14:22.640
<v Speaker 1>But consumers, you know, they're they're always going to have

0:14:22.720 --> 0:14:25.400
<v Speaker 1>to buy electronics or whatever. So I'm not exactly sure

0:14:25.440 --> 0:14:28.720
<v Speaker 1>if that's to me, it seems like maybe you make

0:14:28.800 --> 0:14:33.640
<v Speaker 1>some sort of you assign some value to the B

0:14:33.680 --> 0:14:37.800
<v Speaker 1>two B relationship over B two C or something maybe,

0:14:37.840 --> 0:14:43.920
<v Speaker 1>But also I guess if they yeah, I'm not sure,

0:14:43.960 --> 0:14:44.640
<v Speaker 1>if you make.

0:14:44.840 --> 0:14:47.760
<v Speaker 2>Why would that mean that they charge more for regular RAN.

0:14:47.840 --> 0:14:50.000
<v Speaker 1>Oh As far as why more for regularly, that part's easy.

0:14:50.080 --> 0:14:56.000
<v Speaker 1>That's just because the HBM itself takes the same a

0:14:56.000 --> 0:14:59.600
<v Speaker 1>lot of the same machines as consumer memory. And so

0:14:59.600 --> 0:15:02.880
<v Speaker 1>if you're made more HBM, you're naturally making less consumer,

0:15:03.880 --> 0:15:06.280
<v Speaker 1>which I think is where you start seeing the supply

0:15:06.400 --> 0:15:11.480
<v Speaker 1>squeeze and the price go up. Likewise, a single piece

0:15:11.520 --> 0:15:14.480
<v Speaker 1>of HBM can use up to something I think it's

0:15:14.520 --> 0:15:16.920
<v Speaker 1>like it might be like thirty two dies max or

0:15:16.960 --> 0:15:21.480
<v Speaker 1>something of DRAM you'll commonly see like four referenced. But

0:15:22.320 --> 0:15:27.520
<v Speaker 1>single piece of HBM will take more dram dies to build.

0:15:27.560 --> 0:15:30.840
<v Speaker 1>And so one of the problems is if let's just

0:15:30.920 --> 0:15:33.000
<v Speaker 1>say four, If you have a piece of HBM that's

0:15:33.000 --> 0:15:35.600
<v Speaker 1>got four dram dies in it and you have one

0:15:35.680 --> 0:15:40.680
<v Speaker 1>failure somewhere in that stack or in packaging an assembly,

0:15:41.760 --> 0:15:46.840
<v Speaker 1>now you've destroyed you know, four individual pieces, rather than

0:15:46.880 --> 0:15:49.080
<v Speaker 1>if you have a yield failure with a consumer device,

0:15:49.600 --> 0:15:50.280
<v Speaker 1>you destroy one.

0:15:50.360 --> 0:15:53.280
<v Speaker 2>Sorry to ask a stupid question, what is a die exactly?

0:15:53.360 --> 0:15:56.120
<v Speaker 2>Is that just the what we would think of as

0:15:56.160 --> 0:15:57.240
<v Speaker 2>a stick of ram.

0:15:57.800 --> 0:16:02.840
<v Speaker 1>Uh No, a die is so a wafer we'll start

0:16:02.880 --> 0:16:06.240
<v Speaker 1>the wavefer level. A wafer is just a disc, right,

0:16:06.280 --> 0:16:09.400
<v Speaker 1>it looks like a CD that typically eight or twelve inches,

0:16:11.000 --> 0:16:15.360
<v Speaker 1>and they they process it and they pattern it where

0:16:15.360 --> 0:16:19.560
<v Speaker 1>they literally project like a pattern or they lithographically etch

0:16:19.600 --> 0:16:24.640
<v Speaker 1>a pattern onto the surface of this disc. Once that's done,

0:16:25.000 --> 0:16:28.520
<v Speaker 1>you know, these these patterns, they're called patterns because it's

0:16:28.520 --> 0:16:35.240
<v Speaker 1>a repeating sort of set of shapes that ultimately form

0:16:35.280 --> 0:16:40.080
<v Speaker 1>the logic that makes the silicon. And the word dye

0:16:40.160 --> 0:16:43.320
<v Speaker 1>comes from the process dicing. So with a wafer, when

0:16:43.360 --> 0:16:48.000
<v Speaker 1>they're done producing it and patterning it and it's basically

0:16:48.040 --> 0:16:50.680
<v Speaker 1>ready to become a product, they need to cut that

0:16:50.800 --> 0:16:52.600
<v Speaker 1>disc into a bunch of small squares.

0:16:53.520 --> 0:16:55.600
<v Speaker 2>So it's like a big slab that they caught top.

0:16:56.080 --> 0:16:58.320
<v Speaker 1>Yeah, it's I mean, it's like making a pizza with

0:16:58.360 --> 0:17:02.000
<v Speaker 1>a pizza cutter. You know, they're they're doing a pattern

0:17:02.040 --> 0:17:04.200
<v Speaker 1>that only psychopaths would do on a pizza, which is

0:17:04.240 --> 0:17:07.800
<v Speaker 1>making a bunch of squares and uh, and so they

0:17:07.880 --> 0:17:10.720
<v Speaker 1>cut it into the squares. That's called dicing. And then

0:17:10.760 --> 0:17:14.240
<v Speaker 1>each of those pieces, the squares that yield from that,

0:17:14.280 --> 0:17:17.439
<v Speaker 1>those are the dyes. And so if you were to

0:17:17.440 --> 0:17:21.360
<v Speaker 1>pull up an image of any GPU, typically you'll see

0:17:21.400 --> 0:17:24.720
<v Speaker 1>one large it's called the monolithic dye, which means one

0:17:24.760 --> 0:17:30.600
<v Speaker 1>singular sort of piece of shiny reflective silicon mirror like finish.

0:17:30.600 --> 0:17:33.520
<v Speaker 1>That's your die. And then for memory, same exact concept,

0:17:33.600 --> 0:17:35.040
<v Speaker 1>just a lot smaller.

0:17:35.080 --> 0:17:40.240
<v Speaker 2>Right, So right, okay, so there's less space to make

0:17:40.320 --> 0:17:43.440
<v Speaker 2>regular rams, so they just crank up the price. That's

0:17:43.520 --> 0:17:47.440
<v Speaker 2>really that really is it? I think that's their entire thing, right,

0:17:47.600 --> 0:17:50.400
<v Speaker 2>But I saw Micron zernings and they had eighty four

0:17:50.440 --> 0:17:53.240
<v Speaker 2>point nine percent margins. So it just kind of feels

0:17:53.280 --> 0:17:55.000
<v Speaker 2>like they're setting the price to whatever they want it

0:17:55.000 --> 0:17:55.199
<v Speaker 2>to be.

0:17:55.800 --> 0:17:59.359
<v Speaker 1>You don't think there, you don't think that is? Is

0:17:59.359 --> 0:18:00.840
<v Speaker 1>that not an I think they need more?

0:18:00.920 --> 0:18:03.399
<v Speaker 2>Don't They should get ninety five percent? Well, it's just.

0:18:03.440 --> 0:18:06.200
<v Speaker 1>Kind of why are you setting the setting it so low?

0:18:06.240 --> 0:18:09.000
<v Speaker 2>They should get one hundred and ten percent margins? We

0:18:09.000 --> 0:18:13.120
<v Speaker 2>should No, It's just it's very frustrating as well, because

0:18:13.800 --> 0:18:16.920
<v Speaker 2>I've read now arguments in favor and against Micron where

0:18:16.960 --> 0:18:20.960
<v Speaker 2>it's like, oh, Micron got screwed by Apple and consumer

0:18:21.000 --> 0:18:25.680
<v Speaker 2>electronics companies during the last during the last supply chain

0:18:25.800 --> 0:18:29.120
<v Speaker 2>crisis because they they kind of made a bunch more

0:18:29.200 --> 0:18:33.280
<v Speaker 2>ram than they needed to from the river. You know, like, no,

0:18:33.440 --> 0:18:37.639
<v Speaker 2>it really it really is. But what and it seems

0:18:37.680 --> 0:18:39.919
<v Speaker 2>to be there's this boom and bus cycle in memory

0:18:40.280 --> 0:18:43.560
<v Speaker 2>where they get a bunch of demand and then so

0:18:43.680 --> 0:18:46.359
<v Speaker 2>do they build more capacity? Is it that they just

0:18:47.400 --> 0:18:50.119
<v Speaker 2>ordered too much RAM and then people cancel their orders

0:18:50.160 --> 0:18:52.040
<v Speaker 2>like what happened? What happened last time?

0:18:54.880 --> 0:18:58.200
<v Speaker 1>Yeah, so it's cyclical, I will say right now, as

0:18:58.359 --> 0:19:00.240
<v Speaker 1>nothing like I've ever seen. And we suppoke to a

0:19:00.280 --> 0:19:03.480
<v Speaker 1>bunch of companies purchasers of memory like g Skill and

0:19:03.520 --> 0:19:05.960
<v Speaker 1>course Air, who sell the sticks of RAM that you

0:19:05.960 --> 0:19:08.640
<v Speaker 1>put in a computer, and those guys are telling us

0:19:08.880 --> 0:19:12.639
<v Speaker 1>on record that likewise they've never this is not like

0:19:12.680 --> 0:19:17.040
<v Speaker 1>part of the cycle. This is special. And as for

0:19:17.600 --> 0:19:20.920
<v Speaker 1>how is it different, how the difference is, how much

0:19:21.040 --> 0:19:24.040
<v Speaker 1>the difference is the percentage increase it is this time?

0:19:24.160 --> 0:19:27.840
<v Speaker 1>So you know, you're looking at like seven hundred percent

0:19:27.840 --> 0:19:30.200
<v Speaker 1>increase in price in some situations in a very short

0:19:30.200 --> 0:19:35.600
<v Speaker 1>period of time. Normally, cyclically you'll see some ebbs and flows,

0:19:35.640 --> 0:19:38.920
<v Speaker 1>but it might be like back in the day, a

0:19:38.960 --> 0:19:41.840
<v Speaker 1>fifty dollars kit of DDR four became eighty five or

0:19:41.920 --> 0:19:45.080
<v Speaker 1>ninety dollars, maybe even one hundred and twenty if it's

0:19:45.119 --> 0:19:47.080
<v Speaker 1>a really bad year, you know, but you're still at

0:19:47.440 --> 0:19:51.200
<v Speaker 1>like a little worse than double, Whereas now a two

0:19:51.240 --> 0:19:53.679
<v Speaker 1>hundred dollars kit of memory is suddenly a thousand to

0:19:53.680 --> 0:19:58.119
<v Speaker 1>twelve hundred dollars. Uh, And so it's just the the

0:19:58.160 --> 0:20:01.200
<v Speaker 1>amount of the price in is what's different. And then

0:20:01.240 --> 0:20:07.679
<v Speaker 1>also this time, the sort of the contest for the

0:20:07.800 --> 0:20:15.119
<v Speaker 1>supply is it's coming from within the own industry, where

0:20:15.840 --> 0:20:19.840
<v Speaker 1>the very companies that would be the cause for an

0:20:19.840 --> 0:20:23.000
<v Speaker 1>increase in sales of consumer supply are now the cause

0:20:23.119 --> 0:20:37.360
<v Speaker 1>of these like insane unprecedented volume of sales for AI compontents.

0:20:40.680 --> 0:20:42.959
<v Speaker 2>But it isn't based like so the twenty twenty one

0:20:43.119 --> 0:20:45.800
<v Speaker 2>supply chain crisis chip crisis was because there was a

0:20:45.800 --> 0:20:48.719
<v Speaker 2>flood of consumer spending off the COVID, Yeah, and that

0:20:48.800 --> 0:20:51.879
<v Speaker 2>led to a bunch of consumer demand for products and

0:20:52.280 --> 0:20:55.600
<v Speaker 2>overall spending across the board. But like consumer demand drove,

0:20:56.160 --> 0:20:59.919
<v Speaker 2>this one seems different because it's not demand outside of

0:21:00.160 --> 0:21:04.920
<v Speaker 2>the outside of whatever like psychosis, the various hype sets.

0:21:05.280 --> 0:21:09.879
<v Speaker 2>They're not spending a trullion dollars in CAPEX really feel like,

0:21:09.880 --> 0:21:13.960
<v Speaker 2>it's not like consumers can't access whatever micros COVID.

0:21:14.040 --> 0:21:16.920
<v Speaker 1>I think you know what's interesting is the big three

0:21:16.960 --> 0:21:20.000
<v Speaker 1>memory makers decided not I think it was twenty twenty

0:21:20.040 --> 0:21:24.320
<v Speaker 1>two or three, to bring on more capacity in some

0:21:24.400 --> 0:21:26.919
<v Speaker 1>of these situations because they were talking about how they

0:21:27.480 --> 0:21:30.760
<v Speaker 1>got burned by oversupply and sort of fellow in COVID.

0:21:30.840 --> 0:21:31.000
<v Speaker 2>Right.

0:21:31.320 --> 0:21:33.359
<v Speaker 1>But what's interesting is if you go and look at

0:21:33.760 --> 0:21:36.240
<v Speaker 1>some of the small suppliers's not many of them, but

0:21:36.920 --> 0:21:39.479
<v Speaker 1>there's a couple of small memory makers that make them

0:21:39.520 --> 0:21:41.399
<v Speaker 1>like less than five percent of the market, Wind Bond,

0:21:41.880 --> 0:21:45.240
<v Speaker 1>Nanya or two of them. Nanya's in uh Well, headquartered

0:21:45.280 --> 0:21:47.639
<v Speaker 1>at least in Taiwana of where their fab is, but

0:21:48.240 --> 0:21:52.560
<v Speaker 1>they like these two companies as far as I'm aware.

0:21:52.560 --> 0:21:56.200
<v Speaker 1>I was just looking at this this morning. They increased

0:21:57.119 --> 0:22:00.240
<v Speaker 1>their their production capabilities at the time when the big

0:22:00.280 --> 0:22:04.280
<v Speaker 1>three we're saying that they weren't gonna do it because

0:22:04.640 --> 0:22:08.639
<v Speaker 1>you know, they got burned, right. It's interesting to me

0:22:08.680 --> 0:22:11.160
<v Speaker 1>because if you're this is the argument the lawsuit makes too.

0:22:11.680 --> 0:22:15.159
<v Speaker 1>If you're a small company, I would think you're at

0:22:15.160 --> 0:22:18.919
<v Speaker 1>the biggest disadvantage, the biggest risk to increase your production

0:22:19.000 --> 0:22:23.160
<v Speaker 1>capabilities with this massive amount of spend. If your biggest

0:22:23.400 --> 0:22:27.119
<v Speaker 1>competitors are saying like this, it looks like bad times ahead.

0:22:27.160 --> 0:22:29.119
<v Speaker 1>You know, we don't want to spend into this. But

0:22:29.160 --> 0:22:31.159
<v Speaker 1>if you're a small guy, like you're at the greatest

0:22:31.240 --> 0:22:34.520
<v Speaker 1>risk of going under. If you fuck up your your.

0:22:34.440 --> 0:22:36.680
<v Speaker 2>Cap back right? Why didn't that this is maybe this

0:22:36.760 --> 0:22:40.320
<v Speaker 2>is a dumb question. Why didn't them increasing supply allow

0:22:40.359 --> 0:22:42.000
<v Speaker 2>them to kind of on the cut the microns of

0:22:42.000 --> 0:22:42.359
<v Speaker 2>the world.

0:22:43.000 --> 0:22:47.880
<v Speaker 1>Yeah, that one is just because the there's a micron

0:22:47.960 --> 0:22:52.040
<v Speaker 1>does have a technology advantage, so they can make memory

0:22:52.040 --> 0:22:53.919
<v Speaker 1>that these other guys can't. HBM is one of them.

0:22:53.920 --> 0:22:55.919
<v Speaker 1>Maybe this is I didn't think about this till now,

0:22:55.960 --> 0:23:01.840
<v Speaker 1>but maybe there is a very a small part, I think,

0:23:01.960 --> 0:23:05.600
<v Speaker 1>but possibly part of an answer to your question of

0:23:05.640 --> 0:23:10.159
<v Speaker 1>why HBM that is something that's that other companies are

0:23:10.160 --> 0:23:12.919
<v Speaker 1>struggling to make successfully in current generations.

0:23:12.920 --> 0:23:15.760
<v Speaker 2>So it's well, I know, only like sk Heinex, Samsung

0:23:15.800 --> 0:23:17.760
<v Speaker 2>and micro An not the ones who can make HBM.

0:23:18.160 --> 0:23:21.480
<v Speaker 1>Yeah, and I the CXMT has also struggled with HBM,

0:23:21.560 --> 0:23:24.840
<v Speaker 1>and they're a new Chinese memory maker that's actually done

0:23:24.920 --> 0:23:28.280
<v Speaker 1>really well with DDR five. And so there may be

0:23:28.320 --> 0:23:30.560
<v Speaker 1>a little bit of a pulling the ladder up, you know,

0:23:30.680 --> 0:23:31.760
<v Speaker 1>after them factor.

0:23:32.280 --> 0:23:34.080
<v Speaker 2>Well, here's the question as well, when it comes to

0:23:34.160 --> 0:23:37.960
<v Speaker 2>high badmath memory, surely this is going to lead to

0:23:38.000 --> 0:23:41.919
<v Speaker 2>an oversupply situation regardless because HBM is used in what

0:23:42.080 --> 0:23:45.320
<v Speaker 2>video cards got that's such an anachrotistic term in the

0:23:45.320 --> 0:23:48.679
<v Speaker 2>AI bubble, but like it's used in video cards and

0:23:48.720 --> 0:23:50.520
<v Speaker 2>aigpus basically, right.

0:23:50.880 --> 0:23:55.160
<v Speaker 1>Yeah, it's very limited. There's almost there's effectively zero consumer

0:23:55.240 --> 0:23:55.720
<v Speaker 1>use case.

0:23:56.400 --> 0:24:00.280
<v Speaker 2>So when the AI bubble bursts, where does the high

0:24:00.320 --> 0:24:08.000
<v Speaker 2>bandwidth memory go? Oh? Yeah, I don't Oh okay, yeah,

0:24:08.000 --> 0:24:08.919
<v Speaker 2>because I'm not.

0:24:09.000 --> 0:24:11.199
<v Speaker 1>Talking about the bubble burst in all the.

0:24:11.200 --> 0:24:15.280
<v Speaker 2>Bubble thing I saw, Samsung is talking about increasing their

0:24:15.440 --> 0:24:19.160
<v Speaker 2>high bandwidth. They're spending like fifty something billion, five hundred

0:24:19.160 --> 0:24:22.960
<v Speaker 2>billion dollars across an interterminate period, but like also building

0:24:23.000 --> 0:24:28.119
<v Speaker 2>an entire new high bandwidth memory like factory, yeah and that.

0:24:28.880 --> 0:24:30.720
<v Speaker 2>But I was looking I think I sent you the

0:24:30.760 --> 0:24:33.600
<v Speaker 2>graph for coming on there was. I saw this chart

0:24:33.640 --> 0:24:36.359
<v Speaker 2>where it's like they were making what a couple hundred

0:24:36.600 --> 0:24:41.720
<v Speaker 2>million gigabytes of hbm is in twenty twenty two and

0:24:41.760 --> 0:24:44.480
<v Speaker 2>they're now selling like seven or eight trillion a year.

0:24:45.200 --> 0:24:52.040
<v Speaker 1>Yeah, So what's crazy is the hbm bit demand I

0:24:52.080 --> 0:24:54.639
<v Speaker 1>think I I think I first saw this on semi

0:24:54.680 --> 0:24:57.480
<v Speaker 1>analysis if I remember correctly when about the sort of site.

0:24:57.480 --> 0:25:03.560
<v Speaker 1>But the hbm bit demand from envi Idea was recently

0:25:03.880 --> 0:25:07.000
<v Speaker 1>projected to exceed all HBM bit demand of all other

0:25:07.040 --> 0:25:12.119
<v Speaker 1>companies combined from twenty twenty five good, And that's just

0:25:12.280 --> 0:25:16.879
<v Speaker 1>n VideA. And and again you have more wafer area

0:25:17.480 --> 0:25:23.120
<v Speaker 1>per bit than with d RAM consumed. That counts yield losses, right,

0:25:23.160 --> 0:25:26.160
<v Speaker 1>and so like. Increasingly, as they make more and more

0:25:26.160 --> 0:25:32.000
<v Speaker 1>of this, presumably for Envideo's devices, you will continue to

0:25:32.000 --> 0:25:37.600
<v Speaker 1>see consumers really get shafted if there's not new supply

0:25:37.680 --> 0:25:41.119
<v Speaker 1>online soon. And likewise, if they're focusing all their efforts

0:25:41.119 --> 0:25:45.840
<v Speaker 1>and resources on HBM for whatever reason, who's to say

0:25:45.840 --> 0:25:48.880
<v Speaker 1>that the new fabs will even make consumer memory anyway? Right?

0:25:48.960 --> 0:25:51.240
<v Speaker 1>Like there's they might just be more HBM.

0:25:51.720 --> 0:25:53.840
<v Speaker 2>Well, the thing is, if they're all built to make

0:25:54.840 --> 0:25:58.520
<v Speaker 2>maybe I'm missing something. They're building this fact, these these

0:25:58.560 --> 0:26:01.399
<v Speaker 2>fabs specifically for hype band with memory behind bad with

0:26:01.560 --> 0:26:03.520
<v Speaker 2>memory is only used really for the thing in the

0:26:03.560 --> 0:26:07.280
<v Speaker 2>AI bubble, right, What they're gonna do with all this

0:26:07.359 --> 0:26:08.560
<v Speaker 2>capacity when it's gone?

0:26:08.920 --> 0:26:11.520
<v Speaker 1>They would switched it over it, they'd switched the line.

0:26:11.520 --> 0:26:14.760
<v Speaker 2>I mean they would. But it's like, I guess they'll

0:26:14.800 --> 0:26:19.560
<v Speaker 2>just have aren't they just creating a future nightmare? I mean,

0:26:19.600 --> 0:26:21.840
<v Speaker 2>it's always good to have more capacity for them I guess.

0:26:22.160 --> 0:26:24.199
<v Speaker 1>I yeah, I mean, I guess it's good that and

0:26:24.240 --> 0:26:26.639
<v Speaker 1>more capacity. There's a lot of government money floating around

0:26:26.640 --> 0:26:29.200
<v Speaker 1>to right, Like Micron got a five billion dollar tax

0:26:29.240 --> 0:26:35.240
<v Speaker 1>break in New York as part of the the guess

0:26:35.240 --> 0:26:37.040
<v Speaker 1>big beautiful bill, but the.

0:26:36.960 --> 0:26:40.240
<v Speaker 2>Five billion Like Microns said they're going to spend two

0:26:40.359 --> 0:26:44.240
<v Speaker 2>hundred and fifty billion, right, Samsung and s K Heinez

0:26:44.280 --> 0:26:47.320
<v Speaker 2>have made two point one trillion dollars worth of commitments.

0:26:47.680 --> 0:26:50.200
<v Speaker 2>It just feels like it's it's almost like they saw

0:26:50.240 --> 0:26:52.400
<v Speaker 2>what happened in twenty twenty one and twenty twenty three,

0:26:52.440 --> 0:26:54.840
<v Speaker 2>which ended with all of them doing at least a

0:26:54.840 --> 0:26:57.520
<v Speaker 2>billion dollars of write offs, and when they were like,

0:26:57.560 --> 0:27:00.240
<v Speaker 2>fuck that, we can go bigger.

0:27:00.560 --> 0:27:04.920
<v Speaker 1>Yeah. Well, I mean I do think personally, I think

0:27:04.960 --> 0:27:09.240
<v Speaker 1>that they are colluding again, I think they are price fixing.

0:27:11.840 --> 0:27:15.879
<v Speaker 1>It might be through like a parallelism rather than a

0:27:15.920 --> 0:27:20.400
<v Speaker 1>literal behind closed doors, meaning like we're just gonna announce

0:27:20.600 --> 0:27:26.680
<v Speaker 1>our changes in earnings reports and then our friendly competitors

0:27:26.720 --> 0:27:28.800
<v Speaker 1>will kind of mirror us, and so.

0:27:29.000 --> 0:27:31.520
<v Speaker 2>Yeah, yeah, like it's kind of a prisoner's dilemma, like

0:27:31.720 --> 0:27:34.239
<v Speaker 2>if they don't raise prices, the other guy will. If

0:27:34.280 --> 0:27:36.800
<v Speaker 2>they and if they don't build capacity, the other guy will,

0:27:36.880 --> 0:27:38.560
<v Speaker 2>they won't get the long term deals.

0:27:38.720 --> 0:27:44.920
<v Speaker 1>And right now, yeah, and and also you know the

0:27:44.920 --> 0:27:48.560
<v Speaker 1>the wafers themselves. I have some interesting numbers I wrote down,

0:27:48.680 --> 0:27:52.919
<v Speaker 1>but I was looking up when you were asking about HBM.

0:27:52.920 --> 0:27:55.159
<v Speaker 1>I went and pulled up some of the original coverage

0:27:55.200 --> 0:27:59.520
<v Speaker 1>I did of HBM which started to come online or

0:27:59.520 --> 0:28:02.359
<v Speaker 1>at least being actively developed somewhere around I don't know,

0:28:02.440 --> 0:28:06.280
<v Speaker 1>twenty thirteen plus or minus a bit for AMD GPUs.

0:28:06.720 --> 0:28:11.840
<v Speaker 1>So yeah, when AMD it was working on Fiji and

0:28:11.880 --> 0:28:17.960
<v Speaker 1>its Fury GPUs, they debuted HBM. Actually for consumer devices.

0:28:18.000 --> 0:28:21.400
<v Speaker 1>They had HBM on Vega and on a couple other

0:28:21.480 --> 0:28:25.480
<v Speaker 1>architectures in like the twenty fifteen to maybe twenty eighteen

0:28:25.480 --> 0:28:29.920
<v Speaker 1>Area plus or minus a year or two and massively expensive,

0:28:30.440 --> 0:28:34.080
<v Speaker 1>just like it is today. The power efficiency was great,

0:28:34.119 --> 0:28:36.239
<v Speaker 1>which is really why they used it, although they were

0:28:36.240 --> 0:28:39.720
<v Speaker 1>banned with starved too. But I pulled up I'd done

0:28:39.760 --> 0:28:41.360
<v Speaker 1>some reporting at the time where I spoke to a

0:28:41.400 --> 0:28:44.240
<v Speaker 1>bunch of the people in the know in the industry,

0:28:44.960 --> 0:28:47.800
<v Speaker 1>and at the time twenty seventeen or so twenty sixteen area,

0:28:48.560 --> 0:28:54.320
<v Speaker 1>the HBM two memory for one of the devices should

0:28:54.320 --> 0:28:56.920
<v Speaker 1>have cost around one hundred and fifty dollars cost for

0:28:57.000 --> 0:29:02.200
<v Speaker 1>them to buy, and the interposer in the packaging should

0:29:02.240 --> 0:29:05.400
<v Speaker 1>have been another twenty five dollars one seventy five. And

0:29:05.440 --> 0:29:08.000
<v Speaker 1>this is these are you know, this is old technology. Now,

0:29:08.240 --> 0:29:10.800
<v Speaker 1>I'm sure a lot different. But the point of bringing

0:29:10.800 --> 0:29:13.360
<v Speaker 1>it up is that if you compare a sort of

0:29:13.480 --> 0:29:18.360
<v Speaker 1>time for time and at the same capacity at the time,

0:29:18.400 --> 0:29:21.320
<v Speaker 1>it would cost am D one hundred and seventy five

0:29:21.360 --> 0:29:25.240
<v Speaker 1>bucks or so to put HBM hod its device, whereas

0:29:25.280 --> 0:29:29.520
<v Speaker 1>with GDDR memory the non HBM stuff, they would have

0:29:29.600 --> 0:29:32.320
<v Speaker 1>been at somewhere around like sixty eight dollars.

0:29:33.680 --> 0:29:36.680
<v Speaker 2>So they would be just so, I guess the thing is,

0:29:36.920 --> 0:29:40.600
<v Speaker 2>they absolutely would make more money selling d RAM or

0:29:40.600 --> 0:29:44.280
<v Speaker 2>sorry GDR like regular people ram. It's just that right

0:29:44.320 --> 0:29:46.680
<v Speaker 2>now they have the business to kind of. It's not

0:29:46.760 --> 0:29:49.520
<v Speaker 2>just shitty. It's not these bullshit video cards will lose

0:29:49.560 --> 0:29:54.800
<v Speaker 2>the gamers. It's selling aigpus to big strong boys.

0:29:54.680 --> 0:29:57.720
<v Speaker 1>Yeah right, yes, like Sam Altman.

0:29:57.640 --> 0:30:01.920
<v Speaker 2>And yes, the big strong honky men like Dario Amma

0:30:02.000 --> 0:30:06.600
<v Speaker 2>day right right, yes, yeah, he I've never by the way,

0:30:06.600 --> 0:30:10.760
<v Speaker 2>I don't think i've ever seen someone spread so much

0:30:11.600 --> 0:30:19.080
<v Speaker 2>fear so anxiously as him. It's it's just pathetic. What's Yeah. Also,

0:30:19.600 --> 0:30:22.240
<v Speaker 2>here's a random thing as well for these a question

0:30:22.360 --> 0:30:24.640
<v Speaker 2>to the listeners and to you as well, Steve, you

0:30:24.680 --> 0:30:27.720
<v Speaker 2>ever see anyone on You've seen this weird habit of

0:30:27.720 --> 0:30:30.760
<v Speaker 2>Silicon Valley people of using AI now to add muscles

0:30:30.800 --> 0:30:31.240
<v Speaker 2>to guys.

0:30:32.560 --> 0:30:33.480
<v Speaker 1>This seen?

0:30:34.040 --> 0:30:36.760
<v Speaker 2>What's that about all of the weirdest things I've seen

0:30:36.760 --> 0:30:38.520
<v Speaker 2>in the tech industry's history, And there's a lot of

0:30:38.560 --> 0:30:39.000
<v Speaker 2>weird ship.

0:30:39.280 --> 0:30:41.200
<v Speaker 1>I don't know if it's just well, they're they're not

0:30:41.320 --> 0:30:43.479
<v Speaker 1>used to working for intellectual property at this point. They

0:30:43.560 --> 0:30:45.600
<v Speaker 1>just harvested, so why work for the muscles either.

0:30:46.240 --> 0:30:49.080
<v Speaker 2>Well, it's just it's really strange. Like I like, I

0:30:49.120 --> 0:30:53.120
<v Speaker 2>think the TVPN, the technology, the Blowjup Brothers network, like

0:30:53.160 --> 0:30:57.560
<v Speaker 2>they they they do it with like Dylan Patel, who's

0:30:57.600 --> 0:31:01.120
<v Speaker 2>just like a regular sized guy, and it's just it's sorry,

0:31:01.120 --> 0:31:03.080
<v Speaker 2>I've just realized that's weird. But then I saw someone

0:31:03.120 --> 0:31:05.080
<v Speaker 2>do it for Dario Amedey the other day, and this

0:31:05.240 --> 0:31:07.800
<v Speaker 2>is like, your body's your body. I don't judge people

0:31:07.840 --> 0:31:10.000
<v Speaker 2>for for like how they look, but at the same time,

0:31:10.080 --> 0:31:14.160
<v Speaker 2>Dario Amma day is not like a like fifth course

0:31:14.240 --> 0:31:17.400
<v Speaker 2>of steroids. Guy, Like, it's just the weird it's the

0:31:17.440 --> 0:31:18.800
<v Speaker 2>weirdest thing I've ever seen.

0:31:20.480 --> 0:31:25.880
<v Speaker 1>Did you see the story just recently of the copper

0:31:25.920 --> 0:31:27.880
<v Speaker 1>thieves stealing it from data centers too?

0:31:28.000 --> 0:31:32.480
<v Speaker 2>No, that was good. Have a rich better offline listener there, Yep.

0:31:34.080 --> 0:31:38.480
<v Speaker 1>Yeah, they probably wearing one of your T shirts.

0:31:37.200 --> 0:31:40.560
<v Speaker 2>Just don't god no disabout them.

0:31:41.280 --> 0:31:47.200
<v Speaker 1>Yeah, the SAT there's a title of thieves stealing copper

0:31:47.240 --> 0:31:50.720
<v Speaker 1>from data centers, and it's just like, oh, okay, I

0:31:50.720 --> 0:31:53.240
<v Speaker 1>mean it's really I guess there's no honor among thieves,

0:31:53.240 --> 0:31:55.640
<v Speaker 1>you know, it's just thieves stealing from thieves.

0:31:55.800 --> 0:31:58.400
<v Speaker 2>It's also inevitable at this point because you make these

0:31:58.400 --> 0:32:02.160
<v Speaker 2>giant things full of earth metals and then you put

0:32:02.160 --> 0:32:06.640
<v Speaker 2>them in neighborhoods usually with like like disadvantaged farm neighborhoods

0:32:06.880 --> 0:32:10.320
<v Speaker 2>or like like distressed towns in Texas. You're like, oh,

0:32:10.320 --> 0:32:12.760
<v Speaker 2>I wonder what will happen with the other business.

0:32:13.200 --> 0:32:15.520
<v Speaker 1>Yeah, I wonder what will happen when we screw over

0:32:15.600 --> 0:32:18.480
<v Speaker 1>all these people and.

0:32:17.480 --> 0:32:21.320
<v Speaker 2>And like mock them via the media constantly. Anyway, back

0:32:21.400 --> 0:32:25.160
<v Speaker 2>to back to ram, So, is this something that's going

0:32:25.200 --> 0:32:29.240
<v Speaker 2>to start affecting like storage so hard.

0:32:29.440 --> 0:32:33.360
<v Speaker 1>Yeah, yeah, yeah, so you mean like.

0:32:33.600 --> 0:32:38.200
<v Speaker 2>Actual yeah, like nand like solid state drives and the like.

0:32:39.000 --> 0:32:44.040
<v Speaker 1>Yes, so it's already effecting it. Storage is made at

0:32:44.080 --> 0:32:47.120
<v Speaker 1>the same fabs for the most part as memory, with

0:32:47.360 --> 0:32:50.920
<v Speaker 1>basically the same tools and mostly by the same companies,

0:32:50.920 --> 0:32:53.840
<v Speaker 1>although there's there's like one or two differences, but for

0:32:53.880 --> 0:32:57.239
<v Speaker 1>the most part it's the same people and tools, and

0:32:57.280 --> 0:33:03.040
<v Speaker 1>so definitely want affect the other anyway. But storage in

0:33:03.080 --> 0:33:06.760
<v Speaker 1>general has hasn't gone up as violently as memory, but

0:33:06.800 --> 0:33:11.719
<v Speaker 1>it has gone up. Some of the SSDs we had

0:33:11.720 --> 0:33:14.800
<v Speaker 1>bought previously. I was just checking this actually for like

0:33:14.960 --> 0:33:19.160
<v Speaker 1>ninety bucks maybe about a year ago, are now closer

0:33:19.200 --> 0:33:21.360
<v Speaker 1>to like one hundred and eighty one hundred and ninety

0:33:21.440 --> 0:33:24.760
<v Speaker 1>and Jesus Christ, yeah, I pull up a chart here.

0:33:25.400 --> 0:33:29.720
<v Speaker 2>That's just this is genuinely like I think, I don't

0:33:29.720 --> 0:33:32.240
<v Speaker 2>know if I'd said do anything that's activism, but like

0:33:32.600 --> 0:33:36.280
<v Speaker 2>I think people just need to know this is AI's fault. Yes,

0:33:36.320 --> 0:33:39.080
<v Speaker 2>And the worst part is it's not even as fault

0:33:39.080 --> 0:33:41.720
<v Speaker 2>because they need these data centers because they're taking forever

0:33:41.800 --> 0:33:45.360
<v Speaker 2>to build. It's like you can access claude and chat GPT.

0:33:45.480 --> 0:33:47.840
<v Speaker 2>You don't. There's no one. No one's like unable to

0:33:47.920 --> 0:33:50.800
<v Speaker 2>log on because there's not enough data sentences. Nothing's being stopped.

0:33:50.920 --> 0:33:52.920
<v Speaker 2>They're just like, no, we need to do we need

0:33:53.000 --> 0:33:55.760
<v Speaker 2>to buy buy the chips, need to build the data

0:33:55.760 --> 0:33:56.800
<v Speaker 2>sense for some reason.

0:33:57.760 --> 0:34:00.840
<v Speaker 1>Yeah, it's yeah, there's not like a I mean, I

0:34:00.840 --> 0:34:03.440
<v Speaker 1>guess they're maybe they make the argument of like we're

0:34:03.440 --> 0:34:06.040
<v Speaker 1>trying to make it better and the models will be

0:34:06.080 --> 0:34:07.120
<v Speaker 1>more complicated in that.

0:34:07.080 --> 0:34:08.320
<v Speaker 2>Require and what's not gonna happen.

0:34:08.440 --> 0:34:13.480
<v Speaker 1>But yeah, the storage though, So, looking at an average

0:34:13.560 --> 0:34:18.200
<v Speaker 1>price chart for four terabytes of solid state drive storage

0:34:18.400 --> 0:34:23.279
<v Speaker 1>VME on PC part Picker, which averages it, they have

0:34:24.719 --> 0:34:27.359
<v Speaker 1>the pricing at around it looks like maybe about two

0:34:27.440 --> 0:34:32.320
<v Speaker 1>hundred and seventy dollars in January last year, and now

0:34:32.440 --> 0:34:37.520
<v Speaker 1>it's somewhere around somewhere around eight hundred and nine hundred dollars.

0:34:38.000 --> 0:34:40.120
<v Speaker 2>And that's for what kind of storage that is.

0:34:40.040 --> 0:34:44.799
<v Speaker 1>For four terabytes. Uh so relatively large capacity, which is

0:34:44.800 --> 0:34:46.080
<v Speaker 1>going to be affected the most.

0:34:46.640 --> 0:34:47.480
<v Speaker 2>Jesus Christ.

0:34:47.880 --> 0:34:50.280
<v Speaker 1>Yeah, And this is where this is interesting too, because

0:34:50.880 --> 0:34:53.839
<v Speaker 1>one of the ways you'll see consumers getting shafted that's

0:34:53.880 --> 0:34:58.799
<v Speaker 1>not as obvious is some of the modern devices that

0:34:58.840 --> 0:35:02.320
<v Speaker 1>should be your next sort of you know, improvement upgrade

0:35:02.360 --> 0:35:05.920
<v Speaker 1>on past generations. They're actually coming down in capacity, So

0:35:06.719 --> 0:35:09.200
<v Speaker 1>I haven't looked at the exact devices names for a while.

0:35:09.239 --> 0:35:11.319
<v Speaker 1>We ran a report a while ago talking about some

0:35:11.360 --> 0:35:14.879
<v Speaker 1>of the phones and laptops that have shifted from say

0:35:14.880 --> 0:35:17.760
<v Speaker 1>a prior model of twelve or sixteen gigaway it's down

0:35:17.800 --> 0:35:23.520
<v Speaker 1>towards eight for memory, there's decreasing storage capacity as well.

0:35:23.640 --> 0:35:27.440
<v Speaker 2>Yeah, that's fucking tech. So everyone just suffers here, and

0:35:28.200 --> 0:35:32.040
<v Speaker 2>it's pretty like there's Micron's, Skehihex Samsung. They could just

0:35:32.280 --> 0:35:34.280
<v Speaker 2>they could have not done this, just to be clear,

0:35:34.400 --> 0:35:38.200
<v Speaker 2>just so they could have sat with like seventy percent margins.

0:35:38.719 --> 0:35:41.759
<v Speaker 1>They're already colluding anyway, and my opinion, so yeah they could.

0:35:41.760 --> 0:35:43.359
<v Speaker 1>They can clute it in a different way.

0:35:44.080 --> 0:35:46.759
<v Speaker 2>It's just it's so fucking straight. Well, I mean it's

0:35:46.800 --> 0:35:50.040
<v Speaker 2>actually no, that's not that's not fair. This isn't strange

0:35:50.080 --> 0:35:53.239
<v Speaker 2>at all. This is exactly like, this is exactly what

0:35:53.280 --> 0:35:56.440
<v Speaker 2>companies like this do. Yeah, like this, it's this kind

0:35:56.480 --> 0:36:01.160
<v Speaker 2>of vulgar kind of chancerism. And their argument, from what

0:36:01.239 --> 0:36:04.239
<v Speaker 2>I understand, is well, memory is cyclical, so we need

0:36:04.280 --> 0:36:05.600
<v Speaker 2>to fill our boots when we can.

0:36:06.480 --> 0:36:10.080
<v Speaker 1>And if you're calling something vulgar, then it's pretty vulgar.

0:36:10.400 --> 0:36:13.640
<v Speaker 2>Yes, just to be clear, as the vulgarest man in tech,

0:36:14.000 --> 0:36:17.240
<v Speaker 2>and that is a word now. But the thing is, though,

0:36:17.400 --> 0:36:20.439
<v Speaker 2>just to be clear, that's their argument though, because things

0:36:20.480 --> 0:36:22.279
<v Speaker 2>are good now, they can charge what they want so

0:36:22.280 --> 0:36:23.920
<v Speaker 2>they can fill their coffice for the future.

0:36:24.400 --> 0:36:29.719
<v Speaker 1>Yeah, I think so, and I mean you see it affecting.

0:36:30.360 --> 0:36:33.080
<v Speaker 1>I think that's probably their argument. I think on the

0:36:33.120 --> 0:36:36.000
<v Speaker 1>consumer side too, even a company like Lenovo, which is

0:36:36.680 --> 0:36:39.160
<v Speaker 1>not a manufacturer of memory, but they buy it and

0:36:39.160 --> 0:36:43.520
<v Speaker 1>they put it in stuff. I'm not sure if there

0:36:43.680 --> 0:36:47.440
<v Speaker 1>may be this. I don't know for fact, but there

0:36:47.480 --> 0:36:50.440
<v Speaker 1>may be a benefit for some of these companies as

0:36:50.440 --> 0:36:55.480
<v Speaker 1>well for a few reasons. One is there's a lot fewer.

0:36:55.560 --> 0:36:57.440
<v Speaker 1>It kind of reminds me a little bit of COVID

0:36:57.480 --> 0:36:59.880
<v Speaker 1>when all the stores that were twenty four seven, all

0:37:00.360 --> 0:37:03.239
<v Speaker 1>the grocery stores and whatever suddenly stopped being twenty four

0:37:03.280 --> 0:37:05.600
<v Speaker 1>to seven, and at least where I am not one

0:37:05.600 --> 0:37:08.359
<v Speaker 1>of them has gone back. And I think that the

0:37:08.360 --> 0:37:11.200
<v Speaker 1>memory capacity kind of equivalent here is this offers a

0:37:11.239 --> 0:37:14.799
<v Speaker 1>little bit of a reset, and so with.

0:37:14.840 --> 0:37:17.800
<v Speaker 2>Lower those expectations exactly.

0:37:18.040 --> 0:37:21.279
<v Speaker 1>Yeah, and now your next upgrade is more exciting. And

0:37:22.040 --> 0:37:23.880
<v Speaker 1>what I noticed with Lenovo when I was buying a

0:37:23.960 --> 0:37:28.439
<v Speaker 1>laptop was they had quietly snapped out of existence their

0:37:28.520 --> 0:37:32.600
<v Speaker 1>sixty four gigabyte model memory system memory of the device

0:37:32.640 --> 0:37:34.239
<v Speaker 1>I was looking at, and they only had thirty two.

0:37:34.360 --> 0:37:38.040
<v Speaker 2>And I think, has the memory had sold it onto

0:37:38.080 --> 0:37:38.560
<v Speaker 2>it as well?

0:37:39.000 --> 0:37:40.080
<v Speaker 1>It is, Yeah, you can't.

0:37:40.160 --> 0:37:43.440
<v Speaker 2>Oh so you just can't upgrade. You're just stuck. That's insane.

0:37:43.680 --> 0:37:47.480
<v Speaker 1>Yeah, And so I think what happens there for them,

0:37:47.600 --> 0:37:50.920
<v Speaker 1>you know, in their favor, I might argue, well, they

0:37:50.920 --> 0:37:53.640
<v Speaker 1>can't they're having trouble getting supply, just like everyone else.

0:37:53.680 --> 0:37:58.680
<v Speaker 1>That's probably true. But against them, if they've got sixty

0:37:58.719 --> 0:38:02.359
<v Speaker 1>four gigabytes of memory, because that's just one part of

0:38:02.440 --> 0:38:05.359
<v Speaker 1>the total bomb for a laptop they sell, they might

0:38:05.480 --> 0:38:08.640
<v Speaker 1>rather sell two people two laptops at thirty two gigabytes

0:38:08.840 --> 0:38:11.600
<v Speaker 1>right where they can get the markup on the whole thing, right,

0:38:12.040 --> 0:38:14.399
<v Speaker 1>rather than one guy a sixty four gigabyte laptop where

0:38:14.400 --> 0:38:16.680
<v Speaker 1>they're only marking it up. Whatever the hopefully whatever the

0:38:16.719 --> 0:38:19.919
<v Speaker 1>difference in the memory is. So I think you see

0:38:19.920 --> 0:38:21.360
<v Speaker 1>some of that here too, where there's.

0:38:21.280 --> 0:38:22.840
<v Speaker 2>Well they're just going to use it as a chance

0:38:22.880 --> 0:38:26.440
<v Speaker 2>to reset what people expect and just ohso prices are

0:38:26.440 --> 0:38:30.279
<v Speaker 2>probably never coming down right itself.

0:38:30.520 --> 0:38:33.200
<v Speaker 1>Funny enough that I was using them in this example,

0:38:34.080 --> 0:38:38.440
<v Speaker 1>just like two weeks ago at Is said that prices

0:38:38.480 --> 0:38:41.319
<v Speaker 1>will probably the word they used was never come back

0:38:41.320 --> 0:38:45.960
<v Speaker 1>down to what they were last year. And so yeah,

0:38:45.960 --> 0:38:46.320
<v Speaker 1>I think.

0:38:46.160 --> 0:38:50.640
<v Speaker 2>They're truly evil era, just like a like a disgusting

0:38:50.680 --> 0:38:55.120
<v Speaker 2>era full of horrible perverts. Because it's just it's so

0:38:55.200 --> 0:38:59.439
<v Speaker 2>frustrating as well, because America has price fixing laws. Yeah,

0:38:59.480 --> 0:39:02.440
<v Speaker 2>they we have price gouging laws, like we have means

0:39:02.440 --> 0:39:05.560
<v Speaker 2>of doing this, we just don't do it because obviously

0:39:05.560 --> 0:39:06.839
<v Speaker 2>of capitalism.

0:39:06.480 --> 0:39:09.240
<v Speaker 1>And they've been enacted, you know, like the DJ itself

0:39:09.719 --> 0:39:13.400
<v Speaker 1>busted these same companies in the early two thousands.

0:39:13.760 --> 0:39:16.960
<v Speaker 2>Yeah, that was before. That's before we had social media

0:39:17.080 --> 0:39:19.560
<v Speaker 2>for psychopaths to talk about stocks all day. Now we

0:39:19.600 --> 0:39:21.520
<v Speaker 2>need to keep now, we need to We need just

0:39:22.000 --> 0:39:24.799
<v Speaker 2>borderline corruption or real corruption in everything. That's the only

0:39:24.840 --> 0:39:26.279
<v Speaker 2>way to get things done these days.

0:39:26.440 --> 0:39:30.680
<v Speaker 1>And I think also there's probably incentive to you know,

0:39:30.719 --> 0:39:35.920
<v Speaker 1>if you're no administration of any party wants the economy

0:39:35.960 --> 0:39:37.640
<v Speaker 1>to fail on their watch and I think if you're

0:39:37.680 --> 0:39:43.239
<v Speaker 1>worried about and a bubble pop, and especially if maybe

0:39:43.640 --> 0:39:47.560
<v Speaker 1>spooking investors with the DJ investigation or something, might you know,

0:39:47.680 --> 0:39:50.040
<v Speaker 1>trigger part of that. It just seems like you wouldn't

0:39:50.080 --> 0:39:53.160
<v Speaker 1>be incentivized to not probe too much.

0:40:07.280 --> 0:40:10.160
<v Speaker 2>But isn't this going to cause just already is causing

0:40:10.200 --> 0:40:15.160
<v Speaker 2>hyper inflation within all electronics related products, because yeah, it

0:40:15.200 --> 0:40:17.640
<v Speaker 2>seems that these companies are fully dedicate to the graveyard

0:40:17.680 --> 0:40:21.360
<v Speaker 2>smash of making everything more expensive forever and at some

0:40:21.400 --> 0:40:24.400
<v Speaker 2>point that will start crushing all conceimer electronics.

0:40:24.719 --> 0:40:27.120
<v Speaker 1>Yeah, I think it will, you know, for some things

0:40:27.160 --> 0:40:30.920
<v Speaker 1>that can migrate more to software as a service and

0:40:30.960 --> 0:40:33.560
<v Speaker 1>hardware as a service. I think there's an end game

0:40:33.600 --> 0:40:37.319
<v Speaker 1>there for some of these companies where tell me more,

0:40:38.320 --> 0:40:43.279
<v Speaker 1>I think if it's okay we crushed demand for the

0:40:43.880 --> 0:40:50.320
<v Speaker 1>gaming GPUs market because filthy, poor casual gamers can't afford

0:40:50.360 --> 0:40:52.800
<v Speaker 1>our big strong GPUs that we need for data centers,

0:40:53.040 --> 0:40:55.680
<v Speaker 1>you know, I think if you crush that market, there

0:40:55.719 --> 0:41:00.400
<v Speaker 1>is potentially an out in the form of cloud gaming,

0:41:01.040 --> 0:41:03.240
<v Speaker 1>or maybe a better example where you don't have latency

0:41:03.239 --> 0:41:07.600
<v Speaker 1>as an issue, would just be if you as a company,

0:41:07.640 --> 0:41:10.840
<v Speaker 1>if you're worried about consumers getting systems that are powerful

0:41:10.880 --> 0:41:14.760
<v Speaker 1>in their hands and doing using LLLMS at home or whatever.

0:41:16.840 --> 0:41:19.080
<v Speaker 1>If that is suddenly out of reach because the memory

0:41:19.120 --> 0:41:22.560
<v Speaker 1>is too expensive and the GPS are too expensive, all right,

0:41:22.600 --> 0:41:25.320
<v Speaker 1>I guess they come crawling back to claude or chat GPT.

0:41:26.920 --> 0:41:29.239
<v Speaker 1>So I do think not everyone's going to be able

0:41:29.239 --> 0:41:34.640
<v Speaker 1>to grab that parachute. But I think that moving services

0:41:34.719 --> 0:41:37.720
<v Speaker 1>to cloud oriented services that you pay for every month

0:41:39.440 --> 0:41:42.399
<v Speaker 1>is a way that they can capture the people, which

0:41:42.440 --> 0:41:44.279
<v Speaker 1>is going to be most of them at some point,

0:41:44.280 --> 0:41:47.600
<v Speaker 1>who can't afford to actually own the full device to

0:41:47.600 --> 0:41:52.360
<v Speaker 1>do stuff cloud gaming. Cloud gaming sucks. But I also

0:41:52.400 --> 0:41:55.640
<v Speaker 1>I don't think that's the only place where you know.

0:41:55.680 --> 0:41:58.799
<v Speaker 1>I think one of the real conception if anyone here

0:41:58.920 --> 0:42:03.680
<v Speaker 1>is genuine about LM's and AIB in the future, I

0:42:03.719 --> 0:42:07.160
<v Speaker 1>would think at least companies like open aye would be

0:42:07.200 --> 0:42:12.480
<v Speaker 1>worried about that about lms getting too good if they're

0:42:12.520 --> 0:42:15.400
<v Speaker 1>locally hosted for like, let's just say, the vast majority

0:42:15.440 --> 0:42:21.719
<v Speaker 1>of basic tasks someone might want, and by by all

0:42:21.760 --> 0:42:24.480
<v Speaker 1>the prices of hardware remaining elevated, it does kind of

0:42:24.640 --> 0:42:26.320
<v Speaker 1>keep that at bay a little longer.

0:42:26.719 --> 0:42:30.520
<v Speaker 2>I just because I understand that, and you've said this before.

0:42:30.560 --> 0:42:32.719
<v Speaker 2>The idea that they want to push people towards not

0:42:32.760 --> 0:42:36.040
<v Speaker 2>owning anything. You'll own nothing and you'll love it, I

0:42:36.040 --> 0:42:40.200
<v Speaker 2>think is the phrase. And but at the same time,

0:42:40.840 --> 0:42:42.920
<v Speaker 2>do you think that that's actually their plan or do

0:42:42.960 --> 0:42:46.000
<v Speaker 2>you think my version of this is much simpler, which is,

0:42:46.080 --> 0:42:48.440
<v Speaker 2>do you think they have one? Or is this just

0:42:48.640 --> 0:42:50.799
<v Speaker 2>incredible short terminus thinking.

0:42:50.600 --> 0:42:52.439
<v Speaker 1>Yeah, I don't think it's the plan. I think it's

0:42:52.560 --> 0:42:54.920
<v Speaker 1>like the fallback for the future.

0:42:54.960 --> 0:42:57.840
<v Speaker 2>Google Stadia we all know is a huge success.

0:43:00.480 --> 0:43:04.600
<v Speaker 1>I contributed to the failure of that one. Yeah, that one.

0:43:05.200 --> 0:43:07.560
<v Speaker 2>There are ten people who must be so angry.

0:43:07.640 --> 0:43:09.840
<v Speaker 1>Oh, I'm sure there are.

0:43:09.719 --> 0:43:11.840
<v Speaker 2>Dozens of us G Force.

0:43:12.480 --> 0:43:16.000
<v Speaker 1>Now I had numbers at one point. I don't have

0:43:16.080 --> 0:43:18.960
<v Speaker 1>them currently, but I had a lot of Actually, I

0:43:18.960 --> 0:43:21.319
<v Speaker 1>think we talked about it on your show because I

0:43:21.320 --> 0:43:23.960
<v Speaker 1>pulled up their website. Yeah, however many millions of users,

0:43:23.960 --> 0:43:25.600
<v Speaker 1>and both of us were kind of surprised at it.

0:43:27.520 --> 0:43:30.920
<v Speaker 1>But yeah, I think, you know, I think gaming is

0:43:30.960 --> 0:43:33.000
<v Speaker 1>sort of the easy one to point to. I think

0:43:33.000 --> 0:43:37.880
<v Speaker 1>for a lot of casual users they might be okay

0:43:37.880 --> 0:43:41.759
<v Speaker 1>with cloud connected gaming, but I do think there's more

0:43:41.800 --> 0:43:44.840
<v Speaker 1>services than just gaming, you know that could be sucked

0:43:44.840 --> 0:43:48.040
<v Speaker 1>into the cloud. Even just stuff like QuickBooks has been

0:43:48.040 --> 0:43:49.600
<v Speaker 1>the one I've been ranting about recently.

0:43:49.800 --> 0:43:52.400
<v Speaker 2>I'm surprised that that isn't already sassed.

0:43:52.880 --> 0:43:57.160
<v Speaker 1>Well, basically is because the desktop version, it used to

0:43:57.200 --> 0:43:59.080
<v Speaker 1>be a buy at once for three hundred dollars, then

0:43:59.080 --> 0:44:01.080
<v Speaker 1>I went to seven hundred, and then they went to

0:44:01.760 --> 0:44:06.799
<v Speaker 1>fifteen hundred dollars annually for the desktop version, and you

0:44:06.920 --> 0:44:08.640
<v Speaker 1>have to log in when you launch it, just like

0:44:08.680 --> 0:44:13.280
<v Speaker 1>Adobe software. Oh good, And now they're killing desktop entirely

0:44:13.320 --> 0:44:17.280
<v Speaker 1>and you have to go to cloud, which I actually

0:44:17.320 --> 0:44:19.120
<v Speaker 1>I had just abandoned it and went to a free

0:44:19.120 --> 0:44:21.879
<v Speaker 1>tool instead. But like the point being, yeah, I think

0:44:21.880 --> 0:44:25.640
<v Speaker 1>a lot of these you know, these services they do

0:44:25.680 --> 0:44:28.080
<v Speaker 1>just increasingly go cloud connected.

0:44:28.480 --> 0:44:32.160
<v Speaker 2>But the problem is is cloud connected services still require RAM.

0:44:32.520 --> 0:44:35.440
<v Speaker 2>I mean, just anyone who's ever used an AI tool

0:44:35.480 --> 0:44:38.120
<v Speaker 2>that's still in your browser, well, I mean, Chrome itself

0:44:38.200 --> 0:44:41.080
<v Speaker 2>is a hog, as we all know. And so it's

0:44:41.120 --> 0:44:44.319
<v Speaker 2>just kind of like it feels that there's just going

0:44:44.360 --> 0:44:46.319
<v Speaker 2>to be a point that this escalates to the point

0:44:46.360 --> 0:44:49.440
<v Speaker 2>that it kills large parts of the consumer electronics industry.

0:44:49.480 --> 0:44:52.400
<v Speaker 2>I mean, so Neaster laying the next PlayStation. Microsoft is

0:44:52.440 --> 0:44:55.080
<v Speaker 2>increasing the cost of the next Xbox while firing all

0:44:55.120 --> 0:45:00.160
<v Speaker 2>the people who know how it works. Just an evil company.

0:45:00.320 --> 0:45:03.600
<v Speaker 1>I mean, it's and a steam machine is a great

0:45:03.600 --> 0:45:04.160
<v Speaker 1>example too.

0:45:04.280 --> 0:45:06.640
<v Speaker 2>I love that I just got when. I fucking love it?

0:45:06.680 --> 0:45:07.640
<v Speaker 1>Oh did you really? Wow?

0:45:07.680 --> 0:45:09.840
<v Speaker 2>I really love it. It's just what I But the thing is,

0:45:09.880 --> 0:45:14.839
<v Speaker 2>it's also insanely expensive. Yeah, it's unbelievable.

0:45:15.520 --> 0:45:18.959
<v Speaker 1>Yeah, it's because the Steamer Shione. We had talked to them,

0:45:19.800 --> 0:45:24.719
<v Speaker 1>and the quote they gave us was amazing when I'll

0:45:24.760 --> 0:45:27.279
<v Speaker 1>paraphrase it for the best of my memory, but they

0:45:27.280 --> 0:45:30.520
<v Speaker 1>were talking about how I asked them how did it

0:45:30.560 --> 0:45:32.399
<v Speaker 1>work buying from the memory manufacturers, like did you get

0:45:32.400 --> 0:45:34.680
<v Speaker 1>a contract price or how did you know? How did

0:45:34.719 --> 0:45:38.279
<v Speaker 1>you guarantee your memory supply? And the answer was there

0:45:38.280 --> 0:45:42.960
<v Speaker 1>are no contracts, And the valve guy told us, uh,

0:45:43.400 --> 0:45:46.520
<v Speaker 1>they're offered a price by the memory supplier. In this case,

0:45:46.640 --> 0:45:50.080
<v Speaker 1>the one we got was Heinex and if they say

0:45:50.080 --> 0:45:52.719
<v Speaker 1>no to that price, then the quote was they never

0:45:52.760 --> 0:45:57.440
<v Speaker 1>talked to us again, which is why I feel like

0:45:59.160 --> 0:45:59.960
<v Speaker 1>l like behavior.

0:46:00.440 --> 0:46:02.480
<v Speaker 2>I got some I got some thoughts. I don't think

0:46:02.520 --> 0:46:04.840
<v Speaker 2>I want to share on the record on that one.

0:46:05.040 --> 0:46:07.880
<v Speaker 2>That is just that you know what I'm right back

0:46:07.960 --> 0:46:10.640
<v Speaker 2>round to just I hope these companies supper, Like I

0:46:10.680 --> 0:46:13.120
<v Speaker 2>think the memory companies are evil, Like that's just an

0:46:13.160 --> 0:46:14.600
<v Speaker 2>evil way of doing business.

0:46:15.000 --> 0:46:17.200
<v Speaker 1>Yeah, I mean if it's coercion, right, Because it's like

0:46:18.040 --> 0:46:21.200
<v Speaker 1>if if the player is I offer you a price,

0:46:21.320 --> 0:46:24.200
<v Speaker 1>you say no, fine, I'll take my supply and self

0:46:24.239 --> 0:46:26.279
<v Speaker 1>to someone. I'll never even talk to you again. Like

0:46:26.640 --> 0:46:30.360
<v Speaker 1>you're now down to two companies you can buy from, right.

0:46:31.440 --> 0:46:33.799
<v Speaker 2>And it's not like and it's not and if they'll

0:46:33.840 --> 0:46:35.279
<v Speaker 2>never talk to you again, it doesn't matter if they

0:46:35.280 --> 0:46:40.400
<v Speaker 2>build more supply, right yeah, if you're on there Valve

0:46:40.440 --> 0:46:43.440
<v Speaker 2>as well, who are like the like royalty within the PC.

0:46:44.320 --> 0:46:48.440
<v Speaker 2>It's just this era is just about the companies hitting

0:46:48.480 --> 0:46:50.399
<v Speaker 2>on the people that made them rich.

0:46:51.120 --> 0:46:54.200
<v Speaker 1>And it's you know, the crazy part to me is

0:46:54.280 --> 0:46:59.239
<v Speaker 1>it's like the Valve is not a poor company. You know,

0:46:59.280 --> 0:47:01.799
<v Speaker 1>they're a private so we don't know how much they have,

0:47:01.920 --> 0:47:06.520
<v Speaker 1>but they are definitely a multi billion dollar company. And

0:47:07.320 --> 0:47:11.680
<v Speaker 1>Valve is getting bullied by the trillion dollar companies.

0:47:11.360 --> 0:47:13.880
<v Speaker 2>Which are only the trillion dollar companies because of the

0:47:13.920 --> 0:47:15.480
<v Speaker 2>stock speculation.

0:47:15.360 --> 0:47:19.520
<v Speaker 1>Right, Yeah, not like actually but yeah, it's just it's

0:47:19.520 --> 0:47:24.120
<v Speaker 1>insane to me because it's of course they're saying thing

0:47:24.280 --> 0:47:27.680
<v Speaker 1>Porster has no real power in the purchasing and they're

0:47:27.800 --> 0:47:31.600
<v Speaker 1>almost a billion dollar market cap, not quite. I don't

0:47:31.600 --> 0:47:33.239
<v Speaker 1>know if they've how far they've fallen, but they were

0:47:33.280 --> 0:47:35.200
<v Speaker 1>at one point a billion dollar market cap, and at

0:47:35.280 --> 0:47:38.760
<v Speaker 1>point being like, these aren't nobodies who want the memory,

0:47:38.800 --> 0:47:42.040
<v Speaker 1>and they're struggling to get the memory suppliers to talk

0:47:42.080 --> 0:47:46.359
<v Speaker 1>to them. They're like, they're serious players and they need

0:47:46.400 --> 0:47:48.560
<v Speaker 1>a lot of it, you know, and the response is

0:47:49.760 --> 0:47:51.959
<v Speaker 1>take it at this price or go fuck yourself, which

0:47:51.960 --> 0:47:52.719
<v Speaker 1>is crazy with me.

0:47:52.880 --> 0:47:55.560
<v Speaker 2>I was reading about the long term agreements the ske

0:47:55.719 --> 0:47:59.960
<v Speaker 2>Heinex is presenting and apparently they're considering removing price caps

0:48:00.040 --> 0:48:02.840
<v Speaker 2>because apparently they do the long term agreements. Yeah, and

0:48:02.880 --> 0:48:06.320
<v Speaker 2>then they say, okay, we like they won't go above

0:48:06.360 --> 0:48:08.479
<v Speaker 2>this bound so that you don't just get Roger. They're

0:48:08.520 --> 0:48:09.840
<v Speaker 2>just not doing that anymore.

0:48:09.880 --> 0:48:12.640
<v Speaker 1>I guess rodri it is. I don't think i've seen

0:48:12.640 --> 0:48:13.160
<v Speaker 1>the rider.

0:48:13.040 --> 0:48:16.560
<v Speaker 2>Classic British class, British, beautiful, British phrase.

0:48:16.840 --> 0:48:19.720
<v Speaker 1>I was gonna say, like, that's when I took British

0:48:19.719 --> 0:48:22.520
<v Speaker 1>literature and before I dropped out of college, is the

0:48:22.600 --> 0:48:27.200
<v Speaker 1>last time I read that? Yeah, I think the the

0:48:28.080 --> 0:48:32.799
<v Speaker 1>in the memory supply typically contracts, they do set a

0:48:32.880 --> 0:48:35.840
<v Speaker 1>ceiling and then my understanding is the way the contract

0:48:35.920 --> 0:48:38.719
<v Speaker 1>works if you're lucky enough to get one, is that

0:48:39.239 --> 0:48:42.319
<v Speaker 1>you're offered the supply and you have to buy it

0:48:42.480 --> 0:48:44.040
<v Speaker 1>or you have to pay a penalty.

0:48:44.040 --> 0:48:45.520
<v Speaker 2>Basically, yeah, take or pay right.

0:48:45.640 --> 0:48:47.600
<v Speaker 1>Yeah, Yeah, that's.

0:48:48.320 --> 0:48:50.680
<v Speaker 2>It just feels like the natural end of this is

0:48:50.719 --> 0:48:54.239
<v Speaker 2>going to be horrifying. It's just going to be. It's

0:48:54.239 --> 0:48:55.759
<v Speaker 2>going to be because they're going to be sitting on

0:48:55.800 --> 0:48:58.480
<v Speaker 2>all this hype bad memory. And I was having a

0:48:58.480 --> 0:49:01.200
<v Speaker 2>conversation friend of the Showcase Could Go yesterday and he

0:49:01.239 --> 0:49:03.400
<v Speaker 2>was saying that, like, well, they'll sell it to someone.

0:49:03.840 --> 0:49:07.960
<v Speaker 2>And while I agree on that, in theory, we're talking

0:49:08.000 --> 0:49:14.200
<v Speaker 2>about going from a few hundred million gigabytes of HBM

0:49:14.280 --> 0:49:17.440
<v Speaker 2>to trillions of it. So someone is going to be

0:49:17.520 --> 0:49:20.080
<v Speaker 2>left holding the bag. Maybe it won't be the memory companies,

0:49:20.120 --> 0:49:23.040
<v Speaker 2>but there's a situation where Nvidia or someone else is

0:49:23.120 --> 0:49:24.800
<v Speaker 2>just sitting on the stack of this crap.

0:49:25.480 --> 0:49:30.560
<v Speaker 1>Yeah, if they can't find devices to put it in

0:49:30.600 --> 0:49:34.560
<v Speaker 1>and they oversupply, then it'll be the same type of

0:49:34.600 --> 0:49:36.720
<v Speaker 1>apocalypse we've seen in the past, I mean twenty sixteen.

0:49:36.960 --> 0:49:41.720
<v Speaker 1>Like typically though, this benefits consumers on the crash inside

0:49:41.760 --> 0:49:44.600
<v Speaker 1>of the wave because you it becomes commoditizing and get

0:49:44.600 --> 0:49:48.520
<v Speaker 1>it super cheap. I'm not sure what happens here because

0:49:49.480 --> 0:49:52.000
<v Speaker 1>when we've already reset the expectations, like we were talking about,

0:49:52.000 --> 0:49:55.000
<v Speaker 1>so there's always already been a regression in the technology

0:49:55.000 --> 0:49:56.600
<v Speaker 1>that'll take a few years to kind of get back

0:49:56.600 --> 0:50:02.440
<v Speaker 1>to where we were. But then also whatever crash happens

0:50:02.480 --> 0:50:05.480
<v Speaker 1>next seems like it's not going to be isolated to

0:50:05.480 --> 0:50:07.640
<v Speaker 1>the memory industry, right, it seems like it'll be uh

0:50:08.840 --> 0:50:11.759
<v Speaker 1>like I sent you a photo during Computax of n

0:50:11.840 --> 0:50:15.439
<v Speaker 1>Videos advertisement in Taipei that said it all starts here.

0:50:16.239 --> 0:50:18.759
<v Speaker 1>Do you remember what? You replied with, No, I do not.

0:50:19.960 --> 0:50:25.719
<v Speaker 1>You replied with it parentheses next global financial crisis.

0:50:26.280 --> 0:50:31.400
<v Speaker 2>Yeah, it really is though, because it's like, think about it,

0:50:31.400 --> 0:50:34.920
<v Speaker 2>if we have just this glut of high bandwidth memory,

0:50:34.239 --> 0:50:38.680
<v Speaker 2>how many graphics cards do they realistically make? Because when

0:50:38.719 --> 0:50:41.600
<v Speaker 2>I was saying hundreds of millions of gigabytes, that was

0:50:41.600 --> 0:50:45.200
<v Speaker 2>back in twenty twenty two. So this was the demand

0:50:45.320 --> 0:50:50.840
<v Speaker 2>for these things for every games console manufacturer, every PC manufacturer, everyone.

0:50:52.080 --> 0:50:54.120
<v Speaker 2>As of twenty twenty two, when the economy was doing

0:50:54.120 --> 0:50:57.359
<v Speaker 2>a lot better, right and they only needed a few

0:50:57.400 --> 0:51:03.160
<v Speaker 2>hundred million, we could be sitting on arguably the largest

0:51:03.160 --> 0:51:08.239
<v Speaker 2>supply in memory history. Oh for like an for like, like,

0:51:08.360 --> 0:51:13.520
<v Speaker 2>you can't unbuild that memory, right, you can't pass it out.

0:51:13.640 --> 0:51:16.960
<v Speaker 1>You can't really there's no way to. You would need

0:51:17.000 --> 0:51:20.200
<v Speaker 1>an HBM device to put it on. There's no real

0:51:20.239 --> 0:51:23.960
<v Speaker 1>consumer HBM devices these days, and it's not something you'd

0:51:24.000 --> 0:51:28.160
<v Speaker 1>spin up fast. So yeah, if there's like too much HBM,

0:51:28.760 --> 0:51:30.000
<v Speaker 1>you don't really have a lot you could do with

0:51:30.000 --> 0:51:32.680
<v Speaker 1>it other than I guess sell it for cheaper or something.

0:51:33.800 --> 0:51:35.200
<v Speaker 1>But like, at the end of the day, you need

0:51:35.239 --> 0:51:38.759
<v Speaker 1>something to attach it to. And I mean one thing

0:51:38.800 --> 0:51:41.719
<v Speaker 1>to think about is part of those numbers, although I

0:51:41.719 --> 0:51:43.880
<v Speaker 1>don't think all of it, but part of it is

0:51:43.920 --> 0:51:47.160
<v Speaker 1>that the capacity per device has increased a lot for

0:51:47.800 --> 0:51:51.640
<v Speaker 1>non consumer devices since twenty twenty two, So some of

0:51:51.640 --> 0:51:54.799
<v Speaker 1>it is accounted for there where you just put more

0:51:54.800 --> 0:51:58.359
<v Speaker 1>on a device, But then you look at consumer and like,

0:51:58.480 --> 0:52:04.759
<v Speaker 1>somewhat notoriously, it has remained stuck at like eight gigabytes

0:52:04.760 --> 0:52:08.799
<v Speaker 1>to maybe sixteen gigabytes for a consumer GPU, which eight

0:52:08.920 --> 0:52:12.160
<v Speaker 1>is barely even enough to play modern games with any

0:52:12.200 --> 0:52:16.799
<v Speaker 1>kind of reasonably you know, high texture settings, and so

0:52:16.840 --> 0:52:19.799
<v Speaker 1>you don't have that multiply and effect in consumer. It's

0:52:20.040 --> 0:52:24.200
<v Speaker 1>just in data center. Which all that to say, if

0:52:24.239 --> 0:52:27.600
<v Speaker 1>more supply capacity goes online, if they're able to produce more,

0:52:28.719 --> 0:52:30.960
<v Speaker 1>but the data center demand slows down or the data

0:52:31.000 --> 0:52:35.840
<v Speaker 1>center GPU demand slows then and they switch back to

0:52:35.880 --> 0:52:39.319
<v Speaker 1>just consumer DRAM, they're still going to have too much

0:52:39.400 --> 0:52:45.120
<v Speaker 1>because the consumer devices are they don't use that much memory.

0:52:45.719 --> 0:52:49.000
<v Speaker 1>So I don't know, you finally spec them up maybe.

0:52:48.640 --> 0:52:52.800
<v Speaker 2>But but you'll just have all of this insane amounts

0:52:52.840 --> 0:52:55.400
<v Speaker 2>of high bandwidth memory to go. We're just going to

0:52:55.400 --> 0:52:58.480
<v Speaker 2>get graphics cards with one hundred and twenty eight gigabytes

0:52:58.480 --> 0:53:04.200
<v Speaker 2>of high bandwidth RAM just.

0:53:02.040 --> 0:53:03.960
<v Speaker 1>Just because they need to put it somewhere, right, Yeah, it.

0:53:04.000 --> 0:53:05.560
<v Speaker 2>Could, we got to do something with it. We're just

0:53:05.920 --> 0:53:09.080
<v Speaker 2>gonna have a laptops and you'll be able to open

0:53:09.320 --> 0:53:13.520
<v Speaker 2>seventeen or eighteen Chrome tabs. All right, it's gonna be incredible. No,

0:53:13.680 --> 0:53:15.400
<v Speaker 2>I think I wonder if there's also going to be

0:53:15.400 --> 0:53:16.960
<v Speaker 2>a knock on effect of all of this on the

0:53:17.080 --> 0:53:20.360
<v Speaker 2>used gaming market like they used PC market.

0:53:20.840 --> 0:53:26.160
<v Speaker 1>Well, that's a really common I see people asking about like, oh,

0:53:26.200 --> 0:53:28.319
<v Speaker 1>surely this is gonna be good for secondhand in a

0:53:28.320 --> 0:53:31.000
<v Speaker 1>few years when they retire all these devices or the

0:53:31.000 --> 0:53:31.960
<v Speaker 1>bubble pops.

0:53:31.680 --> 0:53:33.400
<v Speaker 2>Or I just I mean just like right now, I

0:53:33.440 --> 0:53:35.840
<v Speaker 2>mean just people won't be buying new devices.

0:53:36.200 --> 0:53:38.839
<v Speaker 1>Yeah, well, I mean on both of those right now.

0:53:38.880 --> 0:53:41.280
<v Speaker 1>It means that if you go look up ArtX thirty

0:53:41.320 --> 0:53:44.359
<v Speaker 1>series cards from I don't know, like shit, I think

0:53:44.360 --> 0:53:47.120
<v Speaker 1>it might be four or five years ago now on eBay,

0:53:47.600 --> 0:53:50.759
<v Speaker 1>some of them are like within twenty percent of what

0:53:50.800 --> 0:53:53.879
<v Speaker 1>they sold for new, you know. So it's yeah, it's

0:53:54.000 --> 0:53:57.200
<v Speaker 1>wrecking the used market because it's just like it's not

0:53:58.040 --> 0:54:00.879
<v Speaker 1>you're paying close to the new price for something that's

0:54:00.920 --> 0:54:03.799
<v Speaker 1>forty years old. So that's not good. And then on

0:54:03.840 --> 0:54:06.479
<v Speaker 1>the other side of it, none of the data center

0:54:06.560 --> 0:54:10.040
<v Speaker 1>hardware is useful in consumer there is no secondhand use case.

0:54:10.160 --> 0:54:13.319
<v Speaker 1>Yeah yeah, lpdd R five x is either on some

0:54:13.400 --> 0:54:19.480
<v Speaker 1>form of server specific cam card or is soldered to

0:54:19.520 --> 0:54:22.759
<v Speaker 1>the board, so you can't use that. And maybe in

0:54:22.880 --> 0:54:25.120
<v Speaker 1>China they'll deslder it, you know, and solder it onto

0:54:25.160 --> 0:54:28.680
<v Speaker 1>new sticks and sell Frankenstein thing but and then the

0:54:28.719 --> 0:54:34.080
<v Speaker 1>GPUs it's HBM, so it's it's attached to the GPU.

0:54:34.239 --> 0:54:36.359
<v Speaker 1>You can't just you can't just like take it off.

0:54:37.640 --> 0:54:40.960
<v Speaker 2>This is the thing as well, when it comes to

0:54:41.400 --> 0:54:44.000
<v Speaker 2>like this post dot com bubble recovery story, this is

0:54:44.080 --> 0:54:46.319
<v Speaker 2>I'm glad you brought that up, because it's like people like, oh, yeah,

0:54:46.320 --> 0:54:49.080
<v Speaker 2>they'll just use it for something else, useful infrastructure. It's like,

0:54:49.680 --> 0:54:52.480
<v Speaker 2>what useful infrastructure? What are we gonna do with all

0:54:52.480 --> 0:54:55.719
<v Speaker 2>these gps? It's not you can't run a black well

0:54:55.880 --> 0:54:58.840
<v Speaker 2>like a GB three hundred is what's a grace and

0:54:59.200 --> 0:55:02.439
<v Speaker 2>too blackwell? You've got over a terabyte of different kinds

0:55:02.480 --> 0:55:07.759
<v Speaker 2>of fucking rams on that of saying rams and what

0:55:07.840 --> 0:55:09.520
<v Speaker 2>you're gonna do with that? It's not got it's not

0:55:09.640 --> 0:55:13.200
<v Speaker 2>got DisplayPort. Yeah, it's not going to do anything. It's

0:55:13.239 --> 0:55:14.680
<v Speaker 2>still it's built for one thing.

0:55:15.040 --> 0:55:19.120
<v Speaker 1>Right, maybe a local AI model or whatever, but anything reason.

0:55:19.320 --> 0:55:22.320
<v Speaker 2>You couldn't do that unless it was in a consumer

0:55:22.719 --> 0:55:26.600
<v Speaker 2>hardware shell. Yeah, you assume you need like a dishwasher plug.

0:55:26.440 --> 0:55:28.759
<v Speaker 1>For it, or a washing machine plug even like yeah,

0:55:29.880 --> 0:55:32.600
<v Speaker 1>probably need to forty vault Jesus Christ.

0:55:34.080 --> 0:55:37.040
<v Speaker 2>People really, people need to do some do some actually

0:55:37.360 --> 0:55:41.200
<v Speaker 2>like reading about this because it's like they need to

0:55:41.239 --> 0:55:43.960
<v Speaker 2>realize that this can't go anywhere where else like this

0:55:44.200 --> 0:55:46.479
<v Speaker 2>just we're just going to have racks of these things

0:55:46.719 --> 0:55:48.680
<v Speaker 2>and it's not like in the future they'll be cheaper

0:55:48.760 --> 0:55:49.239
<v Speaker 2>to use.

0:55:49.520 --> 0:55:51.759
<v Speaker 1>I think that the But you know, if the dot

0:55:51.840 --> 0:55:55.279
<v Speaker 1>Com era argument of infrastructure was dark fiber or something

0:55:55.280 --> 0:55:57.360
<v Speaker 1>where the fibers in the ground, it's just it's not

0:55:57.480 --> 0:55:59.880
<v Speaker 1>used because all the companies went belly up. Eventually they

0:56:00.120 --> 0:56:04.040
<v Speaker 1>used it. Maybe that's your argument there. I really I

0:56:04.120 --> 0:56:06.359
<v Speaker 1>agree with you. I don't think it works for this one,

0:56:06.480 --> 0:56:09.960
<v Speaker 1>because the closest thing we have to an infrastructure gain

0:56:11.000 --> 0:56:14.719
<v Speaker 1>maybe is power, except the problem of their not really

0:56:14.800 --> 0:56:21.080
<v Speaker 1>bringing more online fast enough, and it's it's at least

0:56:21.160 --> 0:56:24.600
<v Speaker 1>currently it's not helping the prices for the rest of us,

0:56:25.000 --> 0:56:27.319
<v Speaker 1>Like almost everyone's had their power costs go up lately.

0:56:28.040 --> 0:56:30.400
<v Speaker 1>So maybe that would be the advantage if you're like,

0:56:30.760 --> 0:56:33.320
<v Speaker 1>because of data centers, we brought back nuclear and we

0:56:33.760 --> 0:56:36.440
<v Speaker 1>have shitloads of solar and wind and whatever. But that's

0:56:36.480 --> 0:56:38.920
<v Speaker 1>not what we're doing. It's not like our minds on

0:56:38.960 --> 0:56:41.400
<v Speaker 1>the roof, you know, And I don't know.

0:56:41.560 --> 0:56:43.759
<v Speaker 2>It's also what if the power doesn't what if the

0:56:43.800 --> 0:56:47.680
<v Speaker 2>power gets built and the demand isn't there. It's just

0:56:47.760 --> 0:56:51.239
<v Speaker 2>there's so many things that could go wrong here, and

0:56:51.360 --> 0:56:54.000
<v Speaker 2>I think people just kind of I think the reason

0:56:54.080 --> 0:56:55.759
<v Speaker 2>that this is all coming to a head is because

0:56:55.760 --> 0:56:59.440
<v Speaker 2>we're finally facing the physical problems. Yeah, they were like,

0:56:59.560 --> 0:57:02.959
<v Speaker 2>there's no so much capacity, there's only so much money,

0:57:03.000 --> 0:57:06.360
<v Speaker 2>there's only so much power, there's only so much silicon.

0:57:08.040 --> 0:57:09.920
<v Speaker 2>At some point this all has to break, and it

0:57:10.040 --> 0:57:10.880
<v Speaker 2>might break everything.

0:57:12.360 --> 0:57:18.200
<v Speaker 1>Yeah, I think I don't know what the I don't

0:57:18.240 --> 0:57:21.680
<v Speaker 1>know what the Enron moment will be. You know, I'm

0:57:21.720 --> 0:57:26.880
<v Speaker 1>not sure where it'll tip. But it does seem inevitable.

0:57:27.520 --> 0:57:29.840
<v Speaker 1>But I don't know. It could be a year, it

0:57:29.880 --> 0:57:32.360
<v Speaker 1>could be several years, right, Like, I have no idea.

0:57:33.080 --> 0:57:37.000
<v Speaker 2>It could just it feels like the moment the vibe shift,

0:57:37.240 --> 0:57:40.600
<v Speaker 2>because the trigger I'm looking for is that kapek s pullback.

0:57:41.000 --> 0:57:45.280
<v Speaker 2>But what scares me somewhat is the in video is

0:57:45.360 --> 0:57:47.640
<v Speaker 2>the I think, what fifty five sixty five percent of

0:57:47.680 --> 0:57:51.320
<v Speaker 2>all high bandwidth memory demand all for AIGPUS. That just

0:57:51.400 --> 0:57:54.080
<v Speaker 2>feels like a single point of failure.

0:57:55.520 --> 0:58:01.320
<v Speaker 1>Yeah, I think and video, I mean and video itself.

0:58:02.680 --> 0:58:08.280
<v Speaker 1>Jensen Juan himself said of core weave, that without and

0:58:08.440 --> 0:58:10.640
<v Speaker 1>Video there is no core weave, you know, like, if

0:58:10.640 --> 0:58:13.400
<v Speaker 1>I remember correctly that was, I'll go dig that up.

0:58:13.760 --> 0:58:19.080
<v Speaker 1>But they, you know, they create the circle, and video

0:58:19.320 --> 0:58:26.120
<v Speaker 1>is part of the circle, and it's Yeah, if anything

0:58:26.240 --> 0:58:30.640
<v Speaker 1>happens to them, then all of it falters, and then

0:58:31.000 --> 0:58:34.160
<v Speaker 1>they are a kinmaker and yeah.

0:58:34.000 --> 0:58:36.120
<v Speaker 2>But they're also going to be the king loser. I

0:58:36.160 --> 0:58:38.200
<v Speaker 2>think by the end of this just it kind of

0:58:38.680 --> 0:58:42.080
<v Speaker 2>it's just so fucking faster, I guess. Yeah, it's so

0:58:42.360 --> 0:58:45.040
<v Speaker 2>fucking frustrating as well, because I feel like if we'd

0:58:45.040 --> 0:58:47.000
<v Speaker 2>have slowed this down in twenty twenty four, we could

0:58:47.000 --> 0:58:49.440
<v Speaker 2>have avoided this. But everyone was like, no, we need

0:58:49.520 --> 0:58:52.040
<v Speaker 2>to go further and harder and faster and spend even

0:58:52.120 --> 0:58:57.160
<v Speaker 2>bigger more amounts. But one final question, surely with the

0:58:57.240 --> 0:58:59.840
<v Speaker 2>increase in high band with me, like, actually, maybe it's

0:58:59.840 --> 0:59:02.800
<v Speaker 2>two questions in one. The memory companies are kind of

0:59:03.480 --> 0:59:05.840
<v Speaker 2>have Nvidia over a barrel too, don't they.

0:59:07.120 --> 0:59:12.800
<v Speaker 1>Uh, in the sense that Nvidia doesn't really have alternatives.

0:59:12.880 --> 0:59:15.160
<v Speaker 1>But and Video is also heavily involved in the R

0:59:15.240 --> 0:59:18.280
<v Speaker 1>and D for all this new memory, so like they

0:59:18.320 --> 0:59:20.280
<v Speaker 1>were involved in the R and D for GDR seven

0:59:20.640 --> 0:59:24.680
<v Speaker 1>g five X and for the new HPM options and

0:59:24.840 --> 0:59:30.680
<v Speaker 1>so like over a barrel, I feel like I think

0:59:30.720 --> 0:59:33.320
<v Speaker 1>you could make that argument, but I also think that

0:59:33.880 --> 0:59:38.800
<v Speaker 1>Nvidia is more likely pulling a lot of those strains

0:59:38.920 --> 0:59:41.680
<v Speaker 1>despite being the customer to very few suppliers.

0:59:42.320 --> 0:59:45.800
<v Speaker 2>Right. But at the same time, doesn't this just mean

0:59:45.880 --> 0:59:48.240
<v Speaker 2>that in Vidio's prices are going to get linearly more

0:59:48.320 --> 0:59:49.840
<v Speaker 2>expensive the longer this goes on.

0:59:50.840 --> 0:59:54.200
<v Speaker 1>Yeah, I do think, I do think the prices go up.

0:59:54.240 --> 0:59:57.080
<v Speaker 1>I mean, we're you know, with Nvidio on the consumer

0:59:57.160 --> 0:59:58.800
<v Speaker 1>side too. You can look at that as a gauge.

0:59:59.200 --> 1:00:02.240
<v Speaker 1>They were supposed to launched their refresh of consumer GPUs

1:00:02.720 --> 1:00:06.960
<v Speaker 1>like a year ago or something almost and not quite

1:00:06.960 --> 1:00:10.000
<v Speaker 1>a year ago at close and like rumors r end

1:00:10.000 --> 1:00:11.880
<v Speaker 1>of twenty twenty five. Then it was first quarter twenty

1:00:11.920 --> 1:00:13.880
<v Speaker 1>twenty six, and then the rumors where they were all canceled.

1:00:14.320 --> 1:00:16.560
<v Speaker 1>And the reason for that is because this particular type

1:00:16.600 --> 1:00:19.480
<v Speaker 1>of refresh they call the Super series. Normally you see

1:00:19.520 --> 1:00:22.520
<v Speaker 1>an increase in memory capacity at roughly the same price,

1:00:22.920 --> 1:00:26.080
<v Speaker 1>where you see a decrease in price at the same capacity,

1:00:26.760 --> 1:00:29.480
<v Speaker 1>and right now, neither of those things as possible, and

1:00:29.600 --> 1:00:32.440
<v Speaker 1>so Nvidia hasn't shipped the card. It may come out

1:00:32.440 --> 1:00:36.720
<v Speaker 1>at some point, but for now they've delayed that indefinitely.

1:00:37.240 --> 1:00:41.000
<v Speaker 1>And so to your point, it does start to self cannibalize,

1:00:41.080 --> 1:00:44.439
<v Speaker 1>right where like they are the reason that their own

1:00:44.560 --> 1:00:46.560
<v Speaker 1>refresh for consumer can't come out.

1:00:47.440 --> 1:00:50.560
<v Speaker 2>And also but regular the cost of the things that

1:00:50.600 --> 1:00:52.840
<v Speaker 2>were already making the current generation will go up.

1:00:53.920 --> 1:00:57.320
<v Speaker 1>Yeah. Oh, the current generation has already gone up in

1:00:57.440 --> 1:01:03.280
<v Speaker 1>terms of like real world pricing, and officially they haven't

1:01:03.720 --> 1:01:06.600
<v Speaker 1>changed their MSRP from launch, you know, but it's I

1:01:06.680 --> 1:01:08.960
<v Speaker 1>mean a lot of this stuff, the fifty ninety is

1:01:10.520 --> 1:01:13.440
<v Speaker 1>I guess technically sometimes you can get them at MSRP,

1:01:13.680 --> 1:01:16.560
<v Speaker 1>but more often they're like two to.

1:01:17.160 --> 1:01:20.600
<v Speaker 2>I mean, like the aigpus Oh yeah, I mean that

1:01:20.720 --> 1:01:23.960
<v Speaker 2>I would just like, yeah, all of them will go.

1:01:24.360 --> 1:01:27.680
<v Speaker 2>It just feels at some point the money's gonna run out,

1:01:27.840 --> 1:01:30.200
<v Speaker 2>and it's the longer it goes, the worst it will get.

1:01:30.680 --> 1:01:32.560
<v Speaker 1>Well, and then you get the weird lease back stuff,

1:01:32.640 --> 1:01:34.440
<v Speaker 1>right like with Meta and the GP.

1:01:34.480 --> 1:01:38.520
<v Speaker 2>Oh yeah, and all the SPV share. What a horrible era,

1:01:39.200 --> 1:01:41.480
<v Speaker 2>truly awful, And I think that's a that's a great

1:01:41.480 --> 1:01:43.959
<v Speaker 2>place to end it for us. Steve where can people

1:01:43.960 --> 1:01:45.320
<v Speaker 2>find you what you're working on at the moment. I

1:01:45.440 --> 1:01:48.960
<v Speaker 2>know you have some sort of campaign campaign, a dystopian

1:01:49.000 --> 1:01:49.760
<v Speaker 2>campaign you want.

1:01:49.640 --> 1:01:52.080
<v Speaker 1>To Yeah, we do have our AI Dystopia coverage. We're

1:01:52.080 --> 1:01:55.040
<v Speaker 1>doing it. We have a we're trying something new. We

1:01:55.120 --> 1:01:57.400
<v Speaker 1>do these documentaries that are like three hours long, and

1:01:57.520 --> 1:01:59.240
<v Speaker 1>we're trying something new and doing a short one. So

1:01:59.320 --> 1:02:02.880
<v Speaker 1>we're doing two three minute ones coming up. And one

1:02:02.920 --> 1:02:05.120
<v Speaker 1>of them is on the hard Drive cartel, which is

1:02:05.160 --> 1:02:09.400
<v Speaker 1>pretty interesting, nice, and the other one is on this

1:02:09.640 --> 1:02:12.720
<v Speaker 1>memory class action lawsuit. We read through all one hundred

1:02:12.720 --> 1:02:15.040
<v Speaker 1>and eighteen pages of the filing and did a bunch

1:02:15.080 --> 1:02:17.280
<v Speaker 1>of history research. So those are coming up within the

1:02:17.320 --> 1:02:19.240
<v Speaker 1>next week on gamers Nexus, and.

1:02:19.280 --> 1:02:21.240
<v Speaker 2>We'll get the links in there. I don't know what

1:02:21.320 --> 1:02:23.120
<v Speaker 2>I'm going to be doing next week on the show

1:02:23.280 --> 1:02:25.280
<v Speaker 2>because I'm recording this a little early. I'll have him

1:02:25.280 --> 1:02:27.400
<v Speaker 2>on log for you on Friday, though. I have been

1:02:27.440 --> 1:02:29.600
<v Speaker 2>at Zutra on this is Better Offline. You know where

1:02:29.600 --> 1:02:31.480
<v Speaker 2>to find all my stuff will be in the links.

1:02:31.680 --> 1:02:42.320
<v Speaker 2>Thank you so much for listening. Thank you for listening

1:02:42.360 --> 1:02:43.160
<v Speaker 2>to Better Offline.

1:02:43.440 --> 1:02:45.840
<v Speaker 3>The editor and composer of the Better Offline theme song

1:02:45.920 --> 1:02:48.560
<v Speaker 3>is Matasowski. You can check out more of his music

1:02:48.600 --> 1:02:51.760
<v Speaker 3>and audio projects at Mattasowski dot com m.

1:02:51.800 --> 1:02:52.800
<v Speaker 1>A T T O.

1:02:53.080 --> 1:02:55.919
<v Speaker 2>S O w Ski dot com.

1:02:56.640 --> 1:02:59.160
<v Speaker 3>You can email me at easy at betrofline dot com

1:02:59.360 --> 1:03:01.640
<v Speaker 3>or visit Better Offline dot com to find more podcast

1:03:01.720 --> 1:03:05.040
<v Speaker 3>links and of course, my newsletter. I also really recommend

1:03:05.080 --> 1:03:07.000
<v Speaker 3>you go to chat dot Where's youread dot at to

1:03:07.080 --> 1:03:09.440
<v Speaker 3>visit the discord, and go to our slash.

1:03:09.160 --> 1:03:12.240
<v Speaker 2>Better Offline to check out I'll Reddit. Thank you so

1:03:12.400 --> 1:03:15.840
<v Speaker 2>much for listening. Better Offline is a production of cool

1:03:15.880 --> 1:03:18.640
<v Speaker 2>Zone Media. For more from cool Zone Media, visit our

1:03:18.720 --> 1:03:21.680
<v Speaker 2>website cool Zonemedia dot com, or check us out on

1:03:21.800 --> 1:03:25.320
<v Speaker 2>the iHeartRadio app, Apple Podcasts, or wherever you get your podcasts.