We’re not going for the most comprehensive digest out there, but want to focus mainly on covering the technologies already supported in WebStorm as well as the industry’s best practices.
Jake Archibald in his blog talks about web streams and how they will help us take even more control over network processes and improve the performance of web pages.
On January 14 jQuery celebrated its 10th birthday and is still one of the the most popular frameworks for web development. John Resig, the author of jQuery, shares his memories and jQuery milestones. On the same day jQuery 3.0 reaches beta… and it no longer supports IE6-8.
If you’ve missed this news, as of January 12, 2016, Microsoft has ended support for older versions of Internet Explorer (versions 6-8).
Péter Márton shares his perspective on the best practices for developing React apps in 2016. We think the only thing missing is WebStorm 🙂 Don’t forget to check out the WebStorm tips on coding assistance, linting and refactoring for React developers.
While that pull request is still going through the code review, the Node.js community is discussing plans for moving toward VM neutrality.
Sacha Greif, a co-author of Discover Meteor, talks about the current state of the Meteor platform and what went wrong, and shares his hopes for Meteor becoming a back-end platform for building React apps in the future.
The Battle of Task Runners is far from over. Cory House shares his experience of moving from Gulp and Grunt to writing npm scripts (good that WebStorm supports them all, right?!). He believes that Gulp and Grunt introduce redundant abstractions that make debugging really complicated and the whole build process too unstable and too dependent on dozens of plugins.
And a bit more on npm:
- a great collection of tips and articles on npm;
- surprising discovery that disabling npm install progress bar leads to a significant improvement in performance (the fix is on the way).
We hope you’ve enjoyed this overview of January’s trending web topics. We’ll be super happy to hear your feedback on this blog post! Did you like it? Should we continue this type of posts? Let us know!