Scala，未来的Java（？） [英] Scala, the java of the future(?)
问题描述
我想弄清楚scala的受欢迎程度以及有多少SO用户在工作场所实际使用它？
I'm trying to figure out the popularity of scala and how many SO users actually use it in the workplace?
- 以下是一些scala链接
- Here are some scala links
推荐答案
我一直在使用Scala工作一年（财务技术）并且不想要完全回到Java！最初考虑迁移时最关心的事情是：
I've been using Scala for a year now at work (finance technology) and would not want to move back to Java at all! The things that concerned me most when originally considering the migration were:
- 工具支持（IDE是什么样的？）
- 与现有Java库和构建技术互操作（
ant， Spring ，内部编写的东西） - 人才库（我在哪里可以找到优秀的scala开发人员？）
- 转换时间（在我写好 scala之前多久？）
- Tool Support (what are the IDE's like?)
- Interop with existing Java libraries and build technologies (
ant, Spring, internally-written stuff) - Talent Pool (where do I find good scala developers?)
- Transition-time (how long before I'm writing good scala?)
我发现IDEA的scala插件（用于现在免费的v9社区版）非常出色：不如Java的工具支持那么好当然足以满足我们的需求。它具有基本的重构和调试功能以及出色的语法突出显示功能。我对 Eclipse 的体验非常令人失望：我已经明白scala 2.8预计会有很大改进，但我我见过最近的Eclipse-nightly，坦率地说，这很糟糕。
I found that IDEA's scala plugin (for the now free v9 Community Edition) is excellent: not quite as good as Java's tool support but certainly good enough for our needs. It has basic refactoring and debugging and great syntax-highlighting. My experience with Eclipse has been extremely disappointing: I'm led to understand that great improvement is expected for scala 2.8 but I've seen a recent Eclipse-nightly and it was, frankly, awful.
与Java的互操作性是一流的 - 我没有任何问题，仍然大量使用Spring和我们的定制（基于蚂蚁）构建系统。对于员工流动率从中到高的大公司来说，开发人员库只是一个考虑因素;到目前为止，它对我们来说并不是一个问题，并且受访者表示有兴趣使用Scala。
The interoperability with Java is first-rate - I have had no problems whatsoever and still make heavy use of Spring and our bespoke (ant-based) build-system. The developer-pool is only a consideration for a large company with moderate-to-high staff turnover; it has not been an issue for us so far and interviewees have expressed interest in using Scala anyway.
也许最大的问题是过渡时间。我发现这可能是2周时间才能写出任何合理的东西，3个月到开始真正得到它和6个月 - 1年开始利用功能和DSL-斯卡拉的两面。那么，对我来说真正的大收获是什么呢？
Perhaps the biggest issue is transition-time. I've found this to be 2 weeks to being able to write anything reasonable, 3 months to start to really "get it" and 6 months-1 year to start taking advantage of the functional and DSL-sides of Scala. So, what are the really big gains for me?
- 内置类型推理和共同和反向差异（代码更具可读性和直观 - 泛型只是工作，与Java不同，它可能非常痛苦）
- 功能编程风格和闭包（代码更易读，写得更快）
- actor并发库（大大简化了并发编程）
- Type inference and co- and contra-variance built in (code is more readable and intuitive - generics just works, unlike Java where it can be extremely painful)
- Functional Programming style and closures (code is more readable and quicker to write)
- The actors concurrency library (simplifies concurrent programming hugely)
所以得出结论：
- scala有什么好处吗？ 是 - 它太棒了
- 是否已准备好使用真正的企业？ 是 - 现在有很多同行使用它，包括Twitter，索尼和EDF
- 这些收益是否值得采用成本？ 是 - 绝对
- Is scala any good? Yes - it's fantastic
- Is it ready for real enterprise use? Yes - there are quite a few compaies using it now, including Twitter, Sony and EDF
- Are the gains worth the adoption cost? Yes - absolutely
这篇关于Scala，未来的Java（？）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
