A startup's primary focus should be getting the product out and getting customers. The language should be something that you are comfortable with, unless it is critical to the success of the product, in which case you should hire people who know it already. Can you clarify why you think that you have time to learn?
Learning to be able to write functional code will not be enough. You need to be an expert in it - the kind of expertise that is gained with years of writing code in it, knowing debugging techniques as second nature, idiosyncrasies and best practices, where your productivity in the language has reached peak levels and you don't have to think of how to do something in the language, and can focus on solving the problem for the business.
This is more true of languages than of frameworks or tools.
One exception I've found in practice is Go, which being a simple language, can be picked up rather readily. Early code isn't idiomatic but still fairly readable and maintainable. Python could be another which make sense in order to use a simple framework such as Flask or possibly Django. Scala would be on the other end of the spectrum and a definite no no.
3 comments
[ 4.1 ms ] story [ 18.0 ms ] threadIf one gets used to breaking changes and gets to know the inner bits of ones language and libraries and it's less risky.
If one is using very complex stacks and hoping/waiting for other people to fix things, it's much more risky.
Learning to be able to write functional code will not be enough. You need to be an expert in it - the kind of expertise that is gained with years of writing code in it, knowing debugging techniques as second nature, idiosyncrasies and best practices, where your productivity in the language has reached peak levels and you don't have to think of how to do something in the language, and can focus on solving the problem for the business.
This is more true of languages than of frameworks or tools.