Hey everyone, welcome back to My Weird Prompts. I am Corn, and I am joined as always by my brother.
Herman Poppleberry here. It is good to be back in the studio, especially after such a fascinating prompt from Daniel. It is February twenty-second, twenty-twenty-six, and the landscape of the technology we are discussing today has shifted so much even in just the last few years.
Yeah, Daniel's prompt today really hits on something we have touched on before, but from a much more personal and practical angle. He has been tinkering with servers, using artificial intelligence to help him rebuild and salvage parts, and that led him down this rabbit hole of modularity and the right to repair. Specifically, he wants to talk about the Framework Laptop project and how it compares to the desktop experience he is used to.
It is such a timely topic. We talk about sustainability and electronics waste a lot, but seeing a company actually try to build a business model around longevity instead of planned obsolescence is rare. Daniel mentioned that frustration with manufacturers cluttering stock Android with their own ecosystems, and that same philosophy of control and ownership is what drives the interest in Framework. It is the "anti-black-box" movement.
Right, and as a desktop user, Daniel is skeptical. He is used to being able to swap out a power supply unit or a central processing unit whenever he wants. Laptops have historically been the opposite. You buy a slab of aluminum and silicon, and four years later, if the battery dies or you need more memory, you often have to throw the whole thing away. So, Herman, let us start with the big question. Is that lack of modularity in laptops a technical necessity, or is it just a design choice?
That is the perfect place to start. For a long time, the industry line was that to make laptops thin, light, and efficient, you had to solder everything. If you want a device that is less than fifteen millimeters thick, you cannot really have bulky sockets for the random access memory or the storage. Sockets take up vertical space, what engineers call the Z-height. Soldering components directly to the motherboard allows for a much tighter layout and better thermal management in a cramped space because you can put heat pipes directly over the chips without a socket in the way.
But is that actually true, or is it just a convenient excuse for original equipment manufacturers to force you into a new purchase? I mean, we have seen laptops get thinner and thinner, but at what cost to the user?
It is a bit of both. There is a genuine engineering challenge in making things modular while keeping them portable. But as Framework has shown, it is not an impossible challenge. It is a choice of priorities. Most manufacturers prioritize a one-millimeter reduction in thickness over the ability for a user to swap their own battery. Framework decided to prioritize the user's ability to repair and upgrade, even if it meant the laptop was a tiny bit thicker than the thinnest MacBook Air. They proved that the "necessity" of soldering was actually just a preference for aesthetics and manufacturing margins.
So let us talk about the Framework project specifically. How long has this been going on? Because it feels like they have suddenly become the poster child for this movement.
They really have. The company was founded in early twenty-twenty by Nirav Patel, who was actually one of the founding members of Oculus. He saw the waste in the consumer electronics industry and wanted to create a "longevity" company. They launched their first product, the Framework Laptop thirteen, in twenty-twenty-one. Since then, they have expanded into a sixteen-inch model and have gone through several generations of processor upgrades, from the eleventh-generation Intel chips all the way up to the latest Core Ultra and AMD Ryzen series we are seeing here in early twenty-twenty-six. What makes them different is that they did not just make a laptop that is easy to open. They made a laptop that is designed to be changed.
I love that distinction. Most laptops are built to be assembled once in a factory. If you open them, you are fighting against glue, proprietary screws, and fragile ribbon cables. How does Framework actually handle the modularity? Daniel mentioned the "configure once, upgrade whenever" philosophy.
The core of the Framework design is the Expansion Card system. This is probably the most visible and clever part of the laptop. Instead of having a fixed set of ports on the side of the laptop, like two Universal Serial Bus type C ports and one High-Definition Multimedia Interface port, the laptop has four or six recessed bays. You buy these little expansion cards that are essentially specialized dongles that slide into the chassis and sit flush. They use a USB-C interface internally to connect to the mainboard.
So if I want four USB-C ports today, but tomorrow I realize I need a DisplayPort and a microSD card reader, I just swap the cards?
Exactly. You just push a button, slide the old one out, and slide the new one in. No tools required for that part. It solves that classic laptop problem where you are stuck with whatever ports were popular the year you bought the machine. If a new standard comes out, like the newer high-speed SD Express cards we are seeing now, you just buy a twenty-dollar card instead of a two-thousand-dollar laptop. They even have community-made cards now, like tiny LED matrices or even a miniature drawer to hold your spare SIM cards.
That is the external stuff, though. Daniel's experience with his server was about the internal components. He mentioned the power supply unit, the central processing unit, and the random access memory. How does Framework compare to a desktop build in that regard?
This is where it gets really interesting for someone like Daniel. In a standard desktop, you have a motherboard, and you plug the CPU into a socket, the RAM into slots, and the storage into M-dot-two or SATA ports. In the Framework Laptop thirteen, the RAM and the storage are exactly like a desktop. They use standard SO-DIMM slots for memory and a standard M-dot-two slot for the solid-state drive. You can buy the laptop as a DIY edition, which comes without those parts, and you can bring your own, just like Daniel did with his server.
Wait, so I can just go to a computer store, buy a stick of RAM, and it will work? No proprietary "Framework-certified" memory?
Exactly. It is standard off-the-shelf hardware. Now, there is a new standard called CAMM-two that some manufacturers are starting to use in twenty-twenty-six, which is thinner than SO-DIMM but still replaceable. Framework has been watching that closely, but for now, they stick to the most accessible standards. The CPU, however, is where it differs from a desktop. In the laptop world, almost all modern mobile processors are what we call BGA, or Ball Grid Array. They are soldered directly to the motherboard. You cannot just pop a laptop CPU out of a socket like you can on a desktop motherboard because the sockets themselves would be too thick for a portable device.
So if the CPU is soldered, how does Framework claim it is upgradable? That sounds like a contradiction.
They make the entire mainboard swappable. The mainboard contains the CPU, the cooling system, and the interface for all the other components. When a new generation of Intel or AMD processors comes out, Framework releases a new mainboard. You unscrew the old one, move your RAM and storage over to the new one, and screw it back into the same chassis. It is essentially a "brain transplant" for your computer.
That sounds like a lot of waste, though. If I am replacing the whole motherboard just to get a new CPU, am I really being more sustainable than just buying a new laptop?
That is a great question, and it is something Framework thought about from the beginning. When you upgrade your mainboard, you are left with a perfectly functional, albeit older, computer-on-a-board. Framework actually released the design files for a small case that you can 3D print, or buy from them, that turns that old mainboard into a standalone small-form-factor desktop computer. They even partnered with Cooler Master to make a high-quality version of this case.
Oh, that is brilliant! So your old laptop guts become a home server, or a media center for your TV, while your laptop gets the brand-new brain. That perfectly matches Daniel's server-building hobby.
Exactly. It mirrors Daniel's experience of salvaging parts. Nothing has to go to the landfill as long as the silicon is still functional. You are essentially cascading the technology down to less demanding roles in your home. And because the mainboard has all the ports via those expansion cards, it is a very capable little desktop. In fact, some people buy just the mainboard to use as a controller for arcade cabinets or custom robotics.
Let us talk about the comparison Daniel made to the power supply unit. In a desktop, the PSU is this big box with a bunch of cables. In a laptop, it is usually an external brick and then some internal power delivery circuitry. Is that part modular too?
In the Framework, the battery is very easy to replace. It is just a few screws and one connector. No glue. Most laptops today glue the battery to the underside of the keyboard or the trackpad, making it a nightmare to change. The internal power delivery is part of the mainboard, so that is not as modular as a desktop PSU, but the charging port itself is just one of those expansion cards. If you break your charging port by tripping over the cable, you just swap a twenty-dollar USB-C expansion card instead of having to solder a new port onto a motherboard or replace the whole machine.
That is a huge relief. I cannot tell you how many people I know who have retired a perfectly good laptop because the charging port got loose or broken. It is such a small part to cause such a big failure.
It is one of the most common failure points. Now, Daniel also mentioned the Framework Laptop sixteen. This is their newer, larger model, and it takes the modularity even further. It actually has a modular graphics processing unit.
Wait, a modular GPU in a laptop? That has been the holy grail for gaming laptop users for decades. Most of the time, the GPU is the first thing to become obsolete. How do they pull that off?
They created something called the Expansion Bay. It is a large interface on the back of the laptop where you can slide in different modules. One of those modules is a dedicated graphics card. If you want a thin and light workstation, you can put a shell in there. If you want to play the latest games, you slide in the GPU module. And in a few years, when that GPU is struggling, you can just buy the next generation module and slide it in. They have even talked about modules that could hold dual M-dot-two drives for massive storage arrays.
Is there a standard for that, or is that a Framework-only thing? Because the history of modular laptop GPUs is littered with failed proprietary standards. I remember Alienware and Dell trying things like this years ago with MXM modules.
You are right to be skeptical. Historically, those projects failed because the manufacturers did not stay committed to the platform. Framework is trying to solve this by making the specifications for that interface open. They want other companies to build modules for it. We are starting to see some niche manufacturers experiment with this. Imagine a module that adds an extra battery, or specialized hardware for audio production with full-sized XLR inputs, or even scientific computing modules.
That sounds incredible, but I want to push back a bit on the "how it works" part. Daniel is a desktop user. In a desktop, everything is standardized. ATX motherboards fit in ATX cases. CPUs fit into specific sockets. How do we know Framework will be around in five years to sell us the next mainboard? If the company goes under, does the modularity just become a gimmick?
That is the ultimate risk with any new platform. If Framework disappears, you are stuck with the hardware you have. However, because they use so many standard parts, like the RAM, storage, and even the display connectors, you are still in a better position than you would be with a MacBook or a soldered-shut Windows laptop. You can still source those parts from anywhere. And because they have released the schematics and the 3D files, the community could, in theory, keep making parts or adapters. They even have a partnership with a company called DeepComputing that released a RISC-V mainboard for the Framework chassis. That means even if the original company stopped making Intel boards, other companies can step in with entirely different architectures.
That is a big deal for the right to repair movement. Speaking of which, Daniel mentioned the battery episode and how that led him here. One thing most people do not realize about laptops is that the manufacturer often makes it impossible to get replacement parts even if you are a skilled technician.
Exactly. It is what we call "parts pairing" or "software locking." Some companies will make it so that if you swap a screen from one identical laptop to another, the software will disable certain features like brightness control or face recognition because it does not recognize the unique serial number of the new part. Framework is the exact opposite. They have QR codes on every single component. You scan the code with your phone, and it takes you directly to a step-by-step repair guide and a link to buy that specific part in their marketplace. They even sell "Factory Seconds" parts at a discount—parts that have minor cosmetic issues but work perfectly—to reduce waste further.
That is such a refreshing approach. It is almost like they are encouraging you to break it just so you can see how easy it is to fix. It reminds me of the old days of radio kits.
They actually ship the laptop with a screwdriver! It is the only tool you need to completely disassemble the entire machine. It is a dual-ended tool with a Torx T-five bit and a spudger. They are literally giving you the keys to the castle.
Let us go back to Daniel's point about the "cluttered stock Android" and the ecosystem problem. He mentioned how manufacturers add their own layers to the operating system. How does Framework handle the software side? Is there a "Framework OS" that we have to worry about?
No, and that is one of the things Daniel would love. Because it is built for the DIY community, they are very friendly to whatever operating system you want to run. If you buy the DIY edition, it comes with no OS installed. You can install a clean version of Windows without any of the bloatware from companies like Acer or HP. But where they really shine is their Linux support. They work closely with distributions like Fedora and Ubuntu to make sure all the drivers work perfectly out of the box. They even have a dedicated Linux lead on their team to ensure that the firmware is compatible with the kernel.
So it really is a "clean slate" experience. You are not fighting against the manufacturer's desire to sell you a cloud subscription or a trial version of antivirus software.
Not at all. It is your hardware. You bought it, you own it, you decide what runs on it. It is very much in the spirit of the desktop building experience. No "McAfee" pop-ups on day one.
I want to talk about the physical reality of upgrading. Daniel asked how the process compares to replacing components in a desktop. Let us walk through a scenario. Say I have a Framework Laptop thirteen with an eleventh-generation Intel processor, and I want to upgrade to the latest Core Ultra chip. What does that actually look like for the user?
It is surprisingly simple, but it is more involved than just clicking a button. First, you would back up your data, although your storage drive is not actually changing. You use the included screwdriver to remove five captive screws on the bottom. Captive screws are great because they stay in the chassis and do not fall out and roll under your desk. The keyboard and trackpad assembly, which they call the Input Cover, is held on by magnets and one ribbon cable. You lift that off, and the entire inside of the laptop is exposed.
No plastic clips that snap off if you pull too hard? I hate that sound of snapping plastic.
None. It is a very clean, metallic interface. Once you are inside, you see the mainboard. You unplug the display cable, the battery cable, and the speakers. You unscrew the mainboard, lift it out, and then you do the reverse with the new board. You move your RAM sticks and your M-dot-two SSD over to the new board, screw it back in, and put the keyboard back on. The whole process takes maybe fifteen to twenty minutes if you are being careful.
Compared to a desktop motherboard swap, that actually sounds easier. In a desktop, you are dealing with a dozen different power cables, tiny front-panel connectors that are impossible to see, and mounting the heavy cooling fan with thermal paste.
Exactly. Because the Framework is designed as a single system, the cable management is already solved. Everything is exactly where it needs to be. The thermal paste is already pre-applied to the CPU under the heatsink on the new mainboard. It is much more like building a high-end Lego set than the sometimes-frustrating experience of fishing cables through a desktop case.
What about the cost? Daniel mentioned the financial aspect of his server build. Building a server from salvaged parts is obviously cheaper than buying a new one. Is a Framework Laptop a good deal financially, or are you paying a premium for the modularity?
That is the trade-off. If you just look at the raw specifications versus the price on day one, a Framework is usually more expensive than a comparable laptop from a big manufacturer like Dell or Lenovo. Those companies have massive economies of scale. They buy parts by the millions. Framework is a smaller player, and they are building in extra costs for the high-quality connectors and the modular design.
But you have to look at the total cost of ownership over time, right?
Precisely. If you buy a thousand-dollar laptop and it lasts three years because the battery dies or the CPU gets too slow, your cost is three hundred and thirty-three dollars a year. If you buy a Framework for twelve hundred dollars, but in three years you only spend five hundred dollars on a new mainboard instead of twelve hundred on a whole new laptop, you are starting to save money. And in six or nine years, the savings become very significant. Plus, the resale value of the parts is higher. You can sell your old mainboard to someone who wants to build a home server, which offsets your upgrade cost.
It is like the difference between buying a fast-fashion shirt and a well-made pair of boots that can be resoled. The initial investment is higher, but the long-term value is much better.
And then there is the sustainability angle Daniel mentioned. The most environmentally friendly computer is the one you already own. By only replacing the parts that are actually obsolete, like the processor, and keeping the screen, the aluminum chassis, the keyboard, and the speakers, you are drastically reducing the amount of electronic waste you generate. The chassis is made of seventy-five percent post-consumer recycled aluminum, and the speakers are made from thirty percent recycled plastic.
I wonder about the display, though. In a desktop, your monitor is separate. You can keep a great monitor for ten years while you go through three different computers. In a laptop, the screen is attached. Can I upgrade the screen on a Framework?
Yes! They recently released a new two-point-eight-K resolution display with a one-hundred-and-twenty-hertz refresh rate and much higher brightness. If you have the original model with the sixty-hertz screen, you can just buy the new screen, unscrew the bezel, which is also held on by magnets, and swap the display panel. It uses a standard forty-pin eDP connector. They even have a matte screen option if you hate reflections.
That is incredible. They are essentially decoupling the different lifecycles of computer components. The screen might last six years, the keyboard four years, and the CPU three years. You can replace each one on its own schedule.
It is the first time we have seen this work at scale in a laptop form factor. Now, there are some downsides that Daniel should be aware of. Because it is modular, it is not as structurally rigid as a unibody MacBook carved out of a single block of aluminum. There is a little bit more flex in the chassis because it has to be able to come apart. It is still very sturdy—made of milled aluminum—but it does not have that "hewn from a single rock" feel.
That makes sense. You lose some of that "industrial jewel" feel in exchange for the utility.
And the battery life, while good, often lags slightly behind the very best integrated laptops. When you have a modular system, you have more connectors and more separate components, which can lead to slightly higher power draw than a highly optimized, fully integrated system-on-a-chip like Apple's M-series. In those systems, the RAM is literally on the same package as the CPU, which is incredibly efficient but impossible to repair.
That is a fair trade-off for many people, especially those like Daniel who are coming from the desktop world where "thin and light" isn't the primary goal.
Exactly. For a desktop user, a laptop that is slightly thicker but fully repairable feels like a miracle, not a compromise. Now, I want to talk about how Daniel used AI to help him with his server. That is a huge part of this new "maker" era.
Right, he mentioned that AI helped him rebuild and salvage parts. How do you see AI playing into the Framework or modularity ecosystem?
It is a game changer for troubleshooting. Imagine you are trying to upgrade your mainboard and something goes wrong. Instead of searching through forums for hours, you can feed a photo of your motherboard to a multimodal AI and ask, "Is this ribbon cable seated correctly?" Or you can ask it to parse the technical schematics that Framework provides to find the exact voltage of a specific pin. It lowers the barrier to entry for people who are intimidated by hardware.
So the AI acts like a digital mentor, sitting over your shoulder while you work on your laptop.
Precisely. It can help you find compatible parts on the secondary market or even help you write the code for a custom expansion card. If Daniel wanted to build a custom sensor for his server and integrate it into his laptop, an AI could help him design the circuit board and write the firmware. We are moving away from "consumer" and toward "creator" in a very real way.
You know, what strikes me about Daniel's prompt is how it reflects a shift in how we think about our relationship with technology. For the last twenty years, we have been moving toward a "black box" model. You buy a device, you use it, you don't understand how it works, and when it fails, you give it back to the company or throw it away. Daniel rebuilding a server with AI is the opposite of that. It is taking back control.
It really is. And the Framework project is the hardware equivalent of that mindset. It is saying that the user is capable and should be allowed to understand and modify their own tools. There is a certain psychological satisfaction in knowing exactly what is inside your machine. If it starts making a weird noise, you don't have to take it to a "Genius Bar" and wait a week for them to tell you it can't be fixed. You just open it up and look. You are the master of your own silicon.
I want to touch on the "misconception busting" part of our show. One thing I often hear is that modular electronics are "too complicated for the average person." People say, "Oh, my mom could never swap a mainboard." What do you think about that, Herman?
I think that is a patronizing view of users. No, maybe not everyone wants to swap a mainboard. But everyone wants to be able to fix a cracked screen or a dead battery. By making the "hard" stuff possible, Framework has made the "easy" stuff incredibly simple. My mom might not want to upgrade her CPU, but she could definitely slide in a different expansion card to get an HDMI port for a presentation. And if she did need a repair, she could take it to any local shop, and they would be able to fix it in minutes because the documentation is open.
And even if you don't do the repair yourself, the modularity makes it easier for a local repair shop to do it for you. They don't have to spend three hours fighting through glue just to get to the battery. That lowers the cost of repair for everyone and supports local businesses instead of just the manufacturer's authorized service centers.
Absolutely. It supports a whole ecosystem of local technicians. Now, Daniel also asked about how long this has been going. We are currently about five years into the Framework journey. The big test for them is happening right now: can they maintain the compatibility across many more years? So far, they have been incredibly consistent. A mainboard from twenty-twenty-six fits into a chassis from twenty-twenty-one. That is a level of commitment we haven't seen in the tech industry in a long time. Usually, companies change the screw layout or the connector type every two years just to force you to buy a new case.
It reminds me of the old ThinkPads, back before they were bought by Lenovo. They had a reputation for being tanks that you could fix with a single screwdriver. Framework feels like the spiritual successor to that, but modernized for the thin-and-light era.
It really does. And for someone like Daniel, who is already comfortable with server hardware and using AI to guide him through complex tasks, a Framework laptop would be a playground. Imagine using an AI to help you design your own custom expansion card. Since the specs for the expansion cards are open-source and available on GitHub, you could literally build a specialized piece of hardware that fits into your laptop's port.
Wait, people are actually doing that? I thought you were just being theoretical.
Oh, people are definitely doing it. The community has made all sorts of weird expansion cards. There is one that is a tiny vacuum cleaner for your keyboard. There is one that adds an old-school serial port for industrial equipment. There is even one that has a tiny OLED screen to show your system stats or a scrolling marquee. Because the interface is just USB-C, anything you can dream of can be turned into a card. It is the ultimate expression of "weird prompts" in hardware form.
That is the ultimate "weird prompt" right there. "Design me a laptop port that does something nobody else's does." I love the idea of a tiny vacuum card.
Exactly! So, Daniel, to answer your question about whether laptops are inherently un-upgradable: the answer is a resounding no. They were made that way by corporate choice, not by the laws of physics. Framework has proven that you can have a modern, high-performance laptop that respects the user's right to tinker, repair, and upgrade. It is a desktop experience in a portable form factor.
It feels like we are at a bit of a turning point. With the European Union passing new laws about battery replaceability—which are set to take full effect by twenty-twenty-seven—and the right to repair gaining momentum in the United States with states like Oregon and Minnesota passing strong laws, even the big manufacturers are starting to take notice.
They are. We are seeing companies like Valve with the Steam Deck making parts available through iFixit, or even some of the newer Dell models making the battery screws more accessible. But Framework is the only one who has built their entire identity around it. They aren't doing it because a law told them to; they are doing it because they think it is a better way to build computers. They are leading by example.
I think that is a perfect place to wrap up the technical side of this. Daniel, your experience with the server is exactly the kind of "maker" energy that keeps this show going. Reusing hardware and finding new ways to make it work with the help of modern tools like AI is the perfect blend of old-school sustainability and new-school tech. It is about being a participant in your technology rather than just a consumer of it.
And if you do end up getting a Framework, let us know how that upgrade process feels compared to your desktop. I would love to hear if it actually satisfies that itch to tinker. I suspect that once you realize you can swap the keyboard for one with a different layout or change the color of the screen bezel in thirty seconds, you will be hooked.
Definitely. Before we go, I want to remind everyone that if you are enjoying these deep dives into the weird and wonderful world of tech and human-AI collaboration, we would really appreciate it if you could leave us a review on your podcast app or on Spotify. It genuinely helps other curious people find the show and keeps us motivated to keep digging into these prompts.
It really does. We love seeing the community grow and hearing your perspectives on these topics. We have been doing this for a while now, and the prompts just keep getting better and more complex.
You can find all of our past episodes, including the one on batteries and the right to repair that Daniel mentioned, at myweirdprompts.com. We have an RSS feed there for subscribers and a contact form if you want to get in touch with your own weird prompt. You can also reach us directly at show at myweirdprompts dot com.
We are available on Spotify, Apple Podcasts, and pretty much everywhere you listen to podcasts. We try to keep the website updated with links to the tools and projects we discuss, so check the show notes for links to the Framework marketplace and the Cooler Master mainboard case.
Thanks again to Daniel for sending in such a great prompt. It gave us a chance to look at the future of the devices we use every day and how we can make them last a lifetime instead of just a few years.
Until next time, I am Herman Poppleberry.
And I am Corn. This has been My Weird Prompts. Thanks for listening, and we will talk to you in the next one.
Goodbye everyone! Keep tinkering!
