Pete Hunt: React - Rethinking Best Practices (updated) - JSConf.Asia 2013

I'll try one last time: > Sorry none of this makes any sense to me. If you're not familiar with the MVC variants (MVVM, MVP, MVI, MOVE)[0][1] we should start there. Next you should read through some common mistakes of Backbone.js like applications [link] and some criticisms of MVC on HackerNews in 2012[0]. Finally if you haven't before these talks, they are the ones that sold me on React: - [link] - ▶ this video - [link] [0] [link] [1] [link]

in “React is 10 years old” · View on HN

This is amazing stuff, thanks Dan! Hopefully it is the beginning of the end of refresh-driven-development. If you are a web developer (front-end/back-end), and you haven't switched to React yet, take this for a spin, and read "Facebook just taught us all how to build websites" ( [link] ), and watch 'React - Rethinking Best Practices' by Pete Hunt ( ▶ this video ). The distinction between the back-end and front-end is a product of the complexity introduced by the web with its 'worse is better' mix of badly integrated tools. It made building user interfaces a dark art with all its quirks: - a layouting system that had an active vendetta against humans - Javascript with all its deficiencies - Connascence introduced by Server <-> Client communication (Server Model <-> API View <-> JS Model <-> JS View) - declarative views that were ill-suited for web-apps (logic-less templates, what a lie!) - cross-browser incompatibilities - difficulty in implementing client-side routing - immature developer tooling But worst of them all was DOM mutation and spaghetti code, which was in reality a fundamental deficiency of the development model itself, and not because web developers the world over were being deliberately irresponsible. React is changing all that with the help of ES6. It simplifies web development both in concept and in practice. In a few years, building UIs would be just another part of writing software, and competent Full-Stack developers would cease to remain unicorns. Here are a fe

in “React Hot Loader: Tweak React Components in Real Time” · View on HN

JSX & React were literally built to solve Facebook's maintainability concerns, which is one of the most complex client side web apps I can think of. JSX was a hard sell at first 4 years ago, but Pete Hunt did a great job then, explaining how the false separation of concerns between HTML and JS really is unavoidable. You end up with logic in HTML tightly coupled to your JS no matter which way you shake it. ▶ this video And HTML string template languages have been shown to have numerous shortcomings at scale.

in “Vue.js vs. React” · View on HN

I've always found it weird that many people put the HTML, JS, and CSS for one component in three different files, but never thought enough about it to put it into words. Pete Hunt (one of React's maintainers) does that here: ▶ this video React is about separating concerns, not technologies. Everything you need to know to draw an App Bar is in AppBar.jsx. You can dynamically generate the markup with JavaScript, but that doesn't change your separation of concerns, because everything concerning that component lives in that file.

in “Choosing the Right JavaScript Framework” · View on HN

Pete Hunt addresses this specifically in this React talk starting at 3 minutes: ▶ this video Basically, the idea is that most JS templating solutions separate technologies (HTML , JS, templating languages), but don't actually separate concerns, because the concern is simply generating and updating DOM regardless of how many technologies you use. Most JavaScript frameworks or libraries that handling generating and updating DOM, like Ember's two-way binding with Handlebars and Angular's dirty checking with directives, don't really separate markup from logic. They just invent a new language to mix with your HTML, and that new language is deliberately made extremely weak.

in “Compiling JSX with Sweet.js using Readtables” · View on HN

Respectfully, my experience says otherwise: [link] - JS object appears to be at least 2x faster than document.createElement() (Chrome) - Note: JS object only loosely represents JSX element so it is a bit unfair. But with actual JSX objects I would assume it is still somewhat faster than the DOM API. ▶ this video - Pete Hunt, one of the React devs, says "JSX is faster than the DOM because it is JS memory."

in “VanillaJSX.com” · View on HN