

That’s an… impressively small sales number.


That’s an… impressively small sales number.


I anticipate that ICEatzgruppen will just ignore this, like they have ignored countless other rulings.


“Expert advice”

Ah that’s what I meant, oops
Oh wait, it did? TIL. LPCAMM, or SODIMMs?
The “s” means it’s a tiny bit thinner and lighter, but the components are soldered on so you can’t upgrade anything.
One of the big selling points of the newest T14 is that it is probably the most modular and repairable modern laptop you can get, except for Frameworks.
Get the non-s if you care even a little bit about that part.


CVE aside, that headline is phonetically amusing


- On the idea of a kill switch: while I said that we won’t add a “global kill switch”, all of these capabilities will be delivered as Snaps to the OS, layered on top of the existing Ubuntu stack. That means there will always be the option of removing those Snaps - which I suppose acts as a sort of kill switch for the features we’re planning on shipping.
- Opt-in vs Opt-out: my plan is to introduce AI-backed features as a “preview” on a strictly opt-in basis in 26.10. In subsequent releases, my plan is to have a step in the initial setup wizard that allows the user to choose whether or not they’d like the AI-native features enabled. Because of the size of most LLMs, we simply couldn’t ship them in the installer anyway, so opting out at first run is simple: they just won’t be there.
Point of order: “you can easily remove the Snaps from your install” is an opt-out mechanism. Calling these features “opt-in” is gaslighting.


Well, what I mean is that the Dell models you’d find at Best Buy or Fnac or whatever the big tech retail chain is in your country are almost certainly not sold with Ubuntu, so you need to both know that that’s a thing you can get, as well as look for it. Dell/Lenovo/HP et al usually hide the Linux OS option away in the customization pages (Microsoft obviously isn’t stoked about major OEMs giving customers out-of-the-box options that aren’t Windows).


FW13 pro is apparently pretty great in terms of hardware and build quality.
But I also agree that Thinkpads are the absolute tits. Those keyboards are absolute legends. And apparently the new generation of the T series was designed specifically to be super repairable by end-users - not as holistically modular as framework, but WAY better than pretty much any other somewhat-recently-manufactured laptop.


I mean… the target audience is rather different, I think. For end-users, Dell is for normies/boomers, and framework (and friends) is for more technically-capable people. And even in the enterprise setting, Dell is aimed much more at Big Corporate that buy lots in the thousands or tens of thousands with gigantic depo maintenance contracts, whereas framework seems much more oriented towards leaner/more modern companies who are comfortable with a thinner level of warranty support (send back broken main boards and so on for a swap, but do the hardware maintenance yourself because it’s super easy). They’re competitors, but I wouldn’t necessarily call them direct competitors.


I keep having impulses to quit my job, find an old lathe and milling machine, and just do metalworking things and brew beer until I retire. The siren song beckons.


disturbingly pervasive shuffling noises intensify


Suck my Huang, Huang.


I feel like you’re way too invested in whatever hill you’re trying to die on here, and nobody else understands what you’re doing either.


What’s your endgame here? What are you trying to do? Are you an energy vampire, or do you just enjoy being a pointlessly argumentative pithy nonce?



It’s somewhat deeper than that: the ethos of “move fast/break things” came about during the explosion of tech startups in the last decade and a half or so, where being first to market was the pass/fail condition of getting any valuation whatsoever for your startup. It’s an approach that works for some domains (I would argue that those domains tend to be less technically interesting and rigorous, but I digress).
There were some organizations that pointedly too the opposite route, and operated much closer to “build it once and build it right” - to wit, the original iteration of WhatsApp (before it was subsumed and ruined by Meta) was built that way, and that’s specifically one of the reasons why it was so good for so long and gained such a massive userbase.
Anyways: applying “move fast/break things” and all of the idiotic, caustic “engineering leadership” koans that spring from that font of misprioritization and useless metrics is now and will continue to cause the art and serious practice of software engineering to get whittled away bit by bit. The only places where you CAN’T do that these days is in highly regulated contexts (aero/defense; biotech; medical; other similarly regulated fields), but even that is starting to crack.