Petr Bambušek

Microsoft has massive expertise in writing development IDEs and it's really visible. Every since they released Visual Studio Code we benefit from its constant improvements. I can't imagine writing code in anything else anymore.

This was no real choice - we switched the moment Yarn was available, and never looked back. Yarn is the only reasonable frontend package manager that's actually being developed. They even aim to heal the node_modules madness with v2! Npm is just copying its ideas on top of introducing massive bugs with every change.

Writing code without static analysis tool is like driving blind. We choosed ESLint as it's clearly state of the art on frontend and supported by large ecosystem of plugins for various specific problems.

I'm not sure when it happened, but TypeScript is the new cool kid around the block. And we can see the massive potential it's unlocking when included in large scale codebase like ours. Types saves lot of mistakes, questions and searches for documentations, and we're happy to have them.

Have you ever tried to develop and debug large scale 2-way data binding? We did. And that's why we were happy to adopt single-way dataflow pattern that is central to the Redux.

We started with React when it was still in early stages (I think around version 0.13). Back then, it was major step up over plain HTML templates that just weren't debuggable at all. Together with emerging Redux (Flux in that time) pattern it took frontend by storm.