craftkiller

> I hope framework lives up to its promise, but I don't see that happening any time soon.

That's already happened? I started with an 11th gen Intel tigerlake laptop with DDR4 memory and a glossy screen. I upgraded to the AMD 7040 with DDR5 memory when I destroyed my Intel board with a soldering iron, skipping the Intel 12th gen iteration in between and the AMD AI 300 generation after the 7040.

I upgraded my screen from the glossy to the matte screen, I skipped the 120hz rounded corner screen, and now I'm likely upgrading to the new screen released for the FW13 pro. I upgraded my wifi card to a card supporting wifi 7 and my SSD to a 2TB SSD.

I upgraded my hinges from the original 3.5kg to the 4.0kg hinges. I upgraded my top cover from the original to the CNC version.

So far all of these upgrades have been completely interchangeable. I could have done any combination of those upgrades (with the exception that the ram had to be upgraded at the same time as the motherboard because the ram slots are on the motherboard).

At this point, the only original parts remaining in my laptop are the battery, the bezel, and the metal clip that goes over the wifi card antenna connectors. My laptop is literally the ship of theseus, something that has not been possible in laptops before framework.

Based on these announcements, most of the new framework 13 pro upgrades are also completely interchangeable, the one exception being the bigger battery and the bottom cover need to be upgraded together but I could upgrade the input cover without upgrading the bottom cover and battery if I wanted.

Personally, I'm planning on taking my existing AMD 7040 board and dropping it into a completely new framework 13 pro chassis because I've already invested in 96GB of ram for this board. Since I'm going to get the whole pro chassis, I'll sadly have to replace my original 55Wh battery, but they can pry my bezel and metal wifi antenna clip from my cold dead hands!

The AMD board support USB4 40gbps in 2 of the 4 expansion slots.

7040: https://knowledgebase.frame.work/expansion-card-functionalit...

AI 300: https://knowledgebase.frame.work/expansion-card-functionalit...

Pro with AI 300: https://knowledgebase.frame.work/expansion-card-functionalit...

The nice part about the Intel board is all 4 ports support usb4/thunderbolt 4 so all 4 ports are completely interchangeable whereas on the AMD board I need to remember to plug my dock into the back ports closer to the hinge.

Ah that could be it. My laptop mostly sits on my desk at home so there's not much opportunity for the button to get hit accidentally.

Indeed, me too! I try to show my coworkers the cool expansion card system and end up embarrassing myself, struggling to remove the card for like 10 seconds.

I've had the framework 13 since batch 5 of their original first model and that has never happened to me once. Are you sure you're pushing the expansion cards _all the way_ in? They should click and the little button between the cards should pop up slightly more when the cards are fully inserted. It is certainly possible to have the cards visually look inserted and work normally but haven't actually been pushed in far enough to click/lock into place.

FWIW I've also replaced my chassis once, and never had this issue with either chassis.

My headlamp is waterproof and it has a replaceable 18650 battery without needing to dab silicon(e?) on it. It is also rechargeable over USB type-c so I have both the option to replace the physical battery or plug it in to charge that battery.

FWIW I run llama.cpp on AMD hardware using Vulkan. I've got no complaints but also nothing else to compare against.

My top category was social security, followed by medicare. If I live long enough, I'll benefit from both of these. But regardless, these are great things to put our money towards. I'd much rather lose a couple tens of thousands per year than have our elderly dying homeless and hungry.

The next category was military which I think we can all agree that US spends too much on the military but it would be silly to claim that I don't benefit from the pax americana.

The next category was interest on debt... Which yeah... not stoked about that.

In addition, it serves as a good template for writing your own polymarket bot with whatever logic you want.

Ah well then we have a slightly different interpretation. I would read "the faults of <x>" as "the flaws of <x>", which would then imply a flaw of Linux is why aggressive anticheat doesn't work when it is just companies deciding it isn't worth their time.

FWIW, I am not alone in that interpretation since this commenter reached the same conclusion: https://news.ycombinator.com/item?id=47718389

But I don't think we can conclusively say either one of our interpretations is correct.

You didn't read the thread? It's the comment I was replying to: https://news.ycombinator.com/item?id=47718255

They quote "If a game has an aggressive anticheat" and then state "The determination of the average Linux user to ignore the faults of Linux", which is accusing Linux of being at fault for the aggressive anticheat not working.

It doesn't matter to you, but other people care about false accusations.

Aggressive anticheat not supporting Linux is not a fault of Linux. It is a fault of the aggressive anticheat and the games that decide to use it.

At this point, I'm surprised the streaming services aren't grandfathering people into their current plan+rate like the cellular networks do. It would encourage people to keep their subscription active to keep their rate rather than cancelling it and signing up again when there is a specific show they want to watch, while also avoiding the price increase frustrations.

PS: Thanks for the reminder about the price increase, just cancelled my netflix.

eh I've got 802.11be @ 6ghz at home (u7 pro AP and QCNCM865 client) and it is truly impressive, but I only notice the difference once every 1-2 years when I'm transferring a full-disk image over the network for backup. We've long passed the point where the speed improvements matter for daily usage (browsing the web, streaming video, remote desktop, installing updates). For those use cases, you wouldn't notice a slowdown on 802.11ac and I'd argue even 802.11n would be fine.

The one exception I can think of would be video content creators since they end up with large amounts of raw video that would benefit from transferring at much-faster-than-streaming speeds.

And I guess steam downloads if you don't plan ahead at all, but if I'm planning to play a game later, I'll tell steam to install it hours or days in advance.

That certainly _used_ to be the case, but it looks like 802.11ac is supported in iwlwifi since FreeBSD 14.3: https://man.freebsd.org/cgi/man.cgi?query=iwlwifi&sektion=4&...

And it looks like they're adding 802.11ac support to some realtek drivers too: https://www.freebsd.org/status/report-2025-10-2025-12/#_linu...

FreeBSD uses a compatibility layer to run the Linux graphics drivers, though it lags behind Linux. So if FreeBSD currently does not support the graphics cards, it will soon. It looks like they are currently porting over 6.11: https://github.com/FreeBSDFoundation/proj-laptop/issues/41

nit: The 9070XT is listed as $599 but that price essentially never existed. I was lucky to get one for $730.

> durability (dust, water)

Not just dust and water but folding screens are plastic with a mohs hardness of 2-3, as opposed to normal phones with glass screens which are a 6-7 hardness. I like having phones that can't be permanently damaged by pressing my fingernail a little hard into it.

Example: https://www.youtube.com/watch?v=8hgg4YEdPak&t=140s

Another example: https://www.youtube.com/watch?v=8uS90jakOuw&t=107s

I also can trivially replace the screen on my regular phone at home, whereas I'd have to get a folding phone professionally repaired for many hundreds of dollars.

> Notice how it's just Iran that's being attacked

https://en.wikipedia.org/wiki/2026_Lebanon_war

Europe is just under 2% of their GDP spent on military. Where are you getting this "0" figure? https://data.worldbank.org/indicator/MS.MIL.XPND.GD.ZS

For legacy devices, VP8/VP9 is a good option. Intel Added VP8 hardware decoding to Broadwell which was 12 years ago. Nvidia had hardware VP9 decoding 10 years ago on the Geforce 10 series. AMD had hardware VP9 decode support 9 years ago on the Radeon 400 series.

Does the US have any prisoners to exchange? Wouldn't we need boots-on-the-ground to capture enemy combatants?

Only if they're set up properly, which is quite the gamble. I was recently in a hotel and I listed all the chromecast devices throughout the entire hotel. I could see what everyone was watching and if I was a lesser person I could have controlled their TVs or changed what they were watching.

Temporary addresses are enabled by default in OSX, windows, android, and iOS. That's what, like 95% of the consumer non-server market? As for Linux, that's going to be up to each distro to decide what their defaults are. It looks like they are _not_ the default on FreeBSD, which makes sense because that OS is primarily targeting servers (even though I use it on my laptop).

There are genuine improvements in IPv6 aside from the abundance of addresses. The two that immediately come to my mind are:

1. SLAAC means routers no longer need to keep a record of each client on the network. With DHCP, the router had to maintain a table of which addresses had been assigned and getting an address involved 2-way communication. With SLAAC the router just periodically broadcasts the prefix to the network and any device that wants an address can just listen to that broadcast and assign themselves an address within that prefix without having to inform the router and without the router needing to maintain a table of assigned addresses. (2-way communication is still possible since devices can solicit a broadcast but it is not necessary)

2. With IPv6, middleboxes are no longer allowed to fragment packets. The only device that can fragment a packet is the original sender. If any segment along the path has a lower MTU than the size of the packet, the original sender is notified and then they can fragment the packet.

Privacy extensions are enabled by default on OSX, windows, android, and iOS: https://ipv6.net/guide/mastering-ipv6-a-complete-guide-chapt...

On Linux, I think the defaults are left up to the distros so there is a chance of a privacy footgun there. Hopefully most distros follow the example set by Apple and Microsoft (a sentence I never thought I would write...)

> I don’t want some of my devices to be publicly addressable at all, even if I mess up something at the firewall while updating the rules. NAT provides this by default.

Do you ever connect your laptop to any network other than your home network? For example, public wifi hotspots, hotel wifi, tech conferences, etc? If so, you need to be running a firewall _on your laptop_ anyway because your router is no longer there to save you from the other people on that network.

It's also a good idea even inside your home network, because one compromised device on your network could then lead to all your other firewall-less devices being exploited.

You can't correlate the number of addresses with the number of devices because IPv6 temporary addresses exist. If you enable temporary addresses, your computer will periodically randomly generate a new address and switch to it.

https://www.rfc-editor.org/rfc/rfc8981.html

No need to rely on app-specific configs. You can disable it globally in your fontconfig. For example, this disables ligatures in the Cascadia Code font:

  <match target="font">
    <test name="family" compare="eq" ignore-blanks="true">
      <string>Cascadia Code</string>
    </test>
    <edit name="fontfeatures" mode="append">
      <string>liga off</string>
      <string>dlig off</string>
    </edit>
  </match>

Here is someone disabling ligatures for Noto Sans Mono: https://blahg.josefsipek.net/?p=610