Too many of these are quibbles about minor language warts and constructs that shouldn't be used in the first place. For example:
Python: There is no "do ... until <condition>". Most languages don't have this either.
C#: i++.ToString works, but ++i.ToString does not. When would you ever need this?
Ruby: Suffix-conditions after whole blocks of code. Just don't do that.
Java: unused keywords, such as goto and const. Do you really need to name your variables goto and const?
Some criticisms do point out fundamental limitations and flaws, but most of the time this is by design and the solution is to use a different language. For instance, C has manual memory management, Python uses indentation for nesting, and Haskell uses lazy evaluation. Only a few are potential fixes in future language versions or forks (e.g. HashMap literals for Java... which I thought had been introduced in version 8, but I guess not).
Python: There is no "do ... until <condition>". Most languages don't have this either.
C#: i++.ToString works, but ++i.ToString does not. When would you ever need this?
Ruby: Suffix-conditions after whole blocks of code. Just don't do that.
Java: unused keywords, such as goto and const. Do you really need to name your variables goto and const?
Some criticisms do point out fundamental limitations and flaws, but most of the time this is by design and the solution is to use a different language. For instance, C has manual memory management, Python uses indentation for nesting, and Haskell uses lazy evaluation. Only a few are potential fixes in future language versions or forks (e.g. HashMap literals for Java... which I thought had been introduced in version 8, but I guess not).