Blog
After sponsoring React Rally in Utah, and ReactEurope in France this summer, there's one thing that’s extremely evident: The ReactJS ecosystem is moving very quickly.
As Angular 2 looms in the horizon, it is easy to be overwhelmed by the upcoming transition. An important topic emerging for many developers is how to align existing applications, or write new ones, using Angular 1.x to ensure the transition is smooth, and to minimize refactoring when Angular 2 comes out. After all no one wants to write an application today that will be obsolete in a year.
Update: Times have changed a lot since 2015 and while a lot of the gulp patterns in this post are still valid the tooling landscape is quite different. Today we leverage gulp as a "general purpose automation" tool that's well suited to projects with complex and unique build requirements. For web application frameworks in most cases we recommend your respective framework's CLI (every big framework has one) or a tool like webpack.
The development of Angular 2 is on its way with much talk, hype, and fanfare. Surprisingly, there is not much being said about unit testing. As a responsible developer, you have undoubtedly already written a giant unit test suite to achieve ‘near perfect' code coverage, and I'm here to let you know there is no need to throw that all away! While Angular 2 is currently in ‘developer preview’, implying that nothing serious should be built with it currently, the Angular Team has already created a giant wealth of unit tests and a custom testing setup. Unfortunately, it is not easy to set this up for yourself. So this post should help you get started.
This month, Rangle had the pleasure of being the lead sponsor of ReactEurope 2015 in Paris. Having used ReactJS and Flux architectures in about a third of our projects in the last six months, we were very excited about this event… And what a fantastic event it was: being well organized, with an amazing roster of speakers and talks.
As the Angular team is making progress towards a “beta” version of Angular 2, it’s time to think seriously about your transition plan. At Rangle.io we have been looking into this topic for a few months now and would like to start sharing what we’ve come up with.
Fill in the missing line of the following code that implements a function returning the next Fibonacci number every time it's called.
The function getCount() defined below is supposed to return the next number every time it's called, starting with 1. (So, the first call would return 1, the next call would return 2, the next would return 3, and so on.)