I went the other way, started using ruby and then switched to python because of the machine learning libraries and async frameworks. I found rails too bloated and too much magic and fell in love with minimal frameworks like tornado that i have a lot more control over. My productivity increased dramatically using tornado and flask. It seems like each of these languages have their phases to be on top, right now i am using nodejs and twitter storm for a project and i am finding it quicker to build async web services and the amount of async libraries is really helpful.
Scala is allowing access to some good java machine learning libraries and tools such as mahout, scalding, storm, akka, finagle, therefore i believe as a developer we should not define ourselves to a platform or language but we should always be curious and use the best tool for the job. I am not using tornado for my current project because nodejs had the async libraries i needed, that simple.
As business opportunities are arsing around big data, sensors and the internet of things our favourite platforms and languages are going to evolve as well.
Hi, good perspective. I've used Scala as well. Twitter held a meetup with Martin O back in 2007. At the time we started using it, the actor code was not ready for production. I think there is a lot of great activity in that space. I'm sure most of these have been addressed.
I also agree with your last statement. This is not the end of the road.
Scala is allowing access to some good java machine learning libraries and tools such as mahout, scalding, storm, akka, finagle, therefore i believe as a developer we should not define ourselves to a platform or language but we should always be curious and use the best tool for the job. I am not using tornado for my current project because nodejs had the async libraries i needed, that simple.
As business opportunities are arsing around big data, sensors and the internet of things our favourite platforms and languages are going to evolve as well.