Leaning on community support seems ideal because it means you've built a powerful plugin API and people can implement features.
As opposed to having a weak plugin API where all progress depends on the tiny internal team.
The latter suffers more than the first if popularity wanes.
In Atom's case, its lunch was eaten by VSCode which was similar but just better. Based on web tech but with better performance and just as powerful of a plugin API. It wasn't the fact that they let people implement plugins that killed Atom, and they would have been in an even worse situation had they not had a good plugin API.
And Sublime, BBEdit, TextMate, Notepad++, Ultraedit, Slick, vi, vim, XEmacs, Emacs, nano, joe, jEdit,....
It was a good time, but it always left me wondering how long it would last as it leaned heavily on community support for nearly everything useful outside a few packages
Such a situation makes me worry about it keeping up if popularity wanes. With JetBrains for example at least I know that paying for the editor it will keep getting proper updates and support even if it isn’t the most popular (though it is quite popular currently)