HackerTubewatch
Surprise me
Frame from My Framework Investment Should NOT Have Worked Out Plays via YouTube's privacy-enhanced embed

My Framework Investment Should NOT Have Worked Out

32 videos recommended on HN
YouTube
Cited on HN 5 times, 2025, never outright recommended score 0
Years with an HN recommendation, 2007–2026

Used as a source for the Framework CEO's explanation of why the desktop's memory could not be socketed or modular.

Linus Tech Tips covers Framework's newly announced devices, including its first desktop, with comments from Framework's CEO about the company's design decisions.

“This sort-of-interview of Nirav Patel (ceo of framework) explains in a bit more detail” (HN, 2025)

5 citations · News · news from the time

5 Hacker News comments

From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.

@jeroenhd Aug 2025 Cites it
on HN thread The Framework Desktop is a beast
Read more
According to the Framework CEO on the Linus Tech Tips video about this thing [1], they tried and AMD assigned an engineer on getting modular memory to work and decided it's not possible. Unless there's another company out there shipping this CPU with replaceable memory, I'll believe them. Even with LPCAMM, physics just doesn't work out. Of course, there are plenty of slower desktops you can buy where all the memory can be swapped out. If you want a repairable desktop like that, you're not stuck with Framework in the same way you would be with laptops. You'll probably struggle to get the same memory bandwidth to make full use of AMD's chips, though. [1]: [this video]
CEO explains why modular memory was not possible.
@komali2 Aug 2025 Cites it
on HN thread The Framework Desktop is a beast
Read more
As stated previously, the sockets reduce signal integrity, which doesn't necessarily make them "bad," but is why Framework wasn't able to used socketed ram to maximize the potential of this CPU. This sort-of-interview of Nirav Patel (ceo of framework) explains in a bit more detail: [this video] Basically, they need to use LPDDR5X memory, which isn't available in socketed form, because of signal integrity reasons. Which means you won't see an improvement if you solder your ram directly, I think mostly because your home soldering job will suffer signal integrity issues, but also because your RAM isn't LPCAMM and isn't spread across a 256 bit bus.
Framework CEO explains why socketed RAM was not feasible.
@daemonologist Sep 2025 Cites it
on HN thread How to make the Framework Desktop run even quieter
Read more
I agree, but here's a quote from the CEO explaining (to some degree) the choice: “So we did actually ask AMD about this the first time they told us about Strix Halo. It was literally our first question: ‘How do we get modular memory? We are Framework after all.’ And they didn’t say no actually, they did assign one of their technical architects to really really go deep on this—they ran simulations, they ran studies, and they just determined it’s not possible with Strix Halo to do LPCAMM. The signal integrity doesn’t work out because of how that memory’s fanning out over the 256-bit bus.” (from [this video] via [link] )
CEO quote on why LPCAMM does not work with Strix Halo.

Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.

Keyboard shortcuts

/
Search
j k
Next / previous video
r
Surprise me
l
Like (video page)
w
Watch later (video page)
?
This help
Esc
Close