4 ms·
>> Ask HN: How do you architect a 30-year software project? > you labeled it a 30-year software project, which isn't what you're asking Good call - I've chang
by spiffytech 13y ago
>> Ask HN: How do you architect a 30-year software project?
> you labeled it a 30-year software project, which isn't what you're asking
Good call - I've changed the title.
What sort of evidence do you think a developer should look for to tell whether a language may become popular, rather than just plateauing with a strong, but relatively small, user base? How strong should the evidence be to justify choosing an up-and-comer over an existing major player?
- pedalpete 13y agoYou can use github as a decent judge of this I think. You're not going to find any absolutes as to the potential popularity of a language, but I'd recommend not jumping on the next new thing. Go with something that has at least a few years behind it. https://github.com/JuliaLang/julia https://github.com/JuliaLang/julia https://github.com/rails/rails https://github.com/rails/rails https://github.com/scala/scala https://github.com/scala/scala https://github.com/joyent/node https://github.com/joyent/node https://github.com/ruby/ruby https://github.com/ruby/ruby https://github.com/sinatra/sinatra https://github.com/sinatra/sinatra