5 ms·
It might be that way where you work, but that's definitely not the case here. In fact, I think what you suggest would be an extremely short-sighted "strategy"
by kvalle 7y ago
It might be that way where you work, but that's definitely not the case here.
In fact, I think what you suggest would be an extremely short-sighted "strategy" for a consultancy. Sure, you might get the next contract working this way. But once the customer could get rid of you they would, and they would never hire you again.
- roschdal 7y agoThen please answer why Elm was chosen instead of some mainstream programming language/framework. Choosing Elm seems like a very risky choice for something as important as railways.
- Skinney 7y agoElm is a frontend language. Java works on the backend. At Vy, Elm is used for frontend, Java and Kotlin for backend.
- roschdal 7y agoThis doesn't address the issue of mainstream technology, versus bleeding-edge, obscure, niche technology such as Elm. Kotlin in the backend isn't a mainstream technology choice either.
- Skinney 7y agoElm was chosen because we believed it to be a better language than those which are mainstream right now. We believed it would make us more productive, prevent bugs before they reached production, be better at local reasoning and make it easier to onboard new people. So far we are not dissapointed, and in my opinion Elm is on its way to become mainstream because of these things.