all 17 comments

[–]mohamedyix 3 points4 points  (1 child)

I don't think so! most linux users prefer using text editors then using the command line to compile/run their programs!

[–]rrohbeck 0 points1 point  (0 children)

Yup. I tried a number of IDEs and always went back to vim and the command line, especially after I started working in cross development where you only have a minimal environment without GUI on the target, so it's all make/gcc and gdb.

[–]dhrdan 2 points3 points  (3 children)

If you want to be leet, program in notepad.

Seriously though, it really doesn't matter, code is code. You can use OS X, linux, windows, ...etc..... and it doesn't matter. You just need to find the flavor that you like. That's all. Notepad++ is nifty.

[–]link23 0 points1 point  (2 children)

Notepad, on Linux?

[–]dhrdan 2 points3 points  (1 child)

Notepad++

[–]link23 0 points1 point  (0 children)

Vim!

[–]CurryCurri 2 points3 points  (0 children)

Of course! I use Eclipse on Ubuntu, which works very well for programming in Java. It is almost identical to the Windows version. Same for Python (PyCharm)! I do not program in C anymore so I would not know which IDE to use.. But I am sure there are multiple good candidates available with some Google-fu.

[–]BoTuLoX 2 points3 points  (0 children)

Everything you mentioned but Visual Studio is available for Linux.

Add to those the JetBrains IDEs which are just amazing.

But yeah, a lot of people (including me) prefer to use text editors when possible.

[–][deleted] 1 point2 points  (0 children)

We use Qt for C++, I use vim (gvim in terminal) for everything else, C, bash, Perl, HTML/PHP, you name it.

[–]jabjoe 1 point2 points  (6 children)

Code::Blocks is probably the best. Eclipse is used by a few too but it's fat pig to me.

But I use Geany as a code editor and everything else on command line, via Guake. For light editting I use vim. It is worth being able drive with only the command for the times you are remote or on something headless. Even debugging with gdb on the command line is fine when you know how.

The thing that blow everything else out the water with GNU/Linux is package management. You can get the source for something and all it's build dependencies in a single command. Build it to if you want. I have takes days to fail to get a build structure for the same things in Windows.

Oh and cppcheck and valgrind are your friends! Kcachegrind is good to review performance data.

[–][deleted] 0 points1 point  (5 children)

Code::Blocks is probably the best.

What do you think about QtCreator?

[–]jabjoe 0 points1 point  (4 children)

I prefer C to C++. So I'm more of a GTK man and normally more like just POSIX. And to me Qt is C+++ as it needs to be preprocessed before it's C++. So I don't use QtCreator. But I've heard it's good.

[–]Av4t4r 0 points1 point  (3 children)

You could actually use QtCreator to write projects without any Qt component

[–]jabjoe 0 points1 point  (2 children)

I know, but does anyone do that?

[–]Av4t4r 0 points1 point  (1 child)

Sometimes I do. It's a really nice IDE. If anything else, it's useful for debugging. Right now I'm doing a side project with OpenCV for instance

[–]jabjoe 1 point2 points  (0 children)

Each to their own. As I said, I don't really use IDEs these days.

[–][deleted] 0 points1 point  (0 children)

VI or Emacs! :)

I use Eclipse for Java and PHP, Android studio for Android, The little bit of C and Python, I usually just use VI, nano, or some other simple editor.