I think instead they should have had dynamic keycaps like this: https://fluxkeyboard.com. Then we could have helper icons for shortcuts per app when you hold the cmd key down. But it would obviously be much cooler if all the keys had the ability to change their look rather than just the top row.
This is exactly why I'm considering it. It sounds super useful to feel the drag gestures while developing. Same with website testing when they are meant to be used on a phone/tablet mostly.
Many people working at frontier labs came out this week with estimates of 10% chance of catastrophic harm or greater. I’m not in the full doomer camp, but it seems obvious that these agents can hack in swarms, cooperate, and serious companies will be unable to stop it.
These facts are not in debate and none of us need to anthropomorphize to know what getting admin access to HF and an internal OpenAI cluster looks like.
> Many people working at frontier labs came out this week with estimates of 10% chance of catastrophic harm or greater.
The only reason people with P(Doom) of around 10% are even noticed these days because we've run out of new voices in the field giving 50%+ P(Doom) speculations (none of them are grounded enough to reasonably be referred to as "estimates".)
Probabilities are subjective states of belief! They have always been subjective states of belief! There is no such thing as a "probability" out there in the real world (ignoring random quantum stuff, which isn't what anybody is talking about). If you took out a coin right now and flipped it, the true odds of it coming up heads are not 50%, but those are (roughly) the correct betting odds for an external observer to assign to it.
> Our team at DX analyzed engineering velocity from November 2024 to February 2026
In my experience Claude Code only really started to be really strong in December 2025 and most people didn’t notice/adopt it until Opus 4.6, which launched in Feb 2026. So I’d expect quite a different result if measure since then.
It seems clear that AI can port libraries at will to any other language. So even if we disagree on which language should win, the best libraries will be ported regardless.
Each has their benefits:
Python wins in AI and syntax niceties. Loses on perf and library migration. uv (written in rust) saved the whole ecosystem from dying in my opinion.
Typescript wins because web integration, much better type system, ok perf, and gigantic npm ecosystem. Also loses on library migration and perf and large container sizes.
Go wins on compile speed, perf, standard library l, module system, and go fmt + never breaking compatibility being a massive LLM advantage. Main con is not being rust :)
Rust wins on perf, safety, syntax, wasm / sandboxing. think worse on module system and compile speed vs Go.
Java/Kotlan/C# are in enterprise land and probably the runtime approach is flawed for the ai eras.
C++ is strangely relevant because choosing c++ is easier than before. I tried writing a shared library in rust and then trivially converted it to c++ when I wanted
Zig is up and coming but also has an unknown future. Seems like a great language, but if bun switches to rust it might be set back a bit.
reply