3 ms·

How about: RTFM https://facebook.github.io/react/docs/getting-started.html https://facebook.github.io/react/docs/getting-started.html I don't get the react hyp

• andy_ppp 10y ago
  Yeah, the jsx bit is weird to start with, the best bit is changing data diffs the DOM and updates it for you. However, unless building a madly complex UI I've decided it's best avoided; mostly because now that I can build super complex UIs I probably will rather than simplify things that can work in a progressively enhanced way.
• jon_kuperman 10y ago
  haha that's the 5th link in the blog post
• Pfhreak 10y ago
  Everyone has different mechanisms for learning. As someone who learns from manuals, tutorials, and videos simultaneously, a new technology presented as a wall of text can seem impenetrable until I've watched another human make something happen. Then, I can loop back to that text armed with a little context. Videos are often examples of how to develop with the technology outside of a bubble. (Using React? Consider setting up webpack!) That seems to be missing from manuals sometimes.
• walmartian 10y ago
  Separating html out into a separate file/template always seemed weird to me. In every JS Framework HTML and Javascript are tightly coupled. JSX is also javascript, not HTML.
• firasd 10y ago
  The argument (among others) is that if you're going to be using if/else, for loops, and all that in a templating language you might as well use a full-featured language like JavaScript... (youtube timestamp: https://www.youtube.com/watch?v=x7cQ3mrcKaY&t=4m13s https://www.youtube.com/watch?v=x7cQ3mrcKaY&t=4m13s)
  • leeoniya 10y ago
    or, you know, just write the app in pure javascript and still reap the benefits of [2-3x faster than React] virtual dom. though i'm a bit biased [1] ;) [1] https://github.com/leeoniya/domvm https://github.com/leeoniya/domvm [2] http://mithril.js.org/ http://mithril.js.org/
    • a13n 10y ago
      Meh since when is computational performance really a bottleneck? Do you find your site is loading seconds too slowly because JS is executing? I sure don't. On today's machines the much larger bottleneck is how fast and easily you can iterate on product at scale which is a problem that React is a fantastic solution for.
      • pigeons 10y ago
        Actually I do find javascript making many sites that are ultimately just displaying text, so slow as to be unusable.
        • a13n 10y ago
          How do you know it's the JS executing and not network time or the result of a poor infra decision?
          • pigeons 10y ago
            Because it works great with JS turned off, and you can measure what is using your CPU an d what it is doing and how much time it is taking (also you can measure the network).
      • deleted 10y ago
        [deleted]
      • leeoniya 10y ago
        > Meh since when is computational performance really a bottleneck? Ever used a phone that wasn't < 6 months old to browse the modern web? > at scale React is a front-end framework. The only "scale" that exists in its world is the fat DOM you generate and how fast it can mutate it. From that perspective, it sucks at scale (take a look at Preact and Inferno). Your iteration speed depends on good app architecture, not a specific framework. React Native does sound like a good perk, but likely isnt useful enough to make anything you cannot do anyway in HTML5.
• wrs 10y ago
  JSX is entirely optional and it is easy to use React without it. (e.g., http://ludovf.net/reactbook/blog/reactjs-without-jsx-part2.html http://ludovf.net/reactbook/blog/reactjs-without-jsx-part2.h...) (I hope the comment doesn't indicate that you think the interesting thing about React is JSX.)