I can imagine a world where companies have Java legacy code but build new software in Scala to (1) ensure interoperability b/w legacy and new code on the JVM, and (2) give developers a language with more options (functional-style code, REPL)
A lot of companies in SF & NY (Yammer, Twitter, 4sq, for example) use Scala. These cities are pretty cutting-edge in language choice, and I'd imagine these practices will expand geographically as devs migrate to new places.
I'm interning at Knewton, and we have this posted up on our jobs page:
Comments
I can imagine a world where companies have Java legacy code but build new software in Scala to (1) ensure interoperability b/w legacy and new code on the JVM, and (2) give developers a language with more options (functional-style code, REPL)
A lot of companies in SF & NY (Yammer, Twitter, 4sq, for example) use Scala. These cities are pretty cutting-edge in language choice, and I'd imagine these practices will expand geographically as devs migrate to new places.
I'm interning at Knewton, and we have this posted up on our jobs page:
http://jobs.knewton.com/apply/xYwHXb/Software-Engineer-Scala...
and Twitter has this listing:
https://twitter.com/jobs/positions?jvi=ospeWfwL,Job
Good luck!