Echo JS 0.11.0

<~>

tracker1 1845 days ago. link 4 points
Having tried all of the editors listed, VS Code is hands down my favorite.  What is funny is when I first heard about it, I almost rejected it without trying it because of poor experience with Atom and Brackets around that time.
jscharting 1844 days ago. link 2 points
I felt the same about VS Code. But it's pretty nice now. Still, my personal favorite is WebStorm. 

What editors do you guys use/prefer?
Ash 1843 days ago. link 1 point
I'm not sure why, but VSCode still doesn't feel comfortable to me. I suspect it's the best option for TypeScript and I'm missing out.

I'm really interested to try Panic's Nova. The Electron based editors have some amazing features, but I miss having a native editor. The last native editor I used was Chocolat (: https://chocolatapp.com/.
reveltas@gmail.com 1840 days ago. link 1 point
There are many "fields" in JS, each different, each being somebody's specialism or just dilettante's point on the CV: micro npm packages - separate field. React development, ex-Front-End - separate field. Back-end development in JS - separate field. List goes on, up to people who specialise in CSS somewhere in a big agency. What perplexes me is that specialist in one of the fields starts to make observations over the whole ecosystem. From my field's perspective, micro npm packages development - there's no other option than Atom because atom ESLint plugin offers rule autofix blacklisting (bug on VSC raised https://github.com/microsoft/vscode-eslint/issues/719). We are all JS developers, yet some of us don't even realise "other JavaScript" exists, boxing everybody into "The JavaScript" group based on their specialism.