> Dev-cpp, mingw, and allegro where my gateway drug back in 2000 or so, nice to here it’s still around.
Same, when I saw Dev-cpp, my first thought was "bloodshed.net"; I'm glad to see a fork alive and well. This IDE in particular was a stepping stone/turning point in my career.
Me too. I haven't heard anything regarding bloodshed dev-c++ for ages, perhaps over a decade by now. Talk about a blast from the past. I still recall cutting my C++ teeth with dev-c++ writing small opengl+win32 apps with it, and struggling to find where the bloody triangle was showing up. Using dev-c++ made that experience much more enjoyable. Good times.
Same here! I went to a computer camp in 1999 (age 12) and started learning C++. Not able to pay for either CodeWarrior (what the camp used) or Visual C++, I stumbled across Dev-C++ on bloodshed.net and for years it became my go-to. Memories.
Me too. IIRC, there is no free IDE on windows at that time. I used Turbo C and Visual studio 6/.NET at school. Then I find Dev-C++, finally I can code anywhere.
yes, same! I remember being a child and thinking it was so bizarre that they called it "bloodshed" dev c++ but i didn't care, i was having the time of my life.
Same, middle school here. Took a game dev course over the summer through the local technical college. The book recommended it, IIRC. Ran it the little bit I was still somewhat on Windows before switching fully to Linux. Now it is vim and gcc...
I remember this as total pain to use compared to CodeBlocks 10 years ago, but if Embarcadero improved it and kept it low memory it can be pretty usable in our schools which often have 10 years old PCs with 2GB of RAM etc...,
I think the 10 years is the key here. 15+ years ago the DevC++ was a gem, lightweight, fast usable IDE. But 10 years ago there was the free VSExpress out (not even the first, 2005 and 2008) which was far superior to DevC++ imho. (edit: on Windows)
I was going back to home town from college and we were not having internet at home.
I remember I downloaded Dev-c++ before going back and a book on c++ just for fun. Compiling my first program took 2 days ( no net, no similar friend circle ) !! Best 2 days of my life.
Dev-c++ was my first proper IDE, happy to see it around.
Any particular reason why these two posts were rendered dead?
-------
H_Pylori 1 hour ago [dead] [–]
Back in the day, Dev-C++ was the ideal IDE for the C/C++ beginner. Simple, easy to use and very light in term of resources. I remember being able to run Dev-C++ on a 166Mhz Pentium I with 32Mb of RAM (which was hopelessly obsolete even by then). You could even install C libraries automatically as DevPaks.
I wonder what's the motivation behind this fork. Embarcadero is the company currently maintaining and selling Delphi dev tools. They also have their own commercial C++ IDE. Is it treated as demo App for their own toolchain.
I don't think Visual Studio is "hackable" at all. Are you thinking of Visual Studio Code? Aren't the two very different? The first is a very large and commercial Windows application written by Microsoft and the latter is a free/open-source IDE with numerous plugins written as an electron app.
I used to recommend TDM, but it doesn't get updated very often. These days I would say that https://nuwen.net/mingw.html is a much better bet, particularly in view of all the libraries that come with it.
Wow, Dev-C++. Not the very first IDE I used (that would be Div2), but at least the very first IDE I needed to use for academical reasons, back in 2001. This is the IDE where I started committing serious mistakes, i.e. the ones that make a lightbulb turn on when you finally solve them.
I used it lightly. It was nice. Remember it being fast at least for my light usage, compiling simple UNIX-style commmand-line utilities (to achieve small tasks) that I used to love to write on Windows - and still do :)
While I'm on the subject of command-line utilities, here is a post on my blog about a tutorial I wrote for IBM developerWorks on the topic of "Developing a Linux command-line utility" in C:
On Windows it is mostly meh in my opinion as it is hard to compete with the Visual Studio feature wise. Had they ported it to Linux I'd be way more interested. I am not particularly fond of native C++ IDE choices on Linux. Currently using CodeLite for that purpose.
I will have to disagree here. Visual Studio's C++ tools are fundamental for any C++ development beyond toy "hello world" and prototypes. I've been a Linux user for 8 years now and my biggest pain is the lack of a proper C++ IDE with decent debugging. Even if you forget an IDE, there are no decent debuggers[0][1].
QtCreator might be worth trying. It's focused on Qt apps, but it's a general C++ IDE. KDevelop is another one. I don't know if these would fit your purposes or not, but I'd be interested in hearing.
I think there is a level of familiarity bias that happens with debugging tools. I could probably get away with making gdb my login shell I live in it so much, and when I find myself using Visual Studio's debugger, I find it incredibly clunky. The things people complain about for gdb (e.g. you can't see the source code for where it is executing) I don't find to be a big deal (I just jump to the correct line in my text editor). Meanwhile, using Visual Studio is a complete pain for me, for reasons that clearly don't matter to people who use Visual Studio all the time (e.g. while possible, running multiple instances of a program side by side is annoying, quickly evaluating arbitrary expressions is more painful, setting data breakpoints is needlessly complicated (do they still ask if it is C or C++?), etc.
I think it must just be one of those things where the tool you use shapes the way you work, and so then when you switch tools, but try to work in the same way, you get frustrated.
To be clear, the posts you are referencing are about debugging an executable with no source code available, which is not the normal use case for a programmer.
It seems you have not read the post or you don't have experience with gdb or with Linux debuggers/ide combos. He's debugging zig, but his issues are with the ux and iirc he mentions few zig-specific bugs. I have been through the same ordeals while debugging C++ on Linux. In the end, there's only gdb with a command line interface. Couldn't get any nice IDE with watch, memory view or even simple breakpoints to work. Some have a few of those features but none has all of them working. Eg. if you have a working breakpoint it'll fail to properly inspect STL containers etc.
I'm sure there are many people saying "works on my machine", but it never worked on any of mine, sadly. Visual Studio simply works and has a nice, intuitive interface. Pressing F10 to step over will always be better than typing something in the gdb command line and hitting Enter.
I haven’t had any trouble doing graphical debugging with VSCode and the C/C++ plugin. I get breakpoints, locals, watch, etc. The one thing I miss from Visual Studio is being able to easily change the watch window display format (e.g. showing a number as hex).
I agree totally. No one else has ever been able to make a debugger as good as Visual Studio. That's why I do all my core development work on Visual Studio, and only use XCode / code blocks for testing on Mac/Linux.
QtCreator is a generic C/C++ IDE, built with Qt. (and since it has language server support nowadays it looks like it's useable for rust, etc).
It has a profiling UI, valgrind support, etc etc.
VS is definitely one of the better C++ IDE's (if you're programming on Windows, at least); but I've found CLion to be a decent alternative on Linux (and macOS, but I just don't like XCode).
I'm curious, have you checked out JetBrain's CLion? while not free, it's pretty much the best CPP IDE out there, as it's usually the case with JetBrain in general.
I use C++ to mostly to develop backend servers. Since I use multiplatform libraries all active development and debugging happens actually on Windows. I maintain parallel project for CodeLite and makefile on Linux. Normally after I satisfied with the results on Windows I just click a button that triggers my build/test/deploy pipeline. From here all happens automatically but if the tests on Linux fail I would then fire up CodeLite to debug and find the reason. Mind you during last year I only had to do it twice. If I add/remove files / libraries this would be another reason to launch CodeLite to adjust Linux project accordingly. In theory I could do this on using CMake but it is simply not worth it for me.
I tried CLion and bugs / crashes with debugging and some other parts (do not remember exactly as it's been a while) prevented me from using it. Was not fond of its sluggishness either.
I just checked. From cold start it takes 3 seconds for me to start typing in Visual Studio in my current project.
Dev C++ might be faster in this particular matter (been a very big while since I've used it so can't really verify) but I would not trade loosing 3 seconds a day for the whole shebang of features that are way more robust and plentiful in Visual Studio.
At the time when VC++ 6 was the standard, it was worth frigging with Bloodshed if you didn't have $$$, an MSDN subscription, or some other access. Once there were the Express Editions and now VS Community Edition, it's really hard to justify the hassle for a second-rate set of tooling, unless you enjoy shaving yaks.
Back in the day, Dev-C++ was the ideal IDE for the C/C++ beginner. Simple, easy to use and very light in term of resources. I remember being able to run Dev-C++ on a 166Mhz Pentium I with 32Mb of RAM (which was hopelessly obsolete even by then). You could even install C libraries automatically as DevPaks.
