A lot of standards for IDE or Editor was changed since 2014 (design, base languages and another stuff) and comparing Komodo Edit 8 (2013) with Atom (2014) just a bad idea. Atom developers know what another developers need in 2014 and of course Komodo developers just cant know this in 2013. If you want to compare Komodo and Atom - you must look at Komodo 9 when it released.
P.S.: Sorry for my English.
Atom is written in Javascript, so there is barely anything to compile, making it easy for anyone to build it without spending much time on it, but making it a lot slower because, wellā¦ its all in JavaScript. Komodo also uses JavaScript but all the āheavyā stuff is done by either Python or C++.
Komodo does take some time to build but thats only the initial build, after that builds are very fast. That said I have been thinking of making a pre-build Docker image that has already done his initial build, it would be quite large to download still though, and would require you to be running Linux.
All of that being said; you donāt actually need to build Komodo to develop on it, thatās really only necessary if youāre working on core functionality. If you are working on modules or very specific files you can just use the addon system to work on Komodo. We are working on a new documentation site that will cover topics like this in detail.
Hey Nathan + all 
Back to the original question, how is the ironing of niggles and bugs going?
Any of these bugs or enhancements actioned yet?
Hmm link doesnt seem to work for me, nor the old one. I guess workflowy made some changes?
Think they did, yes! Updated nowā¦
Some of those have definitely been addressed, though not all, and some of those likely wont ever be addressed (eg. moving panels to different windows). Weāve mostly been working on large features up till recently, so the polishing phase in which problems like the ones mentioned in your collection has only just started so weāll likely still be addressing many of those raised issues.
I hope so.
Autocomplete on the nightly I downloaded last night was unusable as everything was so dark.
Still no quotes in HTML attr= which is a mind-boggling omission! (itās kind of my yardstick for polishing).
That was pretty much as far I dared goā¦
Autocomplete is skinned according to the color scheme you use. What color scheme were you using?
Whatever is the default.
The editor (HTML) was white background with dark text.
The autocomplete popup was a very dark brown background with black text.
Anyway, Iām sure you will catch it for final release.
Could you please file a bug for something like that? Sounds like a perfect chance for something to get missed.
Also the quotes after HTML tag attributes fell off the milestone so it was not looked at for Komodo 9: ActiveState Support for Enterprise and Developers
Iāve updated it.
EDIT: Microsoft reported that they will support Docker soon so for Windows users, youāll be able to user @nathanrās instructions to build a docker image that contains the build or possibly even use the one that Nathan creates.
Nerdgasm
I personally dont care much for Windows but this opens doorsā¦ doors I tell you!
Have sent you guys an email 
Filed a bug!
I have not gotten a chance to try out Komodo 9 yet but some things I would like to see:
Better SSH support, When I hit save the window should not freeze up. Or worse when I have multiple windows open, 1 SSH can lock out all the windows. Some drag and drop support and basic file support to make SSH feel like working locally.
When I drag and drop, I would like a confirmation box. Not too fond of playing find the file you accidentally dragged.
As I work on multiple projects at the same time, how about custom Themes for each project? It often happens that I have multiple versions of the same project open. (on different servers) and then I would start working back and forth only to realize I am working on the wrong project/server. Quick color codes would make it easy to identify. I use same approach when working on multiple servers on RDP, use different colors to quickly identify where I am.
On the database stuff, are we going to get Postgres support? It has been 5 years since it has been promised. Redis support would be nice on the side too.
Note that while we appreciate all the feedback this thread should not become a dumping ground for bugs/enhancement requests, please use the bug tracker to file them instead. Tracking them via a forum thread is not productive and really only useful for having an open discussion about what a bug / enhancement request might entail.
Also, donāt put all requests in one bug/enhancement request. Multiple action items in one bug is a really great way to lose track of things.
PS. BUT yes! As Nathan said, Thank you for taking time to let us know!
Hi Nathan, indeed I agree that feedback is of the utmost importance, and as said in a different thread I also develop software, and need that feedback to make improvement. But put yourself on the side of the people providing feedback: the first thing you expect is for the feedback to be taken into account in some way, specially if you are reporting bugs, or making what seem relevant suggestions. I count 14 done by myself since I started using Komodo as programmerās editor in 2011, and counted now how many of these bugs are still present in Komodo 9 - latest build from April/15: eight of them are still there. So half of the reports were not taken into account. Two days ago I revised these and added to each of them a note saying that these bug are still there in the latest build of K9.
Now, please donāt read me wrong, Komodo is in my opinion a GREAT editor, the best one, otherwise I would not be using it, but these little things here and there ā¦ and the fact that they accumulate as if the priority is put somewhere else is not good, diminishing the good impression and leaving the door open for people to be willing to try other editors. I do realize that resources for fixing things are always scarce but reports should be addressed at some point, not more than 6 months later, say. This is the list of 8 remaining issues I mentioned above: #91956, created 2011-12-21, #96310, suggestion (relevant), created 2012-11-24 , #102152, created 2013-12-10, #102153, created 2013-12-10, #102154, created 2013-12-10, #102155, created 2013-12-10, #102159, created 2013-12-10, #102211, created 2013-12-10.
To these, I added two days ago another one that I do not see listed in āMy Bugsā, perhaps an issue with the website: when having the beautiful Abyss dark skin, the skin color is not applied to the title field that displays the output of ārun a commandā in āCommand Output Tabā, so that the output is illegible (the color of the font for the Abyss skin seem to be the same as the color of the background for other skins, and the bug is that both get mixed, and then you cannot read anything). This plus the fact, also tracked as feedback that when you resize this command output tab (lower window) the text in the main window blinks and jumps (badly), makes K9 not usable for work. I am still with K8. For that reason I reported these two new bugs. But then no feedback happened. I want to change, but it must be at least as good as K8.
All in all: I still think you are producing the very best editor available, for Mac at least, but a bit more attention to the details still not working 100%, the minor things here and there accumulatingā¦, the feedback disregarded after some timeā¦ all these are areas for improvement, I think, and somehow this is what I feel others are saying as well in this thread.
@ecterrab I totally hear you and I really REALLY appreciate you taking the time to give feedback both on the forums and the bug tracker.
We have been making a lot of changes both internally and externally to better position ourselves to deal with this feedback, most notable:
All of this has happened in just the past year and we will continue to work on more projects that make our community more enjoyable and more importantly; to position it in a way that it actually helps make Komodo a better software.
What Iām getting at is that itās not as simple as to simply address all the bugs everyone has ever reported, we got to a point where our systems just became hard to manage. Now with all the changes weāve gone through over the past year we are in a much better position to listen to our community and I promise you that you will notice the results of those changes in the quality of Komodo going forward 
Hopefully this addresses the concerns you voiced.
The old bugs system has been shutdown for over a month now. Is that where you submitted a bug two days ago? That should not have been possible. Did you potentially file it under a different product?
Either way, please file all new bugs on our github account: Sign in to GitHub Ā· GitHub
And as @nathanr said already:
Honestly, itās more common to get zero back.
Hi Carey, NathanI
Regarding the latest build of Komodo 9 (Apr/15): I tracked now in github the color issues, but when trying to track the blinking of the screen while resizing the lower panel, the github webpage didnāt allow me to attach a quick movie. If I remember correctly, the old bugzilla website allowed you to attach movies, which is in fact a relevant thing when reporting bugs in an interface.
Regarding those bugs reported time ago but not addressed (mentioned in my previous reply), I received now a message: āPlease move this issue to github if you are still experiencing itā. Again, please donāt take these comments wrong, Iām only trying to provide a view from the other side of the road: if you decided to move bugs from bugzilla to github, I think it is not a good idea to ask Komodo users who tracked issues to do that move. Also, in the particular case of [Komodo Bug 102155], this request to me came after I added a note saying that I am still experiencing the issue in Komodo 9 latest built from April/15. The same situation with regards to [Komodo Bug 102211].
Nathan, Carey, Iād like to say again that Komodo is the best editor for mac that I am aware of (and I think I know all the good ones). My comments here were definitely not to disqualify anything but just to echo a feeling that seemed to me expressed also by some others, regarding perhaps minor details that are however visible, reported some time ago, and where fixing them can improve concretely the perception of this really fantastic Editor. Anyway, I read in your replay Nathan, that you are already putting time aside for this, so I am looking forward. Meantime I decided to start using K9 regardless of the issues I tracked, precisely in order to be able to give you more feedback.