Apache resigns from the Java Community Process executive committee

> Speaking as someone who wrote a (toy) compiler once, the big problem in optimizing C/C++ is the "aliasing problem"-- the difficulty of determining if a location in memory has been modified since it was last fetched from memory.

> From what I've read, the general idea in Go (and presumably Rust as well) is "don't communicate by sharing memory, share memory by communicating."

That's true, but the aliasing problem is only the big problem since a lot of other stuff isn't possible. Rust, for example, makes everything immutable by default, which opens up entirely new avenues for optimization that aren't available in C/C++, Java, Go, C#, etc. Whereas functional languages like Haskell make very good use of immutability in their optimizations.