语言采用是否受其可用IDE的生产力驱动?

时间:2023-02-04 17:03:03

Simply put, if the designers of a new language want it to gain adoption and interest from the largest group of programmers possible, should those designers build a highly productive(Intellisense like features to begin with) IDE to encourage the adoption of a language?

简而言之,如果一种新语言的设计者希望它能够从最大的程序员群体中获得采用和兴趣,那么这些设计师是否应该构建一个高效的(Intellisense类似功能)IDE以鼓励采用一种语言?

9 个解决方案

#1


Yes.

Even if you've created the most useful, most advanced language on the planet, there's no way I'm going to waste my time coding in it if I have to use notepad.

即使你已经创造了地球上最有用,最先进的语言,如果我不得不使用记事本,我也不会浪费时间编码。

#2


It's in the best interest of adoption to have tools available that are accessible and can automate much of the overall process. The less time it takes to do something, the more time can be spent on actual development.

拥有可访问的工具并且可以自动完成整个过程的大部分工作,这是最佳的采用方式。做事的时间越少,在实际开发上花费的时间就越多。

Cost for the IDE is the other factor that will affect management buy-in. Some places are OK with the write-off, most would prefer to keep overhead to a minimum.

IDE的成本是影响管理层支持的另一个因素。有些地方可以注销,大多数人更愿意将开销降到最低。

#3


The syntax of a new language can mostly be learned in a few hours. What takes most time and effort is to get to know the APIs. To have a good IDE with IntelliSense makes it so much easier to poke around and learn the APIs than looking up in documentation.

新语言的语法大多可以在几个小时内学会。花费大量时间和精力的是了解API。要拥有一个带有IntelliSense的良好IDE,可以比查阅文档更容易学习和学习API。

#4


History shows that the language comes first and the IDE follows. Instead of building an IDE, build the killer app (Unix, mobile code, Rails, ...).

历史表明语言是第一位的,IDE也是如此。而不是构建IDE,构建杀手级应用程序(Unix,移动代码,Rails,...)。

#5


No, the IDE should not compensate for the language's deficiencies.

不,IDE不应该补偿语言的不足。

Having said that, the IDE sells VB to customers of mine all the time.

话虽如此,IDE一直向我的客户销售VB。

So, a fancy IDE tends to sell a language. Even though it shouldn't.

因此,一个花哨的IDE倾向于销售一种语言。即使它不应该。

#6


In a word, no. How many IDEs were built for HTML? Javascript? Ruby? PHP? etc. All of these had the language come first, and the IDEs come second.

总之,没有。为HTML构建了多少个IDE? JavaScript的?红宝石? PHP?所有这些语言都是第一位的,而IDE则排在第二位。

#7


I think it's great having a good set of tools to help productivity but it's not a 'should-have'.

我认为拥有一套很好的工具可以帮助提高生产力,但这不是“应该有的”。

#8


I'll say "yes." If not the productivity of, at least the presence of an IDE will bring in IDE-lovers and is unlikely to discourage command-line or Vim enthusiasts.

我会说“是的”。如果不是生产力,至少IDE的存在将带来IDE爱好者,并且不太可能阻止命令行或Vim爱好者。

If not a full IDE, at least syntax coloring.

如果不是完整的IDE,至少是语法着色。

Evidence: Fully half the SO questions tagged Objective-J ask about syntax highlighting.

证据:标记为Objective-J的SO问题中有一半是关于语法突出显示的问题。

#9


In an environment where developers are used to good IDEs it is harder to advocate the use of a new language if some of the IDEs people are using lacks support for the language.

在开发人员习惯使用优秀IDE的环境中,如果人们使用的某些IDE缺乏对该语言的支持,则更难提倡使用新语言。

E.g. on the java platform there is a lot of new languages that could be used in conjuction with Java, like Groovy, Scala, JRuby etc. Up to now it has been a problem if you want to start using Groovy and some of the developers use Eclipse, because the Groovy support in Eclipse hasn't been that good (luckily that is changing right now).

例如。在Java平台上有很多可以与Java结合使用的新语言,比如Groovy,Scala,JRuby等。到目前为止,如果你想开始使用Groovy并且一些开发人员使用Eclipse,那么它就是一个问题。 ,因为Eclipse中的Groovy支持并不那么好(幸运的是,现在正在改变)。

#1


Yes.

Even if you've created the most useful, most advanced language on the planet, there's no way I'm going to waste my time coding in it if I have to use notepad.

即使你已经创造了地球上最有用,最先进的语言,如果我不得不使用记事本,我也不会浪费时间编码。

#2


It's in the best interest of adoption to have tools available that are accessible and can automate much of the overall process. The less time it takes to do something, the more time can be spent on actual development.

拥有可访问的工具并且可以自动完成整个过程的大部分工作,这是最佳的采用方式。做事的时间越少,在实际开发上花费的时间就越多。

Cost for the IDE is the other factor that will affect management buy-in. Some places are OK with the write-off, most would prefer to keep overhead to a minimum.

IDE的成本是影响管理层支持的另一个因素。有些地方可以注销,大多数人更愿意将开销降到最低。

#3


The syntax of a new language can mostly be learned in a few hours. What takes most time and effort is to get to know the APIs. To have a good IDE with IntelliSense makes it so much easier to poke around and learn the APIs than looking up in documentation.

新语言的语法大多可以在几个小时内学会。花费大量时间和精力的是了解API。要拥有一个带有IntelliSense的良好IDE,可以比查阅文档更容易学习和学习API。

#4


History shows that the language comes first and the IDE follows. Instead of building an IDE, build the killer app (Unix, mobile code, Rails, ...).

历史表明语言是第一位的,IDE也是如此。而不是构建IDE,构建杀手级应用程序(Unix,移动代码,Rails,...)。

#5


No, the IDE should not compensate for the language's deficiencies.

不,IDE不应该补偿语言的不足。

Having said that, the IDE sells VB to customers of mine all the time.

话虽如此,IDE一直向我的客户销售VB。

So, a fancy IDE tends to sell a language. Even though it shouldn't.

因此,一个花哨的IDE倾向于销售一种语言。即使它不应该。

#6


In a word, no. How many IDEs were built for HTML? Javascript? Ruby? PHP? etc. All of these had the language come first, and the IDEs come second.

总之,没有。为HTML构建了多少个IDE? JavaScript的?红宝石? PHP?所有这些语言都是第一位的,而IDE则排在第二位。

#7


I think it's great having a good set of tools to help productivity but it's not a 'should-have'.

我认为拥有一套很好的工具可以帮助提高生产力,但这不是“应该有的”。

#8


I'll say "yes." If not the productivity of, at least the presence of an IDE will bring in IDE-lovers and is unlikely to discourage command-line or Vim enthusiasts.

我会说“是的”。如果不是生产力,至少IDE的存在将带来IDE爱好者,并且不太可能阻止命令行或Vim爱好者。

If not a full IDE, at least syntax coloring.

如果不是完整的IDE,至少是语法着色。

Evidence: Fully half the SO questions tagged Objective-J ask about syntax highlighting.

证据:标记为Objective-J的SO问题中有一半是关于语法突出显示的问题。

#9


In an environment where developers are used to good IDEs it is harder to advocate the use of a new language if some of the IDEs people are using lacks support for the language.

在开发人员习惯使用优秀IDE的环境中,如果人们使用的某些IDE缺乏对该语言的支持,则更难提倡使用新语言。

E.g. on the java platform there is a lot of new languages that could be used in conjuction with Java, like Groovy, Scala, JRuby etc. Up to now it has been a problem if you want to start using Groovy and some of the developers use Eclipse, because the Groovy support in Eclipse hasn't been that good (luckily that is changing right now).

例如。在Java平台上有很多可以与Java结合使用的新语言,比如Groovy,Scala,JRuby等。到目前为止,如果你想开始使用Groovy并且一些开发人员使用Eclipse,那么它就是一个问题。 ,因为Eclipse中的Groovy支持并不那么好(幸运的是,现在正在改变)。