6 ms·

Glad to see one of the best C++ IDE's getting even better. The best part of it: even after all this years of active development and improvements it still feels

Glad to see one of the best C++ IDE's getting even better. The best part of it: even after all this years of active development and improvements it still feels very lightweight, it's more like sublime in terms of speed, when other comparable (by features) IDE's are feeling very heavy and bulky (like Visual Studio for example). The only thing I would love to dream of is to Qt Creator have a better stand-alone support, now it's completely and fully integrated with Qt ecosystem, and that's really nice if you use Qt, but when I'm trying to convince my co-workers to give it a try, the getting on-board curve is a bit too much. Though this being said: it become much better in last years.

problems 9y ago
It's interesting, I used Qt Creator for a few years, overall I quite enjoyed it, the refactoring features builtin to it were much better than the VS builtin ones IMO. The code completion was brutally slow sometimes though, especially if using the Clang code model which basically maxed a core for over a minute every time I saved a file. In the end I switched to VS and Resharper C++ for the performance gain there and coworkers comfort. I tend to use includes everywhere and only minimal forward declarations when required - this might be the source of the problem, but many modern C++ standards I've seen actually encourage that as best practice and discourage use of forward declarations. VS is able to keep up with that and Qt Creator just isn't. I find maintaining forward declarations a pain in the ass. See https://google.github.io/styleguide/cppguide.html#Forward_Declarations https://google.github.io/styleguide/cppguide.html#Forward_De... for example.
- pjmlp 9y ago
  Google style guide is well known in C++ circles for not being that good of a style guide, other than taming the minions of employees at chocolate factory. It used to be quite behind what is considered best practices in modern C++.
  - problems 9y ago
    I've heard this and avoid it in many places, but I think their arguments are sound here. The maintenance effort and unexpected rebuilds needed to upkeep forward declarations is something I'm not interested in doing. I'm not going to change my coding style because Qt Creator is broken, switching IDEs makes much more sense. Maybe I'm wrong and I've just been made horribly lazy by writing too much C#, Python and JS, maybe this is some pretty horrible technical debt, but hopefully this will all go away once the planned C++17 modules system is introduced. It's one of my biggest annoyances with the language to date.
    - pjmlp 9y ago
      > Maybe I'm wrong and I've just been made horribly lazy by writing too much C#, Python and JS, .... I know the feeling. Nowadays I only use C++ to write libraries for Java/.NET/Android/UWP, that I have full control over. When I see C++ code written in enterprise projects, frozen in pre-C++98, the code looks quite different, it is a continuous education process to try to convince devs to move forward, think Python 2 vs Python 3. I also miss modules, but at least I can play with them on VC++ 2017.

problems 9y ago

It's interesting, I used Qt Creator for a few years, overall I quite enjoyed it, the refactoring features builtin to it were much better than the VS builtin ones IMO. The code completion was brutally slow sometimes though, especially if using the Clang code model which basically maxed a core for over a minute every time I saved a file. In the end I switched to VS and Resharper C++ for the performance gain there and coworkers comfort. I tend to use includes everywhere and only minimal forward declarations when required - this might be the source of the problem, but many modern C++ standards I've seen actually encourage that as best practice and discourage use of forward declarations. VS is able to keep up with that and Qt Creator just isn't. I find maintaining forward declarations a pain in the ass. See https://google.github.io/styleguide/cppguide.html#Forward_Declarations https://google.github.io/styleguide/cppguide.html#Forward_De... for example.

pjmlp 9y ago
Google style guide is well known in C++ circles for not being that good of a style guide, other than taming the minions of employees at chocolate factory. It used to be quite behind what is considered best practices in modern C++.
- problems 9y ago
  I've heard this and avoid it in many places, but I think their arguments are sound here. The maintenance effort and unexpected rebuilds needed to upkeep forward declarations is something I'm not interested in doing. I'm not going to change my coding style because Qt Creator is broken, switching IDEs makes much more sense. Maybe I'm wrong and I've just been made horribly lazy by writing too much C#, Python and JS, maybe this is some pretty horrible technical debt, but hopefully this will all go away once the planned C++17 modules system is introduced. It's one of my biggest annoyances with the language to date.
  - pjmlp 9y ago
    > Maybe I'm wrong and I've just been made horribly lazy by writing too much C#, Python and JS, .... I know the feeling. Nowadays I only use C++ to write libraries for Java/.NET/Android/UWP, that I have full control over. When I see C++ code written in enterprise projects, frozen in pre-C++98, the code looks quite different, it is a continuous education process to try to convince devs to move forward, think Python 2 vs Python 3. I also miss modules, but at least I can play with them on VC++ 2017.