I use geany as both a text editor and an IDE ... so I'm not sure how to vote, maybe other.
|
Quote:
|
I want to change my poll from Other to Both. How would I do that?
|
For a beginning programmer, a good IDE has the advantage of being able to provide a lot of help with matters of syntax and also knowledge of the standard functions/classes/subroutines. However, on the down side, it is often confusing to newbies whether a particular problem is based in the code they have written, or simply in the use/configuration of the IDE. Moreover, the IDE often conceals major parts of the software development process which are part of what you should be learning. This becomes an issue when you have to work on the code without the benefit of the training wheels provided by the IDE.
In Linux, I've only used the Eclipse IDE in any significant amount, and I find it messy to import and export software projects between it and a non-Eclipse environment. If I could shift seamlessly between the two environments, I would probably use the IDE more. I've always thought I should be able to say to Eclipse 'The project I'm working on is rooted <here>; you figure out how to deal with it'. Instead, I have to migrate the work into the IDE's world. I've never been a fan of mixing the IDE's internal book-keeping with the actual code that I'm writing and building. Still, as time permits, I try to convince myself that getting comfortable with Eclipse will have a net gain of some sort. So far, though, put me solidly in the 'Text Editor' column. There are some pretty good programmer's editors available. I do use vi because of it's ubiquity, never managed to learn emacs, and routinely use nedit. If every *nix environment I worked in had one of the fancy Qt/GTK based editors (kate, kwrite, gedit, others I can't think of right now), I would probably migrate toward one of those. --- rod. |
I am primarily an Ada developer. For programming in the large, I find a good IDE indespensable; I prefer GPS. For knocking little C or Python together, vi is fine.
|
Quote:
|
I can't vote because there isn't an option for "it depends on the size of the project". I'll use a text editor with syntax highlighting for small scripts ... less than 100 lines say ... and a full IDE for things with multiple classes or when on-the-fly compiling and error checking is worthwhile.
OK, I've voted "other" considering this: Quote:
|
Quote:
Ada finds application in various industries. I'm told it is currently more popular in Europe than in the US, but have not observed that personally. I've even done web-development in Ada. |
both
use the best tool for the job ajunta or eclipce or gedit or vi or emacs it depends on what you are doing |
Hi,
I've noticed for years, that low-level 'gurus' would stick to text editors no matter what (as a rule of a thumb). I've been using couple a few of both and honestly it's a matter of a preference and balance between 'know-how' and 'easiness'. And I've been using Eclipse CDT for almost all of my development. Why? Well - eclipse CDT seems to get better over time and is pretty much working nicely on most of popular platforms(windows/linux etc.). Although the indexer can struggle on huge projects - for gcc applications / small projects and also embedded stuff (as you configure it) it can do all the job for you: just press ctrl+F11 to get the program executed. It allows you to easy debug it in a 'graphical' environment, you can switch perspectives etc. But the most importantly - it is the best editor I know that does the formatting well (and you can set up any type of style you like / prefer / need (customizing it) and writing the code is just easy: you can finally focus on real work and forget about trailing spaces.. or indentations.. etc - press Ctrl+Shift+F - it will format all the text for you (and so it will as you type). When indexed - leave mouse over a macro (or function) - it will resolve macros so you see what code the preprocessor would create (and it will also show you steps that macro is resolved). Same for functions / other declarations: you'll see the hover with function body, ctrl+click to get there for editing. Many other short-cuts to jump to 'last edited place' etc. You can also customize all shortcuts, define your own ones etc. Of course there's incremental search, file-browser, refactoring, header browsers and other 'standard' tools (hex editor, memory viewer and many more). Ok - I know, that you can spend many years getting to know tools like gvim or emacs (there's also an old 'elvis')- and many people will tell you that these tools can do things like above - but you might well spend lots of time trying to set up tricky options in some configuration files (like gvim)- and might take you weeks to get it set up = eclipse just has it 'by default' - and you only need to klick through *incrementally searchable* options to change 'defaults' to your custom preferences. From free tools only CodeBlocks is comparable - it's a great tool probably much better than eclipse fin practice if you do variety of projects - as it has many scripts / predefinied configurations / templates to create different types of them (e.g. not only console, as in eclipse, but has templates or types for projects like: static/dynamic link libraries,GTK+ / DirectX, GLUT, GLFW, QT, Win32GUI, OpenGL and also embedded ones: ARM / AVR, and even device-drivers and D-language apps). The indexer in the CodeBlocks is quite good and fast). Cons are for me - that given all great stuff that CodeBlocks has - I couldn't set up exactly the code formatting style that was required as a standard in my company and I could easily do that in eclipse. Anyways - in summary - it is a matter of preference really. Go and try it yourself, but don't get convinced, that 'real gurus' are only ones, who use vim or emacs - clever people are lazy and don't do work if there are good tools to do that work for them ;) |
Quote:
Also, not always you can compile automatically with F11 (unless you program in languages with JIT compiler like Java or scripting languages. You still have to write the make file, so you can press ctrl+f11 to build. Quote:
Quote:
Really, even with basic editing features, the biggest advantages vim and emacs offer me is that I can fully work without switching between mouse and keyboard too usual. Also, I can get a very big area on screen for editing text, unlike other IDE where most of the inner windows consume too much space, which I occasionally use. The other IDE I use is Eclipse CDT. Still, I bind the keys to Emacs style. |
Quote:
And you're right, it's not that bad to configure emacs, but still you need to do certain steps -get to find that configuration, customize it if needed and swap manually some config files to get it done. Might be a good experience in itself of course. But just the fact you still have to do it might be a bit discouraging - it wasn't bad if a tool needed such actions (some*) years ago.. but now it could be a bit more user-friendly and more ready to use :) Anyway, hopefully the author of the topic won't get confused too much, it is a matter of preference and is use-case specific. |
Quote:
|
Quote:
When I was first moving from IDE world in Windows to Linux world, I was shocked when I have to use vim to program (now it's very useful), and it left a big question on why I have to use vim. I understand how people, who are not familiar with Linux in general, feel. It's really frustrating as when you move from Java to C/C++, since your starting languages are scripting languages or high level language like Java, which abstracts the low level aspects. People are too used to the Windows way of doing. So if OP is not really optimized keyboard usage, but is more comfortable with the GUI environment, then IDE is the best choice. |
Quote:
|
All times are GMT -5. The time now is 12:48 AM. |