I'd argue pretty small. I primarily work in a language out of the APL family. When I first started it, the entire reference page of every function/command/fla

I'd argue pretty small. I primarily work in a language out of the APL family. When I first started it, the entire reference page of every function/command/flag fit on a double sided printout in regular sized font. Past a certain point you just end up with overlapping versions of the same thing maintained for backward compatibility or slight differences of opinion & behaviour. I feel the same way about framework ecosystems. Some languages almost have too many, to the point that they are constantly being introduced, changed in ways that make old code non-portable, and then sunsetted. It's hard to keep internal corporate software running when if you choose something mainstream it's less than 5 years from EOL, but if you choose something emerging it may never go mainstream. A lot of it seems like reinventing the wheel.