During my work on web project for US client, I faced with interesting issue, which at the first look seemed to be related to D3.js/C3.js donut charts, but after deep debugging, I discovered it’s because of nature of Underscore.JS 1.6.0 library/code. I would say, it’s bright example of the fact how important to know main purpose of dedicated API/tool, and implement custom codebase for the future to be working also correct.
The fact is – Lodash.JS is nice competitor for Underscore.JS. There are so many thoughts in a community regarding how different and how good they are. This post is about Backbone.JS and required dependency of Underscore and my willingness to BE SURE, that replacement/migration is OK. So I asked myself:
How good Lodash is against Underscore in scope of Backbone.JS stable/correct work?
And as turned out, I found more than answers, I found “future”. 🙂
UPD: Below notes are valid for Backbone with versions
1.3.3 and Marionette
2.0.*. Aug-23-2016 Marionette release
3.0.0 major version with many changes, including API and function name changes.
During my work on a new brand project based on Backbone.JS in scope of my current employee company, I faced with comprehensive task – get the best Internationalization solution to meet project goals. At first glance, it seems to be simple task – like resource bundle (file where I may store strings which are repetitively used or should bee able to re-configure with no coding). But it turns out as more complex task.