为什么要使用IDE? [英] Why should I use an IDE?

查看:144
本文介绍了为什么要使用IDE?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在另一个问题中, Mark 高度评价IDE,说有些人还不知道为什么他们应该使用一个...。作为使用vim进行编程的人,并且在大多数/所有同事使用vim或emacs进行所有工作的环境中工作,IDE的优点是什么?为什么要使用一个?

In another question, Mark speaks highly of IDEs, saying "some people still just dont know "why" they should use one...". As someone who uses vim for programming, and works in an environment where most/all of my colleagues use either vim or emacs for all of their work, what are the advantages of IDEs? Why should I use one?

我确定这是一些充电的问题,对于某些人来说,我并不感兴趣,所以请仅回复您认为基于IDE的方法优于的原因。我不知道为什么我不应该使用IDE;我已经不用了。我有兴趣从篱笆的另一边听到,可以这么说。

I'm sure this is a charged issue for some people, and I'm not interested in starting a flame war, so please only reply with the reasons you believe an IDE-based approach is superior. I'm not interested in hearing about why I shouldn't use an IDE; I already don't use one. I'm interested in hearing from "the other side of the fence", so to speak.

如果你认为IDE可能适合某些类型的工作,但不适合其他人,我也有兴趣了解为什么。

If you think that IDEs may be suitable for some types of work but not others, I'm also interested to hear why.

推荐答案

这真的取决于你使用的是什么语言,但在C#和Java我发现IDE有益于:

It really depends on what language you're using, but in C# and Java I find IDEs beneficial for:


  • 快速导航到一个类型,而不需要担心命名空间,项目等

  • 通过将其视为超链接,导航到成员

  • 当您不记得所有成员的名称时,自动完成

  • 自动代码生成

  • 重构(大量)

  • 组织导入(使用Java自动添加适当的导入,使用C#中的指令)

  • 警告为您的类型(即某些错误甚至不需要编译周期)

  • 悬停在某物上查看文档

  • 保持文件的视图,错误s / warnings / console / unit tests等和源代码全部在屏幕上同时以有用的方式

  • 轻松从同一个窗口运行单元测试

  • 集成调试

  • 集成源代码控制

  • 导航到直接从错误发生编译时错误或运行时异常细节。

  • Etc!

  • Quickly navigating to a type without needing to worry about namespace, project etc
  • Navigating to members by treating them as hyperlinks
  • Autocompletion when you can't remember the names of all members by heart
  • Automatic code generation
  • Refactoring (massive one)
  • Organise imports (automatically adding appropriate imports in Java, using directives in C#)
  • Warning-as-you-type (i.e. some errors don't even require a compile cycle)
  • Hovering over something to see the docs
  • Keeping a view of files, errors/warnings/console/unit tests etc and source code all on the screen at the same time in a useful way
  • Ease of running unit tests from the same window
  • Integrated debugging
  • Integrated source control
  • Navigating to where a compile-time error or run-time exception occurred directly from the error details.
  • Etc!

所有这些都节省了时间。他们是我可以手动做的事情,但更痛苦:我宁愿编码。

All of these save time. They're things I could do manually, but with more pain: I'd rather be coding.

这篇关于为什么要使用IDE?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆