Postcards from the Peak of Complexity by Brian Goetz

If java had such a principle, right now we would be in a mess of having async-await code everywhere in our libraries just for IO calls. This would have introduced colour functions that are constraining or hard to debug, even if you get assistance from an IDE :) As a matter of fact, Zig is actually trying to fight this by redesigning its IO again. Python saw java made the right choice and they want to also introduce virtual threads too because most of its core library is not IO compatible. It just shows careful planning and implementing features should be done properly. And honestly, this should take it's time, and what I really want now for my project is value types proposed by Valhalla. I s…

> Zig is "worse is better", and Rust is "do the right thing". I sort of see where you're trying to go there, but I disagree. Doing the right thing essentially means doing the utmost not to compromise on what's right for the user, but that's not what Rust does. In fact, the original "wrose is better" article says that "doing the right thing" means, among other thigs, that "It is more important for the interface to be simple than the implementation"; does that sound like Rust? Rust is full of compromises on user experience and interface simplicity, it just doesn't compromise on some principles (such as memory safety) which are axiomatically declared to be "the right thing, at any cost". If an…