shagabutdinov

It's not a framework. It's just a toolbox and set of libraries. There is no inversion of control which is the core point of frameworks.

What are the pros & cons in comparison with production-ready solutions like grafana-prometheus stack / nagios / etc?

Package control does not provide this feature. I talked to maintainers of package control and we decide not to implement this feature (although I could do it by myself) because I'm only the author who need it.

Actually, there are not much really complex plugins for editors; most of plugins it is 1-5 python files that require no dependecies.

I didn't like Atom because of speed and GUI settings (got used to text settings after sublime or vim). And there are migration issues - I have a lot of plugins, settings, project files and knowledge so migration process will take too much effort.

Also, I don't think that it is a good idea to implement CPU intensive real-time applications in javascript (e.g. code parsing or syntax highlighting). There are plenty of languages/tools that suit well for it, there was no reason to pick a javascript as the primary language for a editor.

There is "go to definition" feature that based on syntax highlighting files rather than on real language parsing. It works fine if you jump only across the project and have "vendor" folders excluded.

Today I learned something new about English language, thank you!