I also am very frustrated by Komodo. I think there are a number of reasons why it is this way. There's only one really big issue though, and that K10 seems to be coded in some XUL product, so you're actually working with something that was designed to be a web browser (renderer) and not a code writer. Many issues I report I think are either because of that, or because people coding against that don't know how to code it properly. That last one is speculation though, and may have more to do with OSX (i'll get to that later)
Other than the backend challenge, there seems to be more stress put on adding new features to advertise rather than fixing stuff that is already broken. Maintenance is not sexy and sold licenses are already sold. It is much harder to sell the maintenance stuff than new features, but I think K10/11 is so bad it, that if they fixed the issues, K12 could be great and worth buying.
The big reason why I think it's so bad from a product standpoint is lack of dog-fooding. Clearly, the Komodo devs don't use Komodo for their day-to-day work (particularly on OSX).
I've mentioned OSX twice now and want to say that on Linux Komodo does much better. I am not sure why, but I'm definitely thinking it's a platform thing. Remember XUL? I think it all traces back to the XUL engine not being used heavily on OSX, where Webkit reigns supreme. The komodo team should be forced to use OSX since that seems to be the worst possible experience.
I am trying out K11 again on OSX, and the new code completion is terrible. It's supposed to be better but I can't see what I'm typing because of all of the popups and none of them are what I actually want.
Let's take a look at what's new for K11 and see (what I thought) :
Revamped Code Intelligence: (Would have been good, it it was intelligent)
Print Debugging: (Never thought my IDE should do this)
DevDocs.io Integration: (DK,DC Don't know, don't care)
Live Previewing: (DC)
Project/Folder/File Templates: (DC)
Dependency Detector: (DC)
Universal Package Manager: (DC)
Clipboard Manager: (DC)
Auto-Formatting: (This I like, but it's a 1-time conversion)
Updated Publishing: (DC)
-Asynchronous remote files - work with remote files way faster (Could be interesting, but who isn't using git for this?)
-SDK availability (DC)
-Project template for Komodo add-ons (DC)
-User interface enhancements (Ok, this I care very much about but it was far too little)
The only reason why I am here is because Nathanr is responsive, and seems to care, but there is far too little for progress on my outstanding issues for me to keep using it. I've bought a license twice and been given one once (because that was easier than supporting K9 on Sierra!)
In the end, unless ActiveState's management shakes things up and reprioritizes working features over shipping new ones (and starts really supporting OSX rather than an afterthought) I will not be buying another Komodo license.
I have had to neuter K10/11 and turn it back into a dumb text editor on OSX because it's so terrible. The fundamental problem is if you leave K10/11 open for multiple days it starts beachballing and keystrokes lag by seconds. It's done this since Yosemite, which is when I started using it on OSX. There's clearly a problem with the XUL engine on OSX, but no one uses it enough to care to track it down and fix it. I think it's because it's in XUL, and ActiveState is not interested in actually fixing XUL, just using it. Nathanr and others play dumb about seeing this issue, but I've seen it on all 3 macs, on all versions of Komodo. I think if they dogfooded it they'd see what I mean.
As more and more devs get Macs, this will be a bigger and bigger issue. It might be too late, and Komodo is likely doomed. IMHO, their only options are to either fix the XUL engine they depend on or replace it outright. Between those two, there's only one feasible solution. It's far easier for me to just buy a license for something else and forget about Komodo, which I think the rest of the industry will eventually conclude.
And Petewulf, I'm at the same place... I keep filing report after report... of things that shouldn't even make it out into the wild. But even so, the stuff I report never gets fixed.