Why JetBrains needs Kotlin

The question of motivation(动机) is one of the first asked when someone learns that someone else is working on a new programming language. Kotlin documentation offers a fairly(详细) detailed overview of why the language exists. Still, we would like to make it clearer what exactly(究竟) JetBrains expects to gain from the whole endeavor(努力). We’re obviously(明显的) in it for the long run, and yes, we realize(认识到) it will take years to reach(达到) our goals. And here’s why we are willing to make this investment(投资).
[collapse title=”翻译”] 当人们得知另一些人在研究一个新编程语言时,第一个被问到的问题就是动机。在Kotlin的文档中,对这种语言为什么存在提供了非常详细概述。不过,我们想弄清楚的是JetBrains究竟想通过整个努力得到什么。显然我们需要一个长时间的努力,是的,我们也意识到要达到我们的目标可能需要很多年。这就是我们为什么要进行这样的投资。

First and foremost(最重要的), it’s about our own productivity(生产力). Although we’ve developed support for several JVM-targeted programming languages, we are still writing all of our IntelliJ-based IDEs almost entirely(全部地) in Java. The IntelliJ build system is based on Groovy and Gant, some Groovy is also used for tests, there is some JRuby code in RubyMine, and that’s it. We want to become more productive by switching to a more expressive(表现力) language. At the same time(同时), we cannot accept compromises(妥协,折中方法) in terms(条款,地位) of either Java interoperability(互用性) (the new language is going to be introduced gradually(逐步地,渐渐地), and needs to interoperate smoothly(平稳的,平滑的) with the existing code base) or compilation(编辑) speed (our code base takes long enough to compile with javac, and we cannot afford(提供) making it any slower).
[collapse title=”翻译”] 首先也是最重要的,就是我们的生产力。虽然我已经开发了几种针对JVM的编程语言,而且我们仍然几乎完全使用Java写我们的基于IntelliJ的所有IDE。IntelliJ编译系统是基于Groovy和Gant,Groovy也被用于测试,在RubyMine里有一些JRuby代码,就是这样。我们想切换到一种更具表现力的语言来提高效率。同时,我们不能在与Java的交互方面(新语言在逐渐的被引入的过程中,和现有的基础代码的交互需要平稳)和编译速度方面(我们的基础代码使用javac编译时需要很长时间,我们不能让它再慢了)进行妥协.
注:in terms of 在……方面

The next thing is also fairly straightforward: we expect Kotlin to drive the sales of IntelliJ IDEA. We’re wording on a new language, but we do not plan to replace the entire ecosystem of libraries that have been built for the JVM. So you’re likely to keep using Spring and Hibernate, or other similar frameworks, in your projects built with Kotlin. And while the development tools for Kotlin itself are going to be free and open-source, the support for the enterprise development frameworks and tools will remain part of IntelliJ IDEA Ultimate, the commercial version of the IDE. And of course the framework support will be fully integrated with Kotlin.

The final point is less obvious but still important: new programming languages is a topic that many people really enjoy talking about, and the first days that have passed since we’ve unveiled Kotlin prove that. We see that people who are already familiar with JetBrains trust the company to be able to do a good job with this project. Thus, we believe that this trust and the increasing community awareness of JetBrains will not only drive the company’s business, but will attract even more people to our approach to building development tolls, and let them Develop with Pleasure.

And we’d like to reiterate that our work on Kotlin does not in any way affect our investment into other development tools, and in particular the Scala plugin. If you’re already happy with Scala and have no need for another new language, we’ll continue to do our best providing you with first-class Scala development tooling.