As someone who pad thai’d himself into a food coma all through the 90s, I don’t think that year is accurate

"I have a decent fluency in LLMs, and they have utility, but the absurd degree of over-hype, the way they're being forced on everyone, and the insistence on ignoring the many valid critiques about them make it very difficult to focus on legitimate uses where they might add value."

Apparently they used a very particular lens that creates that effect ymcinema.com/2025/01/13/t...

Not again lol

Right! A buffer needs a way to track its lifetime, which is often implemented via a class. A noncopyable struct can do that same lifetime management without the possibility of multiple references, which means exclusivity checking should be done statically

Some of those sound hard to do without classes! But maybe noncopyable types can help in those cases. I think eliminating the access tracking can end up helping both in the cost of the checks _and_ unlocking more ways for the optimizer to do its job
in opening

Just a casual 2.6x boost in performance

Inspired by the talk, and a few spare hours to kill, a nice 2.6x boost in SwiftTerm performance: github.com/migueldeicaz...

Learn how to optimize your Swift code with new language ehnancements from @nnnnnnnn.bsky.social in Improve memory usage and performance with Swift

developer.apple.com/videos/play/...

#swift #swiftlang #wwdc

nice

Here's the quote in context. It's good advice! But it's clear about how you absolutely need to spend time on that 3%.

Key is to get your project into a state where you can continuously identify the 3% whenever you add new code.