4 ms·

Now I don't know what to believe: https://imgur.com/gallery/jL62c https://imgur.com/gallery/jL62c

• cdelsolar 10y ago
  Don't use it. I used something called JS stack from scratch (it's a github repo). You set it all up but along the way it teaches you everything. It worked perfectly. The only JS I'd done before that was Backbone stuff and requireJS.
  • zappo2938 10y ago
    I about to convert backbone views in a standing app to React components. Then eventually convert the backbone app to React much later. Do you have any advice, tutorials, and code repositories that would help me?
    • cdelsolar 10y ago
      The "Thinking in React" doc on the main React page, and their tutorial, were greatly helpful, and it was about 80% of my reference docs. I didn't bother with trying to interface with existing Backbone models, but your app may be too huge to rewrite (it still took me several months to rewrite from scratch, but it's a side project so it probably would have been a few weeks if full time). That "js stack from scratch" repo is also very helpful in setting up the whole build.
  • wishinghand 10y ago
    I'm more of a fan of Vue and it's CLI launcher, I was just pointing out the two high-visibility opposing views which I'm sure add to the frustration.js that devs old and new experience.
• lj3 10y ago
  I don't know if this sort of thing has me concerned or optimistic. On one hand, most ecosystems have a set of standard practices ("best practices"). This can take a lot of ambiguity out of learning and using a new ecosystem. On the other hand, some communities have chosen best practices that seem a little odd (I'm looking at you, PHP. If I wanted to write code in Java, I'd use Java). If nothing else, this makes asking React based interview questions complicated.