Nim also has top notch meta programming, probably more so than Zig. You can easily do loop unrolling, specialization, etc. For example Constantine, which is a constant time crypto library that outperforms C, etc.
To me programming Rust feels so limiting due to lack of good compile time meta programming with types. That’s the key.
Yesterday I did some testing on the cost to solve the same simple problem on openrouter with different models using cline. Simple problem but it had a few nuances to solve it properly and so required reasoning.
After reading comments like this I was expecting (hoping?) that DeepSeek or similar would be cheaper.
However I was surprised that DeepSeek v4 cost about 5.5x GPT-5.4 to solve the problem.
That doesn't sound right. Were you using the actual Deepseek provider? The one time I spent 3 dollars on Deepseek in a day, I had 615k output tokens, 96M cache hit input tokens, and 5M cache miss output tokens.
> FBI deputy director Paul Abbate called Crooks's activity on social networking services antisemitic, anti-immigrant, extreme, and espousing political violence.
It has some pluses, I miss an updated version of "The Design and Implementation of the FreeBSD Operating System", but it is understable there are other priorities and putting such a book out is lots of work for very little money, given how much book authoring gives back.
For me it's all about Nim + LLMs. I'm greedy and want both fast-to-ship and fast-to-run? Readability comparable to Python but with strict static typing that LLMs can't "cheat".
I actually (mostly) enjoy reading the code that the LLMs create in Nim. It's quick to read and look for refactor or cleanups. Compile times in seconds so the LLMs is usually the slow piece. It's fun and productive. With Python + LLMs I'm seeing them just create ever more layers of unmanageable cruft.
Recently I wanted "magic" behavior to get OpenAPI types and swagger.json along with auto parsing my rest APIs for me. I had Codex make a library for me using compile time reflection and a sprinkling of macros. Done, simple.
You'll also need to just chop New York into two and split the city off. NYC data skews the rest of the state so hard...
(north country anectedote: we leave our doors unlocked and laptops, keys, wallets, and iphones straight up in plain view in parking lots up here in rural nowhere. people are dumb.)
The idea of having a non-crap Siri on my phone that I could interrogate directly would be amazing.
My ADHD brain would love to do this stuff:
"Hey AI, how much is my electric bill this month?" and "Okay thats high. Pay it but remind me next week to order a new AC after researching options for me."
Do you recall which libraries? Use of nightly fell of a cliff after 2018. Looking at the bottom of https://lib.rs/stats#rustc-usage, ~8% of all crates.io requests came from a nightly newer than that corresponding to 1.86. That's am upper bound, as using a nightly compiler doesn't mean that a nightly compiler was needed. The prevalence of nightly is also niche specific. If you're in embedded it is likely you need to use some nightly-only features that haven't been stabilized, but if you have an OS chances are that you don't.
> That's am upper bound, as using a nightly compiler doesn't mean that a nightly compiler was needed.
To be fair it's not even a lower bound, as using a stable compiler doesn't imply the absence of nightly only feature (as in Cargo features, the ones you can enable on crates you depend on).
For the purposes of this discussion the question is not whether or not a crate exposes optional features that require a nightly compiler, but whether or not a crate makes use of the nightly compiler mandatory, which has become extremely rare in my experience. Perhaps it's more common in some embedded use cases, but if people want to make that assertion, I would ask that they either mention which libraries they're specifically talking about or which nightly features they're specifically referring to.
I think the divide is apps vs libraries: a library that requires their dependants to set an environment variable opting out of stability guarantees is unlikely to gain adoption, but applications that do so are more common, like Firefox.
> For the purposes of this discussion the question is not whether or not a crate exposes optional features that require a nightly compiler, but whether or not a crate makes use of the nightly compiler mandatory
In my opinion what matters is the functionality. If it's provided by a nightly-only crate or as a nightly-only feature of an otherwise non-nightly-only crate it doesn't really matter.
But I agree that this is become more and more rare.
Finding myself in the awkward position of defending Saudi Arabia here, but this is not at all a consensus of the political analysis community.
Relying on statements by the Trump administration as proof of this makes it even more spurious.
That said, MBS has done worse and it's not impossible, but alignment with UAE is faltering more and more so it's possible even if they once favored that action by the US they no longer hold the same view.
I am not claiming Saudis want what's best for the region, only that, even if they wanted war with Iran, they likely now no longer do, or at least would like the conflict to wrap up due to the heavy costs its inflicted on the region.
UAE will see the the whole region burn if it means MBZ can keep his seat.
Sure, but the Saudi Crown prince comments seem reasonable, and don’t seem to have been denied by the Saudi’s
Regardless, my point was that people have a political axe to grind and call this “Israel’s war”.
They intentionally ignore the political realities that the Iranians have pissed off almost everyone in the region and the longstanding tension of the IRGC and the US and our new “Cold War” with China.
To me programming Rust feels so limiting due to lack of good compile time meta programming with types. That’s the key.
reply