LukeShu

> You may want that but you won't like its unsubsidised price.

I promise you I won't give a shit about the unsubsidized price.

The textfiles.com guy works at the Internet Archive.

"<-chan TYPE" is the receive end, "chan<- TYPE" is the send end, "chan TYPE" without an arrow can be used for either.

close() on a chan is "indicate end-of-transmission"; you should only ever use it from the send end. There is no way to explicitly "close" the receive end.

You can use `select` to do a non-blocking sends/receives, but yeah normal sends/receives are blocking.

> a premium price tag?

$0.80 in bulk. Around $1.25 for individual quantities, depending on who your reseller is.

AIUI, the CPU cores are a small fraction of the die area compared to all the peripherals on the chip.

But those weren't on "IBM PC"-compatibles, just older micros? The 5150 had 5¼" drives. That is: (Q|MS|PC)-DOS never supported 8" floppies, right?

Several of the peripherals in the RP2350 are also ARM IP.

Luke Wren works at Raspberry Pi and designed the Hazard3 CPU core that is in the RP2350 chip.

It was not. It was implemented by Dylan Taylor, an outside contributor who works at a fintech company in North Carolina, and has made it his hobby to submit PRs implementing age verification to all kinds of projects. The systemd maintainer who clicked "merge" (Luca Boccassi) does work at Microsoft.

NB that you could already add your own freeform fields; it just added that field to userdbctl and friends.

GCC has `[[gnu::musttail]] return`.

But yes, framing TCO as an optimization is unfortunate.

    type IntBox struct { v int }
    type StrBox struct { v string }

    func (b IntBox) MapToStr(f func(int) string) StrBox {
        return StrBox{v: f(b.v)}
    }

(Please forgive any typos I made on mobile.)

It wasn't a great example because "Box" isn't really a useful type. But the point is that you no longer need to define a separate "MapToXXX" method for every type you might want to map to; now you can have just one type-generic "Map" method.

> along with their style of development: patches onto mailing lists

I mean that's also Git's style of development.

I'm surprised to see that it's OK that he has opensource AHB/APB stuff in it--I'd avoided learning them too much about them assuming that they were ARM proprietary.

I mean no disrespect to Luke Wren, but he did not write it in 2026; he wrote it in 2018-2021. :)

I think "ASIC design" engineer is under-selling him--he's working on their CPU cores too!