Editing revision 19 of EditorsVsIDE
HomePage
|
RecentChanges
|
EditorIndex
|
TextEditorFamilies
|
Preferences
Editing old revision 19. Saving this page will replace the latest revision with this text.
Lots of folks have issues with comparing a good solid TextEditor with a good solid [[IDE]]. * '''[http://www.infoworld.com/article/03/09/19/37FEcodeedit_1.html?development An article in InfoWorld about the rise of the Texteditor against the IDE:]''' * '''[http://www.blueskyonmars.com/2003/09/23/infoworld-and-the-old-editor-vs-ide-debate/ And a reaction from Mozilla's Kevin Dangoor]''' * '''[http://discuss.fogcreek.com/joelonsoftware/default.asp?cmd=show&ixPost=1314 Naturally, the folks at FogCreek (JoelSpolsky's place) have interesting opinions too.]''' * '''[http://www.cubiclemuses.com/cm/blog/2007/rails_ides.html/ Finding a Rails IDE]''' - '''''J. Aaron Farr''''' * '''[http://lifeonrails.org/2007/8/30/netbeans-the-best-ruby-on-rails-ide Netbeans - THE best ruby on rails IDE]''' '''''George J. Cook''''' * '''[https://spin.atomicobject.com/2015/12/22/ide-vs-text-editor/ IDE vs. Text Editor: Choosing the Right Tool at the Right Time] '''''Matt Rozema''''' ---- One of my problem with IDEs is that they have the concept of "project", which is a catch-all for storing all of this stuff that they keep in order to track what it is I'm working on. One problem is that there is no standard for "project". Therefore, it is not easy to switch IDEs. So, I tend to develop using TextEditor''''''s, GnuMake, KornShell scripts, and a source control system such as GNURCS. I am a big believer in cleanroom builds. These "project" files hide a lot about what is going on. I'm naturally distrustful of these systems so I stay away. I would also contend that the use of the IDE is very "windowsy" whereas the use of a toolbox of little tools is very "unixy". I'm a product of the Unix/VMS environment which is lots of tools you run from a command line. In other words, I'm a bit of a dinosaur! --RonPerrella Let's look at what your typical IDE includes: * A built-in, not-to-shabby Windows-style TextEditor * A built-in debugger * A built-in Make/ANT equivalent build system * A built-in GUI builder or layout tool * A built-in compiler for the language (or languages you've chosen) * Tools such as ... ** multi-file search ** file manager ** FTP manager ** extension/plugin facility ** Access to an SCM system (source control management system) Some have more advanced capabilities such as: * File differencing/comparison * Code refactoring * Wizards It seems to me that many of the top text editors also have such capabilities. The rarest capability seems integration with a debugger. ---- 03/03/07 DMcCunney The IDE that is taking over the world at this point appears to be IBM's Eclipse project, at http://www.eclipse.org Eclipse is free and open source (though there appear to be some payware add-ons appearing.) It's written in Java, so it's cross platform, and will run on anything that has a current Sun JVM. As an IDE, it's an "everything *including* the kitchen sink" product, with editor, class browser, project manager, and all the other bells and whistles. It's intended for writing Java code, but can be used for pretty much any other language, though you may need to install an add-on or two for things like syntax highlighting. Borland was trying to unload its development tools a while back because Eclipse was taking over. Why buy JBuilder or C++Builder from Borland when you could get Eclipse free? I think the fundamental assumption behind IDEs like Eclipse is that programmers are not working alone. They're part of a programming team, working on specific parts of a larger project, and including code written by other members of the team, as well as code that may come from outside the team. Therefore, the IDE must support things like modules, class browsing, and access to source code repositories like CVS or Subversion, as well as integration with build, test, and debugging tools, and communication with the rest of the team. If you want to view it that way, Emacs is also an IDE. With the appropriate elisp extensions installed, you can do all of the above. An old friend who was a Unix developer used CCA emacs, and said "Why would you ever leave it?" Emacs wasn't only his editor -- it was his shell. He invoked emacs when he logged on and stayed in it all day, as he could do everything he needed to do from within emacs - edit, compile, test, debug, access a shell, read and write email and news, even play games.
Summary:
This change is a minor edit.
Please calculate
*
=
(Visit
Preferences
to set your user name.)
View other revisions
HomePage
|
RecentChanges
|
EditorIndex
|
TextEditorFamilies
|
Preferences