A system of permissions for plugins would be welcome in my mind for Atom, similar to browser plugins or mobile apps. Then a new "feature" would require the "transmit your code to a third party" permission.
My hope is that the core of Atom isn't so bloated with GitHub integration and that integration is optionally available through the plugin management system. I'm of the type who prefers to use the text editor just for code and other tools for source control and project management.
I really hope they'll improve the discovery of third-party plugins, the repertoire of available atom plugins is insane, yet finding something you want is still a /lot/ harder than with sublime + package control...
Are there specific features of Atom that aren't in Code? It seems that Code could likely add some of the features missing that are in Atom easier than trying to merge them, or go the other direction.
They could probably also merge the two somehow. The one thing I like more about Atom (even though I don't use it anymore) is editing the editor settings gives you a UI instead of just a JSON file which I don't mind, but it's kind of uneeded to me to have to work harder just to check all my editor settings.
for me, atom’s initial value proposition way back when was, (well, in addition to the customizability/programmability) the third party plug-in ecosystem. It was a pretty big deal for me at the time not to have to wait for my code editor to release an extension for that-one-thing-I-use.
Atom is slow for larger files, but the vast amount of third party plugins is a great asset.
You can add them for things like syntax highlighting, but they can do so much more, and in many cases can border on "IDE-level" features.
Things like autocomplete, code linting, smart refactor tools, find reference/definition, test runners, debuggers, git integration, and a ton more. (one that I use a lot adds a terminal in the browser so I can run some command line tools without having to tab away to something else)
They are pretty limitless. If it can be rendered via HTML/css/js, it can be a plugin.
So, what prevents any Atom package from being silently taken over and turned into a private code Hoover? Is there anything in Atom's packaging APIs that ensures plugins that can read source cannot also access the network without permission?
reply