Choosing a development tool based on its popularity isn’t a bad idea. Popular tools are usually more stable, and they often have more resources and community support than less popular tools.
Developer Satisfaction is another key indicator of a good tool.
React vs Angular
Let’s put them face to face for more comparison points that might be of interest to some developers.
Angular: Component-Based Framework using Typescript
Angular: 2-way data binding
React: 1-way data binding
Angular: Quite large and since it needs to be shipped to the client side, it increases the initial load time
React: Quite small in size, especially when compared with Angular
Angular: Quite steep, given the number of features and options you have in Angular
React: It’s easy to pick up and learn
Angular: Comparable to React, Angular 2 and 4 are some
React: Faster than Angular thanks to the Virtual DOM
Angular: Quite complex
React: Fairly simple but takes some time to set up a project and configure everything
Angular: Easy to scale thanks to the power CLI and generation tools, It’s also used by many large companies.
React: Fairly easy to scale and is quite testable which facilitates the scaling procedure
Gulp Vs. Grunt
How To Choose
I don’t think there’s any question about the fact that both Grunt and Gulp are great tools and have helped people save countless hours of time over the years. Grunt is a bit slower for now, but has a much bigger community. Gulp is faster, has a cleaner API, but is lacking the user base.
I think that the decision will ultimately come down to continuity, available plugins and preference.
(1) If you’ve been using Grunt/Gulp for a while now and you’re happy with it, there’s no reason to switch.
(2) If your project requires plugins which are not provided by Gulp and you’re not prepared to write one yourself, you will need to go with Grunt.
(3) If the above two considerations do not apply to you it will come down to preference. I suggest trying out both and seeing which one sticks with you.
As I said, I chose to use Gulp because I like its cleaner API better but I am perfectly comfortable using Grunt if a project calls for it. What you should not do is read that Mr. Know-it-all said that Gulp is better and accept it. While there are differences, there is no clear winner and both projects can, and will, coexist. Try them out and make up your own mind.
npm vs. Yarn
2016 was the year that Yarn emerged onto the scene as a new alternative client for the Node.js package registry. npm remains the default package manager for Node.js, but extreme growth is expected for Yarn. It seems to be on track to be the preferred client to the Node.js registry due to its performance, which is several times better than that of npm.
His answer: "Probably no,” since the foundation doesn’t want to do anything that might fragment the ecosystem. So while Yarn was talked down in a recent foundation meeting, the members did express interest in its performance gains. Lewis says a more likely outcome is that npm will begin incorporating Yarn’s features and remain the default path to the Node.js package registry.
Mocha Vs. Jasmine
Native apps Vs. Apache Cordova
So while these are the frontrunners for JS mobile frameworks for the moment, expect React and AngularJS to be here next year, when they will likely be the tools of choice for PWAs.
Sublime Text Vs. Atom