Page MenuHomePhabricator

IDE Notes
Updated 856 Days AgoPublic


Courtesy of Anjuta website

anjuta-screenshot.png (848×1 px, 218 KB)



  • No Windows version. -@smcarlson
  • Limited top toolbar (Where are the run/debug buttons?). -@smcarlson
  • Compiling is rather difficult (According to people on the web). -@smcarlson
  • Adding files to a project isn't simple, sounds a lot like Code::Blocks (According to people on the web). -@smcarlson
  • Debugging tools aren't easy to use (According to people on the web). -@smcarlson
  • Help files are online and lack images/detail. -@smcarlson


Screenshot_(93).png (900×1 px, 156 KB)



  • Comments are by default a light grey font color that is hard to read. [This is only a default - you can change colors under Settings -> Editor -> Syntax Highlighting. - @jcmcdonald]
  • Doesn't automatically compile code. -@smcarlson
  • Breakpoints aren't saved when project is closed/reopened. -@smcarlson
  • Can't right click to add a file to the project [With the project open, right-click anywhere on the open file or its tab and click Add file to active project. -@jcmcdonald]
  • Can't right click in the file explorer to add a new class (.cpp and .h) to the project. -@smcarlson
  • Limited Intellisense. -@smcarlson [NOTE: Only true of some installs.]
  • Debugging doesn't show what's in the variables [Watch list displays contents of monitored variables. -@jcmcdonald]
  • Compilation settings split between global and project and debug and release can lead to confusion in integrating external libraries. -@beanders
  • Because it can do so many things, it can be quite confusing at times especially when switching languages -@jchutton
  • Possibly heisenbugged - some features don't work on some machines. -@jcmcdonald


This is Luna, current version of Eclipse as of 4/22/15.

Screenshot_(94).png (900×1 px, 124 KB)


  • Outline shows all fields and methods contained in a class (Clicking takes you to that field/method). -@smcarlson
  • Breakpoints persist throughout sessions and can be toggled on/off. -@smcarlson
  • Debugging shows what's in the variables and highlights where the changes are when stepping through the code. -@smcarlson
  • Awesome intellisense. -@smcarlson
  • Code automatically compiles. -@smcarlson
  • Fairly fast access to documentation built in. -@smcarlson
  • 3rd party tools can be added on (Downside is they sometimes don't work). -@smcarlson
  • Fairly simple to find tools and most options. -@jchutton


  • Breakpoints are fairly small in size. -@smcarlson
  • Debugging is a separate view that looks different from the coding view. -@smcarlson
  • Can be difficult to get it to install correctly. -@smcarlson
  • Not super customizable. -@smcarlson
  • Problems pane references everything in your Eclipse workspace, not just the current project. -@smcarlson
  • Large memory footprint may not be suitable in memory constrained environments. -@beanders


Screenshot_(95).png (900×1 px, 118 KB)


  • Visual option for debugger (Perhaps only useful to people new to CS?) -@smcarlson

Courtesy of jGRASP website

Capture.PNG (437×441 px, 53 KB)

Screenshot_(96).png (900×1 px, 143 KB)

  • Fairly clear what buttons in the toolbar do. -@smcarlson
  • Very clear what variables hold while debugging. -@smcarlson
  • Wide open space for code and console output -@amhenry


  • Doesn't automatically compile code. -@smcarlson
  • No intellisense. -@smcarlson
  • Annoying popup message if you click run from a file that doesn't contain main. -@smcarlson
  • Very limited syntax highlighting. -@smcarlson
  • Files like .class that aren't editable are displayed in the project explorer (This could be a headache for a large project.) -@smcarlson
  • Very limited customization of setup, what you see is what you get (Can resize panels, but you can't move them.) -@smcarlson


Screenshot (100).png (900×1 px, 106 KB)


  • Syntax checking and linting while you type. (Similar to spellcheck.) -@jcmcdonald
  • Large code composition area. -@smcarlson
  • Vertical toolbar. (Some may dislike.) -@jcmcdonald (This can easily be changed, drag it to the top. @smcarlson)
  • Built-in Python console. -@jcmcdonald
  • Choice of themes. (Have to restart after changes for this to work correctly. @smcarlson)
  • Simple layout. -@jcmcdonald
  • Format and commenting shortcuts. -@jcmcdonald
  • Full "symbols" list for quickly navigating code. -@jcmcdonald
  • Easy plugin installation. (Built-in catalog.) -@jcmcdonald
  • Detailed linting for migrating Python 2 to Python 3 code. -@jcmcdonald


  • Limited debugging tools. -@jcmcdonald
  • Doesn't warn you that a folder already exists with the same name, simply adds files in. -@smcarlson

Visual Studio

Screenshot_(97).png (900×1 px, 175 KB)


  • Extremely powerful, I feel like you could use VS for years and never know everything that it's capable of. -@smcarlson
  • Highly customizable, dock things where you want them, resize them, and pull out features when you need them (ie database tools). -@smcarlson
  • Easily add new files to project and link in existing ones. -@smcarlson
  • Built in source control. -@smcarlson
  • Easily see what is in variables while debugging. -@smcarlson
  • Persistent breakpoints for debugging. -@smcarlson
  • Great designer with a lot of properties to set for each built in control. -@smcarlson
  • Double click on visual designer item in order to do event handlers. -@smcarlson
  • Amazing intellisense. -@smcarlson
  • Code folding with regions makes large projects easy to deal with. -@smcarlson
  • Documentation shortcuts available. -@smcarlson
  • Lots of resources on how to set up or do anything. -@jchutton


  • Poor backwards compatibility with its own previous versions. -@jcmcdonald
  • Only uses one compiler (MS Visual) w/ limited compatibility. -@jcmcdonald
  • Overwhelming to new users, need a class/tutorial to get up and running. -@smcarlson
  • Finding a feature that you need could be challenging. -@smcarlson
  • Massive size, slow to start up. -@smcarlson
  • Very large memory footprint, making it unsuitable in machines with less than 2GB of ram -@beanders
  • Windows only -@beanders
  • Can see where breakpoints are on scrollbar, but can't navigate directly to them. -@smcarlson
  • Difficult to debug GUI code, stepping through often times doesn't display elements. -@smcarlson
  • Must quickly get in the habit of renaming GUI elements because it's difficult to change names after adding click events and other behind the scenes code. -@smcarlson
  • Heavily heisenbugged - errors on identical code/compilers vary between machines and even individual users. (Probable occurrences of Schrodinbugs as well.) -@jcmcdonald



  • Feels like an easier version of Visual Studio. -@jchutton
  • Works only on Linux OS. -@jchutton (I wouldn't call this an advantage, TBH -@jcmcdonald)
  • Intellesense works pretty good. -@jchutton
  • Options are easy to find and usually intuitive. -@jchutton
  • Shortcuts are intuitive. -@jchutton
  • Layout is optimal and easy to work with. -@jchutton


  • Works only on Linux OS (for you Stacy) -@jchutton
  • Still in development so not all code works (but its gotten pretty good) -@jchutton
  • Mostly for C# or .NET code but others can be used. -@jchutton
Last Author
Last Edited
Apr 10 2020, 2:36 PM

Event Timeline

jcmcdonald changed the title from IDEs to IDE Notes.Apr 10 2020, 2:36 PM
jcmcdonald moved this document from IDEs.
jcmcdonald added subscribers: beanders, amhenry, jchutton and 2 others.