He recommends reading offline and code-free first (although chapter-by-chapter).

https://github.com/rasbt/LLMs-from-scratch/blob/cdbd33e6d57a...

The American dream is alive and kicking.

https://chromium.googlesource.com/chromium/src/+/main/docs/s...

If you use a safe language like Rust, you can afford untrusted input and no sandboxing.

If you use an unsafe language such as C++, you must chose between trusted inputs or sandboxing.

I was curious as to where rfgplk's implementation lay within the Venn diagram.

https://github.com/aloshdenny/open-dlss

Maybe I'm being too harsh.. on the plus side the system has at least failed hard every time there's been a fault. Nobody has died. But it's been 3 times now in the past couple of years, and two of those times resulted in over 2000 flights cancelled and days of backlog, and misery for hundreds of thousands. It's really not acceptable.

Well, that's comforting to know.

BBC: "Flight chaos caused by software defect in space of a millisecond, report says"

Sky: "'Millisecond' software error caused air traffic outage that grounded thousands of flights"

The Guardian: "Flight chaos for hundreds of thousands was caused in ‘millisecond’ by software error"

Sounds like pure bad luck.

[1] https://news.ycombinator.com/item?id=37461695

[1] https://github.com/zelikos/davincibox

[sharing reflections on his journey from MIT graduate to Apple executive to OpenAI Chief Hardware Officer as part of the Distinguished Speaker series hosted by the School of Engineering]

[https://thetech.com/2025/10/30/tang-tan-openai]

I just tried to Google it and their AI responded with "The NHS and social care account for roughly half (49%) of all day-to-day public service spending controlled by the Westminster government.", linking me to a report from the The King's Fund [1].

But on reading that report, it seems to say only that 49.5% is the cost of staffing the NHS from its own budget, which it states as £205 billion in 2024/25 - that's more like 20% of the year's public spending [2]. Which seems more in line with what I had assumed.

[1] https://www.kingsfund.org.uk/insight-and-analysis/data-and-c...

[2] https://obr.uk/docs/dlm_uploads/BriefGuide-M23.pdf

I would guess the codec limitation might come from licensing requirements, as BMD would need to pay for h264/h265 licenses for Linux, and that can't really be sustainable for a free product. MacOS and Windows already come with licensed system codecs.

My project had ProRes source media, so there was no codec issue and everything worked very smoothly. I exported ProRes and used ffmpeg to transcode to whatever I needed.

I don't think I would have bothered trying to run Resolve on Linux were it not for finding that davincibox script. It was incredibly straightforward to install, and now I just start it by clicking on an icon like a regular application.

Have fun!

I was really impressed by how well it worked for me on Linux.

I think these things might have helped:

- I use an X11 desktop (Cinnamon), not Wayland. I've tried it out on a GNOME Wayland desktop but it seemed quite a bit more clunky and froze frequently.

- PipeWire runs the system's audio routing, so Resolve just appears as another ALSA client, and I can then use wiremix to send to my preferred speakers or headphones. (I haven't tried any audio input yet)

- I didn't try to install Resolve natively, I used davincibox [1] to install and update it within a container (it uses distrobox, which then uses podman).

I'll now be purchasing the studio version, which hopefully will work as well.

[1] https://github.com/zelikos/davincibox