Every (software) company should be doing something like this. (Like the NSA told us to)
I think we can all agree that whenever Rust comes up there's a high amount of "I like to program in C/C++ and don't plan to change, thankyouverymuch"-style comments. Was there a similar backlash against the rise of Java, Swift, Kotlin, or TypeScript? Or is this somehow a unique case? Nothing is new under the sun and all that, but I can't remember similarly animated discourse before.
[flagged]
Is it safe yet?
It's so fucking safe...
Ah yes, rust. A language so "safe" that its compiler downloads shit from the internet every time you call it.
With rust I absolutely hate when they make it more complicated to do something that is already unsafe.
Great examples:
- Reference to mut static (interacting with it is already unsafe), but now you get additional warnings.
- the entire addr_of!() mess.
Things like these just make me wish I did this in c where I know I am only ever executing in a single thread.
Anyone know what this means?
> In addition, we are exploring more seamless interoperability with C++ through Carbon, as a means to accelerate even more of our transition to MSLs.
Carbon doesn’t really care about memory safety except as a vague “in the future we’ll evolve the language somehow to add more memory safety” statement. The primary goal seems to be to parse code as quickly as possible. So I’m not sure I understand how it improves the MSL story. Or is it saying that interfacing Carbon with a MSL like Rust is easier so carbon is a better bridge to MSL than things like autocxx?