[moonchrome]

Plugins are very brittle and hard to read - courtesy of coffescript/javascript - constant 'undefined' error popups and the likes - given up on trying to fix/report as it seems to be a whack-a-mole just using it as a basic text editor and removed all fancy plugins.

Very slow search with large files, rendering performance not the best but tolerable.

On Windows it doesn't let me enter ']}' characters because of my keybord layout conflicting withing with shortcuts (can't tell if this is still the case it was in 1.0 - I haven't used Windows in a while)

I use it for editing python scripts/resource definition YAML files in my asset pipeline and since it mostly comes down to file organization having an actual tree view view where you can cut/paste files and visualize the structure with nice icons beats ASCII art from NERDtree. Also QtCreator project structure with CMake is immutable so I use it to move organize C++ source files as well. It works as a treeview + texteditor and it integrates with git - that's good enough for what I need.

[clumsysmurf]

"courtesy of coffescript/javascript" ... I wonder if switching to TypeScript for most development would help.

[mikekchar]

Although I'm a huge statically-typed language fan, I suspect it would not. I don't think the language is really the problem here. I think it's more that the environment is young. It will take time for the higher quality plugins to supplant the lower quality ones.

You can see the same thing with Node modules. The quality of the main modules that people use has gone up over the last 2 years or so, IMHO. This is not because the modules have gotten better, but rather that people have switched to the better modules over time.

This year I wrote a lot of coffeescript code. I really like it. I don't think it is harder to write good code in it than any other language. I think the main problem is that it is more accessible than some other languages and so attracts relatively novice programmers.

Having said that, TypeScript has been on my TODO list of languages to try for ages and I haven't actually written any code in it. I'm mostly saying that I don't expect strong typing to magically fix the problems with poor plugins. People will just find different ways to make mistakes ;-)

[moonchrome]

>Although I'm a huge statically-typed language fan, I suspect it would not.

Most of the bugs I've dealt with would be fixed by static typing (undefined property use, recursive dependancies, etc.) and it would give more structure to the plugins + make the API self documenting and toolable which would make it easier to drop in and fix the issues