Let's try to reply at DH6. The point I have an issue with is this: > The third illusion: ecosystem is the most important for a language > There's only one tr

Let's try to reply at DH6. The point I have an issue with is this: > The third illusion: ecosystem is the most important for a language > There's only one true ecosystem, the C ecosystem. The dynamic language modules are just the bindings of the existing C libraries. Not all software projects are created equal. If I have to do something quickly, having a wealth of libraries a pip install away is definitely going to be a major factor. For example, I'm in the paradoxical situation where one of the languages I use the most is Python, also one of the languages I like the least. I'd say there are two cases: - If the project is small enough, the ecosystem is in fact the most important factor. Yes, maybe those libraries are just C FFI, but reimplementing the FFI when somebody has already done the hard part for you is simply uneconomical. - If the project is big enough to warrant being 'properly engineered', then you probably have a laundry list of requirements, and language, ecosystem, etc. have to be weighed against everything else.