3 ms·

For more casual user (me) a large plugin ecosystem makes things complicated. It means you need to invest time to understand which ones to pick and this might be

For more casual user (me) a large plugin ecosystem makes things complicated. It means you need to invest time to understand which ones to pick and this might be changing all the time as projects are abandoned and forked. For Eclipse there was (is?) something called MyEclipse which was paid software and contained a curated set of plugins.

nickelcitymario 6y ago
An excellent point. My solution to this would be (ironically) to add one feature to Sublime: Grouped Packages. Simply put, the idea would be to define a set of plugins needed (or recommended) for certain types of development. So you'd install Sublime, and then have a handy popup asking if you want to install any of the suggested Grouped Packages. There might be a dozen or so that are commonly useful for a Rails developer, another group that's useful for C, or for Wordpress, or whatever. That would allow for a minimal text editor, the infinite possibilities of plugins, and also easy onboarding for new users. It would also be useful for advanced users who are getting started in a new field.