It's great to see battery life improving so much with the Pro, but it's good to note that the existing Framework 13 was already improving before this. I bought mine with the 12th-gen Intel Core i7, and the battery life was absolutely miserable - I couldn't get more than two hours. Last year I upgraded to the Ryzen 9 HX 370, and my battery life immediately tripled!

MetaComputing recently released an ARM mainboard for the Framework 13.

Check out Jeff Geerling's YouTube review.

The parts are mostly compatible with the existing Framework 13. There's a chart on the website that shows what isn't, and how you can work around it:

https://frame.work/laptop13pro?tab=upgrade-to-pro

Basically, if you want the new larger battery, you need the new bottom cover, because it is machined differently to make sure there is room for the battery. And if you want the new bottom cover, you also need the new top (input) cover. Also if you want the new keyboard and/or touchpad, you need the new top cover. (And every generation of mainboard has its own non-swappable heatsink and fan) But everything else is compatible.

Personally, I'm looking forward to the new keyboard and top cover - I tend to press very hard when I type, and I can feel the flex in the old one.

Until now, kernel compilation left some room for portability between different processors within the same family. For example, you could build the kernel on an Intel processor and then run it on an AMD processor, or switch between different generations of processors. By default that's still going to be true, but this option allows you to say "this kernel will only be used on this exact processor, so there's no need to keep anything for other processor, generations or brands."

Both Bulwer and Lytton are probably named for Sir Edward Bulwer-Lytton, for whom this contest was also named, and both names probably date back to shortly after Queensland was created by splitting it off from New South Wales; Bulwer-Lytton was Secretary of State for the Colonies at the time.

Who is saying that? Not the comment you replied to:

---

Right now, this looks like it should be one of the most powerful mini-ITX boards that I can find on the market. I suspect MINISFORUM and others will have similar boards available soon, but right now they don't.

The whole point of Framework is that they make it very easy to buy exactly the parts you need. If you want specific parts, they will be available in the marketplace later in the year, and you can buy exactly which ones you want. If you don't want any of their parts, you're clearly not the target market.

The first I ever saw measuring in liters was the rise of the "1-liter PC" like the aforementioned Lenovo ThinkCentre "Tiny" series, the HP Elite "Mini" series, the Dell Optiplex "Micro" series, the Intel "NUC" series, etc. ServeTheHome has a great series of articles about this form factor, which they call "Project TinyMiniMicro".

Companies have been specifying chassis volume in liters for smaller desktop PCs for many years (doing a quick search found references 10 years ago), since it's an easy way to compare the size of all small form-factor (SFF) PCs, not just the tiny ones described above. But I think it's become more popular along with TinyMiniMicro-type projects, since mid-2020.

I was disappointed to see the soldered RAM, but the fact that it's a standard mini-ITX form factor means that you can use their motherboard in other cases if you care about the power supply being non-standard, or other motherboards in their case if you care about the soldered RAM.

Most of the desktops that I use these days are the "1 liter" PCs, such as the Lenovo ThinkCentre Tiny, but those are 100% proprietary parts other than the RAM and SSD. If I had a place where I needed a more powerful system and wasn't space limited, I would probably consider this machine.

I have a first generation Asus Chromebook that lost official updates several years ago. However, there's a version of ChromeOS called ChromeOS Flex that is specifically designed for installing on your own hardware, and it runs on Old Chromebooks just fine. I still get updates, and it still works great. The battery even still lasts for several hours. The only downside to an old Chromebook is that 2 GB of RAM is not enough to have a lot of browser tabs open at once.

Someone probably asked ChatGPT (or any other of its ilk) to help collect quotes for the trailer.

He said "we've decided to waive our right to arbitration". That means they still think that they are legally allowed to force this into arbitration, and are only making a one-time exception due to the negative publicity of this case. I guess that's a fair warning to anyone else who will ever have major trouble in a Disney park in the future.

I have accounts at Capital One (because they acquired my local bank 15 years ago), and with Discover (opened around the same time). Discover customer service has always been incredible, and Capital One has always been garbage. I have no doubt that Capital One's first move will be to bring Discover down to Capital One's existing level.

There is at least one model of toothbrush I find online that has a Wi-Fi connected base station. (I didn't look for more models once I saw that one exists, so I don't know how many others there might be.) It boasts of having Alexa integration ... though I can't imagine what the point of that is.

the inability for either side just to simply ask the user to replace the ratty USB cable

Actually, just today I plugged my Google Pixel 6 into my Toyota Sienna and the Pixel popped up a notification that said something to the effect of "this cable may be broken, and you may have issues with Android Auto, we suggest you get a new cable."

It then worked perfectly for the next 20 minutes, until I moved my phone a little bit and it got disconnected. I have no idea what it was detecting, but it was clearly correct.

and that customers tend to blame the automaker rather than the phone manufacturer or phone software.

I've used Android Auto in vehicles made by Toyota, GM, Chrysler, and several aftermarket units. The Toyota and aftermarket units worked perfectly, while the GM and Chrysler units had major trouble. I've spoken to family members and friends who say the same thing - some infotainment system makers have done a much better job than others at implementing Android Auto. (I have not tested Apple Carplay.)

When GM says "Android Auto has bugs", they really just mean they can't be troubled to implement it well.