3 ms·

Despite all the talk, there isn’t a world of difference between how apps used to be written 10 years ago and more modern frameworks. The tooling and the languag

Despite all the talk, there isn’t a world of difference between how apps used to be written 10 years ago and more modern frameworks. The tooling and the language have evolved, but you still manage state in similar ways, fetch data, build components, render. Mainly you’ll be managing the rendering lifecycle manually in Backbone, which you’d end up doing in React anyway to get the best performance for an app like this - you’ll get molasses if you naively build a spreadsheet in react. One thing I consider a huge advantage: you can read and understand the source in one afternoon. Makes debugging and optimization a lot easier.

s3arch 5y ago
>you’ll get molasses if you naively build a spreadsheet in react. I digged a bit more on other real world applications. Found two interesting posts from atom text editor implementors. [1] Why they moved to React. [2] Decision to implement text editor DOM updates manually instead of via React [1] https://blog.atom.io/2014/07/02/moving-atom-to-react.html https://blog.atom.io/2014/07/02/moving-atom-to-react.html [2] https://github.com/atom/atom/pull/5624 https://github.com/atom/atom/pull/5624