41–48 of 48 posts
BTW Everyone, please write "Qt Creator" with space between "Qt" and "Creator". I don't know how spaceless variant got so widespread.
Any plans to migrate away from Sourceforge for the pre-compiled binaries? Alot of people are becoming uneasy with them as a host given their recent history of malware-wrapped packages. Some adblocking subscription lists even blacklist the domain.
"We disagree with some of the previous monetization strategies from an industry and business perspective, and have immediate plans to discontinue programs inconsistent with our being a trusted and reliable resource for the entire open source community."
Sourceforge has nice features if you get away from the malware.
I'm not a C/C++ dev, so forgive my ignorance. Is Visual Studio [Community] not the standard anymore?
I use QtCreator: It's pretty solid and has good and fast code completion.
Earlier quoted context omitted.
Visual Studio does not run on anything other than Windows. However there is an Atom-like code editor called Visual Studio Code that is multi-platform running on Windows, OS X and Linux. I believe VSCode is built on the same platform (Electron?) as Atom although I might be wrong.
That they're both open source editors built on Electron is just about the only thing that Atom and VSCode have in common.
I'm not a C/C++ dev, so forgive my ignorance. Is Visual Studio [Community] not the standard anymore?
Not if you intent your code to be portable.
(I have used RedHat 4 back when it was new and fresh and have been using Vim for 15+ years; I have written vim scripts of 100 lines and more. Just to say, I'm not some greenhorn who's never known anything but an IDE. I still think developing C++ using Visual Studio is an order of magnitude better than any alternative.)
Earlier quoted context omitted.
I know. See my reply to versteegen. I am just too lazy to do it as they erase everything after each semester.
> I am just too lazy to do it as they erase everything after each semester. Write a script that does your reinstall. There's lazy-lazy and active lazy. As a programmer, it pays off to be actively lazy. Or, you can make a Git archive of your home directory. So long as your university has good bandwidth, this means you often won't even have to reinstall. Really, there's tons of things you can do.
Including just sticking gedit like what he's doing now.. If his assessment is that he doesn't stand to gain enough to bother then who are we to question that? I'm all for emacs any day, but let the guy make his own decisions.
Earlier quoted context omitted.
Not if you intent your code to be portable.
Why not? You can develop on Windows, don't include windows.h or put platform-specific things in #ifdefs, make use of all the awesomeness that is Visual Studio (potentially improved with ViEmu, Visual Assist and Resharper), then add a CMakelists at the end to compile for other platforms. Yes the first time you'll probably have to tweak a bit to get it to compile on other platforms, but that's loads better than sufferi…
If the Visual Studio compiler was able to run on many platforms and target those platforms, it could definitely be a choice, as it compiles fast and generates fast code. However, for the moment, g++ allows me to ensure that my project properly builds for all desktop platforms, without having to setup compilation-dedicated virtual machines or worse, a jenkins build server ...
How are you going to avoid breaking things if you can't cross-compile before committing ?
Earlier quoted context omitted.
Why not? You can develop on Windows, don't include windows.h or put platform-specific things in #ifdefs, make use of all the awesomeness that is Visual Studio (potentially improved with ViEmu, Visual Assist and Resharper), then add a CMakelists at the end to compile for other platforms. Yes the first time you'll probably have to tweak a bit to get it to compile on other platforms, but that's loads better than sufferi…
Experience has taught me that C++ compilers generally don't agree on the code they will accept: incomplete implementation of the standard (Visual C++ 2010 partial C++11 support), different non-standard header files (string.h vs memory.h), different warnings ( "possible loss of data" ), different error message conditions ( "not all control paths return a value" ). I find it a lot easier not having to support several c…
"How are you going to avoid breaking things if you can't cross-compile before committing ?"
Depends on the workflow. If you cannot afford to break builds, you need to push changes through a staging layer, which will then (in large scale setups like that) also run tests etc. If it's just a few people, your build server will catch it. If it's just me, who cares that it breaks on another platform - I'll have to fix it myself anyway. As long as you do somewhat regular integration, obviously.
There is no silver bullet. But when it comes to giving up the great efficiency gains that come from a great IDE like Visual Studio, or having to fumble with the toolchain a bit to integrate better - it's an easy choice for me. Plus having a project that compiles with multiple compilers keeps you honest about standards conformance and portability.