Skip to content

Instantly share code, notes, and snippets.

@paulodeleo

paulodeleo/notes_on_pluralsight_react_webinar.md

Last active June 23, 2016 18:57
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save paulodeleo/3f46a05b24bac86416d3941ffa517e46 to your computer and use it in GitHub Desktop.
Save paulodeleo/3f46a05b24bac86416d3941ffa517e46 to your computer and use it in GitHub Desktop.
Download ZIP
My notes on "Pluralsight webinar: Is Your Team Ready to Use React.js?"
Raw
notes_on_pluralsight_react_webinar.md

Title: Pluralsight webinar: Is Your Team Ready to Use React.js?

Webinar date: 06/23/2016

URL: https://cc.readytalk.com/r/ec0c44k4trzl&eom

Description:

There are a seemingly endless number of new JavaScript frameworks and libraries to pay attention to and it’s often hard to decide which one is best for your project or workflow. In this screencast, we take an objective look at Facebook’s React.js library and explore its learning curve, performance, and real-world uses by businesses like Paypal and Airbnb. We’ll compare React.js to popular alternatives like Angular and jQuery to show why it may make sense for your team to start using React.js in your front-end workflow.

  • pros

    • state object
    • declarative vs. imperative code
    • virtual dom
      • partial updates (diff)
    • just a view lib, not a complete framework
      • start small
      • no need to start with Flux and Redux bundled
      • no extra template engine, just plain html

  • cons

    • weird syntax (ES2015/babel?)
      • html mixed with js
    • this this, this that, bind this... :(

  • not sure

    • possible with jquery, not recommended
      • for ajax?
    • server side rendering
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment