Though we’ve been Ruby lovers for the past decade here at Novelys, we’re always keeping an eye on other languages and ecosystems. We’ve been playing around with google’s
go here and then, and recently I was trying to achieve something that I was quite used to do in
n parallel requests to various apis, then wait for all of them to complete and move on. In a way, it is the opposite topic of a previous blog post, in which I did not wanted to wait for all of the requests to complete before displaying feedback.
We had another opportunity to use Ember.js in a client project recently. The application is a kind of video aggregator: the front page loads many rows of videos, each coming from a different source. Since the various requests can take some time, we want to display a spinner for each row. Nothing too fancy or unusual here.Continue reading »
At Novelys, we have been developing and maintaining a sales book for Eckes-Granini for a few years. At some point, they contacted us regarding some features they wanted to add to the application. With the client, we decided it was best to start from scratch, remove the cruft, and benefit from the best technologies that were now available. This post is going to dive into some of the technological choices we made and why.Continue reading »