Let me preface this with the fact that I have spent years writing software in KDevelop 4. I think it's a wonderful IDE and I think it is the only IDE for linux currently out there capable of managing multi-million line C++ projects while still somehow remaining simplistic.

When I heard KDevelop 5.0.0 was released, I obviously had to try it right away! And boy was I disappointed. A lot of things that broke in this version I could have dealt with - It was a new release and obviously there were a lot of open ends to be neatly tied up. But there's one thing I just can't handle with this new release and it ultimately made me jump ship.

The parser.

Why. Why is the parser slow? A grandma with severe Amelia can type faster before auto-suggestions kick in, and I'm not exaggerating. The time between a ctrl+space press and when the suggestions appear sometimes takes up to 2-3 seconds. And when the parser actually does decide to kick in, there are situations where it gives suggestions so wrong, that you have to delete and re-type the line (such as the "magic methods" when auto-completing member functions).

Here are a list of things wrong with KDevelop 5.

• A lot of the default keyboard shortcuts are ambiguous with other shortcuts.
• The parser is SLOW. Auto-complete is unusable due to the parser being slow. I can type faster than auto completion.
• There are times when the parser will freeze KDevelop for 30 seconds.
• Jumping to the first error (F4) stops working after you've debugged once, the only fix is to restart KDevelop.
• When debugging, the variables browser doesn't resize automatically on break. Only when you left-click on a variable does the window decide to auto-resize.
• When debugging, expanding a variable in the tree doesn't automatically resize the window.
• When debugging, the flippy arrows in the variables view sometimes disappear inexplicably when stepping. They re-appear if you select a different stack frame.
• Things written to stdout don't always appear in the output window in the bottom. They seem to be buffered and flushed later. This is very annoying for simple puts() debug messages.
• Targets no longer list the files associated with them, instead you have to go look for them in folders.
• On a dual monitor set up, where two monitors with different sizes are used, the window will continue to grow and grow sideways until half of the IDE no longer fits onto your monitor. The only fix is restarting KDevelop.
• Closing (exiting) KDevelop causes one CPU core to be utilized 100%. You have to kill -9 the process to fix this.
• Opening files is slow (ctrl+alt+o)
• Switching between header/source doesn't always work and is slow.
• When the parser does decide to be fast enough and it auto-suggests a member function implementation, it does it so wrong, that you have to delete it and re-write it by hand. E.g. it doesn't fix up what you've already typed.

In general, the IDE feels sluggish and slow. KDevelop 5.x.x is a clear regression when compared ot 4.x.x.

I really do hope things are improved with this version, but the slow parser is just unacceptable, sorry.

It's like whole KF5.
Just downgrade and check again in 6 months or more.

Most of the issues you list are new to me. So please consider putting them in the tracker ...

A few comments:
- There's a bug which makes the parser very slow with some projects. It's relatively fast with others. We really need to investigate this, we're currently not sure what the circumstances are which make it slow. I think you are affected by this issue. The parser _is_ overall a bit slower than in KDevelop 4, but in return scales much better with the amount of CPUs in your system, so if you have at least 4 cores, it tends to make no difference. In return, it's much more accurate (fully supports C++14 and complex templates, etc). Edit: Relevant mailing list thread: https://mail.kde.org/pipermail/kdevelop ... 55066.html
- Buffering is, well, buffering; if you want to be sure that your output shows up, flush the stream.
- Regarding the freezes you report, do you use 5.0.0 or 5.0.1? We fixed a really bad freezing bug in between.
- The "hangs" on exit are cleanup and waiting for jobs to finish. That it takes so long for you is probably related to 1), but you should just wait it out. If you kill -9 the process, you will corrupt the persistent disk cache and force it to be rebuilt on the next restart, which again requires re-parsing everything.
- Listing targets works here, so more information is needed.

I'm not much into the debugger stuff, so unfortunately I can't comment on that.

Greetings,
Sven

I am using kdeveop 5.5 and it hangs often on the parser, often also crashing. it's a mess. Ubuntu 20 LTE

Yep you will kinda hit lots of these issues in first ten minutes of using the KDevelop
I still think its potentially the best FOSS Linux IDE for C/C++ after little bit of polishing, but now the amount of tiny, annoying bugs is staggering. Especially for the application used mostly by C++ devs (probably if you can use it, you can fix it ). So I switched from using KDevelop to fixing KDevelop almost immediately