Slashdot Mirror


What is the Ultimate Linux Development Environment?

nachmore asks: "I've been programming on Linux for a while now, always content to use vi for my editing and any debugger tools out there (gdb for C/C++, and so forth). As part of my SoC project I was working on Thunderbird (my first huge project on Linux) and I found that , although shell-based tools can do the job, they lack in easy project management, ease of debugging and other development features. I've only ever programmed with a GUI on Windows — and I have to admit that I find Dev Studio to be one of the few programs that Microsoft seems to have gotten (nearly) right. I've played around with Eclipse but find it's C/C++ support still lacking. So what GUIs would you recommend for Linux? I would like something with debugging (single step, step through, step-to-end, etc) support, CVS access and of course, support for large projects (e.g. Mozilla) and especially good support for C/C++. Is there anything really good out there, or is vi the way to go?"

6 of 643 comments (clear)

  1. Re:You might as well ask... by JungleRob · · Score: 0, Offtopic

    Amen!

  2. Re:You might as well ask... by Nimey · · Score: 0, Offtopic

    Quoth Pitr: "All are fallink into the hands of Discordianism!"

    --
    Hail Eris, full of mischief...

    E pluribus sanguinem
  3. Re:You might as well ask... by T3hFish · · Score: 0, Offtopic

    Its all about the flying spaghetti monster, man!

    --
    "A witty saying proves nothing." -- Voltaire
  4. Re:You might as well ask... by AuMatar · · Score: 1, Offtopic

    Many problems with this:

    1)Most religions are not hierarchial. You managed to pick the only one that is. Other than rabbi, there's no higher up to go in Judaism. Same for Islam and Imams. Same for Buddhism. Same for many Christian sects.

    2)Not all religious leaders really believe. Historically, religion has been a path to power, especially for younger sons of nobility. In the middle ages, popes were appointed for political reasons to please the most powerful king, not because they were faithful. I'd say the vast majority of high religious offices are not held by the most faithful, but by the most power hungry even today. The truely faithful would be too busy praying to play political games needed to move up a hierarchy.

    3)Cult leaders frequently do believe. Some are utter frauds, but many devoutly believe in what they say.

    So nope, still no difference other than number of followers.

    --
    I still have more fans than freaks. WTF is wrong with you people?
  5. Re:Personally... by NickFortune · · Score: 0, Offtopic
    tell you what..build me a windows forms app with vi and I'll use VS.net

    I'm not actually opposed to GUI based forms designers, or to code generation suites where the problem is well understood. I just don't think that this functionality is best provided by embedding it into my favourite text editor. That's the point you see - to have lots of separate tools that can be combined flexibly, rather than a single monolithic tool that embodies the design time assumptions of the lead developer.

    ...and I'll do it 10 times better in 1/10th the time as you.

    You might be surprised. I've recently looked at some of the code that VS2003 generates and it's pretty pedestrian stuff. That's forgivable from generated code, but you don't have to do it like that. I reckon I could write a shell tool to generate equivalent code from user defined text file. There are a couple of framework approaches I think would take the pain out of forms writing as well. I've done it before in other environments.

    Give me a fucking break....vi....

    Here's a challenge for you: why don't you go and write me a chat server in Boo using VS 2003. I'll have mine written and tested using vi before you're done writing the necessary plug-in. Oh, and I expect it work on Linux under Mono as well as Windows with .NET

    Have fun!

    --
    Don't let THEM immanentize the Eschaton!
  6. Re:Personally... by cortana · · Score: 0, Offtopic
    - automatic build process, generating a makefile, or at list a part of it (dependencies) if you want flexibility. And don't tell me you like telling which .h you need for every single .c / .cpp file you got... it's stupid, repetitive and SHOULD MUST BE automatized.
    Of course, but you don't need to flee to an IDE to do this! :)

    I recently read the excellent Recursive Make Considered Harmful paper, and subsequently came up with this:

    include $(sources:.cpp=.d)
    %.d: %.cpp
            $(CXX) -MM -MF $@ -MT '$*.o $*.d' $<

    GCC creates a .d file for each source file, that lists its dependencies; GNU Make reads these files (building them if they don't already exist) and uses them to know exactly which files are needed to build which other files.

    If I need anything more complicated (i.e. automated cross-compiling, or providing a build system that has to work on an old crawling horror of a machine that GCC and Gnu Make can't be run on) and I use the autotools.