2 ms·
You interpreted hackability = ability for you to spend your time hacking on it. But I think they were going for hackability = other people will be more likely
by hombre_fatal 8y ago
You interpreted hackability = ability for you to spend your time hacking on it.
But I think they were going for hackability = other people will be more likely to develop plugins. The lower barrier to entry is basically one of the major upsides of Atom/VSCode: their plugins tend to have cutting edge support.
For example, iirc Atom was the first to have a good plugin for Elm lang (elm-jitsu). Meanwhile the Elm plugin for Jetbrains' IntelliJ came later as the result of the effort of two Microsoft employees spending billable time on the somewhat academic project.
A better example is that the creator of elmx ("JSX for Elm") was able to create an Atom plugin for their basically experimental library: https://github.com/pzavolinsky/elmx#atom-integration https://github.com/pzavolinsky/elmx#atom-integration
I also think this differs from "hackability" when used with Vim/Emacs which does mean "you will be hacking together your .*rc file" which is definitely not how I'd characterize VSCode/Atom.