I don't see problem with growing languages as long as designers are doing their job. There's difference between adding features randomly and putting effort int

I don't see problem with growing languages as long as designers are doing their job. There's difference between adding features randomly and putting effort into making it obvious, transparent, integrated well into the ecosystem and overall UX. UX is something that languages and API designers must put more effort into. Start creating APIs with assumption that people have no access to documentation - it makes everybody's life easier. Just take a look at .NET BCL - it's very well designed. They even wrote a book about framework / libraries design basing on their decades of experience.[0] Also "small language" is relative. If you have started doing X lang development decade ago then that version of language is "small" to your perception. For somebody who started 5 years ago it was small 5 years ago. The point is that at every point language have some features which aren't popular because they serve some specific cases which are required for somebody. Very often those features are required for base class libraries makers so they can create either good API, or have good performance/safety, or anything else. For me it seems like programming languages and its ecosystems lack of deprecation process which actually removes stuff. [0] - Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .Net Libraries