#3. Configuration is a problem:
I'm a long-time Atom
it got a lot of heat, if you can remember, for creating a
everyone was using sublime, and complained
and how web-developers were all fools.
they were right.
but Atom built an editor that was
massively-configurable, using the web-stack.
some had a
some even had ~50
but Atom had many-thousands of
weird amateur plugins.
You could drink too-much coffee and find yourself installing
dozens, at a time.
there was this chaos of fighting config, and cascading
it was kind of awesome.
but at the end of the day, the final-truth was this:
that's direct manipulation of the editor using CSS in
your config folder.
there was no plugin API here - you
could open devtools, poke around, then change a padding somewhere.
that is glorious, IMO.
this is what kills me about vscode -
They worked so hard creating an enormous API-layer, for people to
so they can config A, B, and C.
then users want to change D.
they're told there's not an API for this.
i would understand if vscode were
written in Qt or something,
and they were limited by their framework
but it's a webpage!
you can change it, already, for free.
let people do it!
and everyone will spend less time whining on github.