I don't really understand what #RustLang's Cell<T> looks like at runtime. Does it still exist? Presumably it depends on T—something like: If T is on the heap, then Cell<T> is a pointer, but if T is Copy then Cell<T> is pretty much erased?
If you have an OSS project written in #C or #CPP, and people keep suggesting you add #Rust to the codebase, you should take that as a compliment, IMO. What they're saying is "I value this piece of software so much that I think it could be relevant for decades. I want to take steps to ensure the next generation of devs can keep this project alive." Deep down, this constant push to rewrite things in Rust is as much about fear of loss as it is about safety.
@5150cec1@c8c5c50e EdgeDB is running on Postgres’ engine, but with a (dramatically better, IMO) new query language. Even though it was originally written in Python, the devs appear to be writing new bits in Rust, and from their public discussions about it, have plans to gradually rewrite a lot of their implementation in Rust over time. I think the Postgres engine itself will stay untouched for a long time, given the scale of effort required.
Oddbean new post about login | logout
Notes by Dusty Pomerleau | export