It's clang-based, so suffers from none of the tags-type issues: it's context-sensitive, and can see straight through gnarly stuff such as identifiers generated by token pasting.
Good points:
- Only mildly fiddly to set up
- Code browsing works well
- Code completion works well when it works
- Cute gcc/g++/etc. wrapper trick means you don't have to change any build settings
Bad points:
- Making it work with code you haven't built yourself on your local system (e.g., 3rd party stuff that's not complete, code for another platform) is less straightforward
- Code completion sometimes doesn't work with certain files (and for no reason that I've ever been able to figure out)
- It's probably my own limitations but I found it extremely inconvenient to debug (internally it's surprisingly complicated: separate client and server, lots of lengthy command lines, client code writes elisp code to stdout and elisp in emacs eats it up, the actual completion popup is a separate package, etc.)
I tend to use a single maximized app in a GUI environment, often running emacs, though I do like to split the screen in half to allow two full-page, focused views (e.g., code editor and browser). And when helpful, I'll pull up more windows.
See also http://lifehacker.com/5689579/five-best-distraction-free-wri... for others who have felt the need for focused tools that remove the distractions of multiple window environments.
"For personal reasons, I do not browse the web from my computer. (I also have not net connection much of the time.) To look at page I send mail to a demon which runs wget and mails the page back to me. It is very efficient use of my time, but it is slow in real time."
But the attitude of 'I won't even take a photography of my screen for a semi-noble purpose, something thousands of people do for spurious purposes, because I will not give up an inch of self righteousness, ever'.
That's what gets me.
This is not an screenshot: http://i.imgur.com/sEygQyP.jpg
It's only a photography, but it works just as well.
https://usesthis.com/interviews/brian.kernighan/
The screenshots are of Rob Pike's Sam editor.
https://emptysqua.re/blog/unittests-code-coverage-in-pycharm...
http://blog.jetbrains.com/idea/2012/04/code-coverage-for-jav...