- About Scala
- In the Enterprise
- Scala Community
- Language Research
- In the Press
- The Scala Team
- Scala's Prehistory
- Contact Us
- Learning Scala
- Tour of Scala
- Scala API
- Setup & Getting Started
- Programming Guides
- Other Guides
- Code Examples
- Scala Developers
Re: Re: Two killer applications for Scala
Sat, 2011-06-18, 13:22
OTOH Sala might not need to proove it self that much. The relative risk of using Scala where Java is ok is rather low and need not be a strategic decison. The interoperability is so good that the official story might very well be that you are using Java, just a particular dialect.
As a data point I might add that the things holding me back from introducing Scala is
a) The tooling support before 2.9. But that part is more or less solved by now.
b) The cost/benefit ratio. The less technically interested team members will have to be taught a new syntax and will have little incentive to do so. Scala will slow them down for a while with little percieved benefit. The more technically skilled members will have a better tool to build abstractions, but even here there will be a period of learning new idioms that will incurr a cost to development. Given that the project is relatively mature there might never be a ROI for this migration.
The things that makes me concider it is:
a) Fun. Scala removes lots of friction and makes development fun again. Hard to estimate in business value but I think this leads to happier and more creative employees.
b) I suspect that there is a possibility that the migration cost actually can be offset by the higher expressibility of the language and in a surprisingly short time.
c) The REPL. I think this alone has the potential to shorten debugging time significantly enough to warrant at least including scala toolong in development. I wonder what could be done with a REPL attached to the running production system.
Sent from my phoneDen 18 jun 2011 09:15 skrev "Sergei" <hello [dot] sergei [at] gmail [dot] com>: