562: Do You Have a Dragon?
https://atp.fm/562
OpenAI's turmoil, M3 Max thermals, keyboard wear, and the Humane Ai Pin.
562: Do You Have a Dragon?
https://atp.fm/562
OpenAI's turmoil, M3 Max thermals, keyboard wear, and the Humane Ai Pin.
@atpfm @siracusa @caseyliss @marcoarment
Did a quick size comparison of the MacBook Pro 16ā with the PowerBook G4 12ā. It blew me away that the 12 and 16 are nearly identical in weight. I remember thinking my 12ā was so tiny and lightweight twenty years ago.
MBP 16ā
90.34 cubic inches
4.7/4.8 lbs.
PowerBook 12ā
110.61 cubic inches
4.6 lbs.
PowerBook 17ā (for giggles)
157.08 cubic inches
6.9 lbs.
@frankly @atpfm @siracusa @caseyliss @marcoarment
MBP 16" (40.6 cm)
1480 cm³ (1.5l)
2132g/2177g (2.1 kg/2.2 kg)
PowerBook 12" (30.5 cm)
1813 cm³ (1.8l)
2087g (2.1kg)
PowerBook 17" (43.2 cm)
2574 cm³ (2.5l)
3130g (3.1kg)
@atpfm He was talking about the chiplet and chip-stacking architecture, which John also talked discussed soon after, where SRAM is going to be moved onto dedicated dies on older N-x nodes, then 3D stacked onto the CPU chip. The High Yield youtube channel has been making good videos about the problems with SRAM scaling:
@atpfm All while not messing up all of the transistors and layers they already made on the front! Incredible stuff.
https://www.anandtech.com/show/18894/intel-details-powervia-tech-backside-power-on-schedule-for-2024
10/10
@atpfm I haven't bought a shirt since "slaccidental tech podcast" and "butterfly" in 2019, between shipping to Australia and the exchange rate it just hurts too much (now AU$87 for one US$39 shirt).
But I would 1000% buy an "err network changed" related shirt š¤£
@atpfm the story about QUIC/H3 being at fault for ERR_NETWORK_CHANGED sounds iffy. QUIC is actually designed to cope well with network changes and the RFC describes how a QUIC connection can continue even if a network path changes (see https://www.rfc-editor.org/rfc/rfc9000.html#name-connection-migration). So if anything, QUIC connections should be more robust, not less robust, to network changes.
(I started my own QUIC implementation in Rust, https://github.com/quinn-rs/quinn, which has become decently popular.)
This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm.