4 ms·
To me it comes down to usage: if given a problem X you are likely to chose language Y to solve it, then Y is viable. That sentence probably sounds super obvious
by slx26 9y ago
To me it comes down to usage: if given a problem X you are likely to chose language Y to solve it, then Y is viable. That sentence probably sounds super obvious, ok. The important point is realizing that the critical question there is: Am I likely to chose language Y? And realizing that the answer doesn't depend on popularity. For a general-purpose language popularity is probably a big factor, but for other languages that shine in solving particular problems it might not be very relevant. The question, as I say, is: is there any scenario where I would chose this language over other alternatives? If the answer is yes, then I'd say the language is viable.
- stonemetal 9y agoPopularity to a certain extent is a prerequisite for viability. Given problem X, and given that language Y is the most suitable language to solve problem X, how likely are you to chose language Y to solve it? If you are unaware of language Y's existence? If you have heard of Y on a internet forum but have seen zero lines of language Y code? If you have written 10 lines of language Y but you are the only dev at your company to have done so, and all other code at your company is written in Z? The more popular Y is the easier it is to choose, not because we are pop culture, popularity hounds but because popularity conveys certain benefits. Libraries and infrastructure, documentation and blogs, knowledge in other people on the team. That is why large companies are able to so successfully produce new languages, they are able to pay people to convey those benefits without the chicken and egg problem of natural growth popularity. For an interesting example of this D is almost the same age as C#(2001 vs 2000). D had to grow its user base and tools organically vs C# hitting the ground with thousands of devs working on an in it full time.