I just read the whole thing, the post would be even better if it includes an example for concurrency. It's not easy to imagine it just by looking at the binary search's example.
Ive been using Rust with LLMs for the past 2 years already. It's just amazing, I can't really think anything else to code with. Normally, been testing my codes unit tests + integration tests where necessary. But, I will take a look at this seriously.
I don't think this is a sarcasm, as a long standing Rust user myself, I don't think the community should preach out by "memory safety" -- rather the structural change in coding mindset and new ideas such as ADT and generic programming, while retaining mostly zero-cost like C++ without the bearing of C++ complexity (that includes a compiler that spits out 300 lines of compiler error just because I missed one <).
Memory safety is just what Rust inherited from C++ smart pointers with a stronger linear/affine type system twist, especially regarding move semantics, cloning and borrowing rules. What makes it powerful is the various language features it also incorporated from Cilk/C#/OCaml/Haskell.
Right now Rust and Zig is my two favourite middle ground. It is sad that Zig went completely sod-off-to-LLM mode but the most devastating aspect of Zig is that it is way too Linux focused. A lot of the code in Zig I cannot compile on Windows, plus the major changes to IO interface and the colorless function fiasco is really making me question the stability of Zig.
This recent event led me to displace Zig and replaced it with Nim, which emits C code instead and having a really powerful algebraic language system, while getting some benefits of Rust such as scoped smart pointer (I think they call it ORC), or using simple mark and sweep arena collector or even full-blown Boehm GC.
Right now I'm trying to create a distribution of Nim in a single binary (with musl and mingw packed together) and using tcc as the backend, all in a single binary with Rust and an internal project to convert wasm 3.0 and wasi proposal 1 modules into Rust code, which the Nim compiler and TCC are both compiled to WASIp1 first, then term-rewritten/transpiled to Rust (think w2c2 or wasm2c, but targets Rust, I found some nice structuralism of Rust and wasm lately)
In the long term we are all dead. But I think you mean that VW fleet electrification effort is dead. Which is not true either. You're underestimating the willingness of people in Europe to buy domestically produced cars. Even if they are not the state of the art from the perspective of picking up the latest EV technology. Don't forget the new china propagated LFP batteries are not better than the already existing NMCs. They may be cheaper, NMCs got cheaper too.
Sure, but that was before European manufacturers started making already-installed seat heating a subscription service, started selling your data - including location - to anyone willing to pay, released EVs which were 5+ years behind Chinese options, and sold them at well over 2x the cost of the alternatives. Oh, and a huge chunk of those "European" brands aren't even European anymore.
Most Europeans happily pay a premium for a well-engineered semi-local product, as we saw with the German manufacturers during the ICE era. But paying significantly more for a significantly worse product, just for that "Made in Europe" label? Not happening.
VW & friends don't even seem to be aware yet that they are in a fight for survival, and that's what is dooming them. They are more interested in lobbying for tariffs and EV rollout slowdowns than in actually building EVs.
reply