Would you mind elaborating on which aspects of the language reflect poor design? And what was done well for that matter?
I have no strong opinions on Solidity, btw - just generally interested in people's views on developer experience.
I have no strong opinions on Solidity, btw - just generally interested in people's views on developer experience.
1) There's no need for a garbage collector, because there's very limited computation within each transaction, and complete cleanup of non-permanent storage after each one.
2) The author doesn't appear to realize that the list of mis-compilation bugs is a list of fixed bugs. The list is only available in json because its purpose is just to let tools display warnings for obsolete compilers.
3) I have a hard time dreaming up an application that would need a string library in Solidity, because storage on chain is very expensive, and you only need to compute things on chain that require global consensus. Strings on chain are usually very short and static; for longer stuff we just store their hashes on chain and use client code to manipulate the strings.