Brad

@doublefree.dev

The ability to do shared-memory concurrency imposes a massive burden on the ecosystem, because everyone keeps having to ask "is this dependency thread-safe". Most languages should just stick to message passing and the actor model (99% of the time, it's a better way to build software anyway)

`pub(...)` was a mistake: `pub` should mean `pub(crate)` and there should be `export` or similar to mean current `pub`. Nothing else. If you need more than that, then your crate is too big.

“There’s a tidal wave coming. You can see it. We can all see it. Are you going to lay down and die, or are you going to do something about it?” Be ready to patch your systems, repeatedly, for at least the next 12 months.

Yael Grauer@yaelwrites.com · 3mo ago

What happens when amateur hackers have the tools to iterate through exploits at machine speed? I wrote about the neu script kiddies, what happens after Mythos, and how companies can prepare. www.theverge.com/ai-artificia.... with insight from @k8em0.bsky.social Dan Guido, Joshua Saxe, & Tim Becker.

LLM-explanation is now live in @compiler-explorer.com - An example: compiler-explorer.com/z/rvvx7MxKq * LLMs make mistakes and are overconfident * We'll never force LLMs or AI on you, it's opt in (like clang-tidy, PVS Studio or other tools) * It is *beta* quality Initial results are promising(1/3)

Compiler Explorer - C++ (x86-64 clang 21.1.0)

// setup constexpr auto valid_chars = "0123456789abcdef"; bool is_valid_id(std::string_view maybe_id) { if (maybe_id.size() != 16) { return false; } if (maybe_id.find_first_not_of(valid_ch...

explain.compiler-explorer.com