Why we moved from Angular 2 to Vue.js (and why we didn’t choose React)

  • My conclusion about Angular 2 was simple, the only thing Angular 1 and 2 share in common is the name, they are completely different frameworks.So consider that we had 17 versions to upgrade on a non-tested system, a lot of pressure from the business to write new features, lots of bugs and poorly written code, the original developers weren’t on the team anymore, only one developer (me) at the time with many other responsibilities, Typescript, problems with finding the right documentation since I was using a beta, and Angular 2 moving to version 4.
  • I got a good understanding of the basic concepts of Vue.js, defined a good and extendable architecture but most importantly I really enjoyed the experience of writing code with it and I felt I was doing it faster that with React.React was a lot harder than I thought, choosing between Redux and MobX is more problematic than having one option that is well integrated with the framework like Vue.js and Vuex do.
  • React took the most mentions and Angular 2 came in a distant second place.I started to look for local talent with Vue.js experience and I did find some who were really good so I started to think that I was not alone, my social techy circle was probably too small and I shouldn’t play enough attention to the fact that I didn’t know anyone in person working with Vue.js on production.MobileAt the time we were thinking about Vue.js vs React, we were also considering rewriting our mobile app and React Native looked like a really good choice.
  • Twitter is another good example, they released Bootstrap under the very permissive MIT License and no one is talking about License problems with Bootstrap.Final wordsOut of the many web pages I researched before making a decision, one graph caught my attention, the developer satisfaction on The state of Javascript survey that Sacha Greif @sachagreif does every year.
  • You can read The State of Javascript on the following link.Overall, Vue.js was the the winner in our evaluation, it had many questions answered on Stack Overflow, the clearest official documentation of the three options, the smallest code base, integrates well with Bootstrap and learning that it was backed by strong projects like Laravel and a big company like Alibaba was a big plus.

At Rever (www.reverscore.com) we just released a new version of our web client using Vue.js. 641 commits and 16 weeks of intense development after with two resources, here we are, very proud of a…
Continue reading “Why we moved from Angular 2 to Vue.js (and why we didn’t choose React)”

Why we moved from Angular 2 to Vue.js (and why we didn’t choose React)

  • My conclusion about Angular 2 was simple, the only thing Angular 1 and 2 share in common is the name, they are completely different frameworks.So consider that we had 17 versions to upgrade on a non-tested system, a lot of pressure from the business to write new features, lots of bugs and poorly written code, the original developers weren’t on the team anymore, only one developer (me) at the time with many other responsibilities, Typescript, problems with finding the right documentation since I was using a beta, and Angular 2 moving to version 4.
  • I got a good understanding of the basic concepts of Vue.js, defined a good and extendable architecture but most importantly I really enjoyed the experience of writing code with it and I felt I was doing it faster that with React.React was a lot harder than I thought, choosing between Redux and MobX is more problematic than having one option that is well integrated with the framework like Vue.js and Vuex do.
  • React took the most mentions and Angular 2 came in a distant second place.I started to look for local talent with Vue.js experience and I did find some who were really good so I started to think that I was not alone, my social techy circle was probably too small and I shouldn’t play enough attention to the fact that I didn’t know anyone in person working with Vue.js on production.MobileAt the time we were thinking about Vue.js vs React, we were also considering rewriting our mobile app and React Native looked like a really good choice.
  • Twitter is another good example, they released Bootstrap under the very permissive MIT License and no one is talking about License problems with Bootstrap.Final wordsOut of the many web pages I researched before making a decision, one graph caught my attention, the developer satisfaction on The state of Javascript survey that Sacha Greif @sachagreif does every year.
  • You can read The State of Javascript on the following link.Overall, Vue.js was the the winner in our evaluation, it had many questions answered on Stack Overflow, the clearest official documentation of the three options, the smallest code base, integrates well with Bootstrap and learning that it was backed by strong projects like Laravel and a big company like Alibaba was a big plus.

At Rever (www.reverscore.com) we just released a new version of our web client using Vue.js. 641 commits and 16 weeks of intense development after with two resources, here we are, very proud of a…
Continue reading “Why we moved from Angular 2 to Vue.js (and why we didn’t choose React)”

Do I need Node.js in the backend?

Do I need #nodeJS as a #backend when I use #reactJS?

  • Like any other frontend library (jQuery, etc), it is happy to be served by any old webserver – Apache, NGINX – or any kind of backend – PHP, Rails, and so on.
  • Lest we lose track of how the Internet works, here’s a diagram to anchor the discussion:

    Since React and Angular are purely client-side libraries made up of JavaScript files, any old HTTP server can send them to users – PHP inside Apache, PHP inside Nginx, plain Apache/Nginx, Java Tomcat, Rails inside Passenger, and yes, Node.js.

  • I said that React doesn’t care what your server is doing, which is true…

    But if you add React Router to your project, and you want to use its feature, the server must serve up your page no matter which URL the user accesses.

  • Though if your backend is not Node.js, you’ll probably want the last step of your build to be “copy the built files to my server’s root directory.”
  • Alternatively, you could set up Webpack to serve your React app and then proxy all other requests to your real backend server (whether that’s local, or across the web somewhere).

Can you use React with a PHP, Java, Rails, or other kind of backend?
Continue reading “Do I need Node.js in the backend?”

Interview With Lee Byron, React Developer at Facebook

Join us for a talk with Facebook's @leeb about @reactjs development and infrastructure:

  • You actually need to also include ReactDOM in order to use React in a browser.
  • community, react, grommet, interview, facebook, javascript library, javascript
  • Lee was kind enough to answer a few questions about React that we sent his way.
  • Grommet is a library of reusable UI components.
  • I was part of designing and building the early versions of React and designed the component lifecycle API.

Read the full article, click here.


@grommetux: “Join us for a talk with Facebook’s @leeb about @reactjs development and infrastructure:”


Coming from the folks at Grommet, check out this interview with Lee Byron, from Facebook, talking about his history with React, offering up a few tips, and discussing where he sees the popular JavaScript library headed next.


Interview With Lee Byron, React Developer at Facebook

Do I need Node.js in the backend? – Angularity

Do you need Node.js in the backend?  #ReactJS

  • You can use any frontend library for fetching data – React doesn’t come with one.
  • My site is hosted on a PHP/MySQL backend and I read somewhere that I need to have a Node.js environment in the backend to use these new JavaScript libraries like React and Angular 2.
  • Read on for how to fetch data, deal with routing, and server-side rendering without Node.js.
  • If you want to support server-side rendering (a.k.a. “isomorphic” rendering), whether to increase page load speed or to improve SEO, then React will actually be running on both the server and in the browser: once to render the page server-side, and then again in the browser after it downloads and displays the initial rendering.
  • Server-side rendering is way outside the scope of this post, but even if you do need it, you don’t have to use Node.js in the backend.

Read the full article, click here.


@ReactiveConf: “Do you need Node.js in the backend? #ReactJS”


Can you use React with a PHP, Java, Rails, or other kind of backend?


Do I need Node.js in the backend? – Angularity