Good Contents Are Everywhere, But Here, We Deliver The Best of The Best.Please Hold on!
+01 (414) 230 - 5550
Dawid Pośliński, Technology

Disclaimer: In this article, the point is not to deprecate other front-end solutions. The main goal is to point out that there is no one single technology that fits every context, i.e. every use case, every project or every development team.


Keep an open mind


If your main goal is just to extend an existing application by adding some extra Javascript to it and you are looking for some fancy tool to do so, EmberJS might be an overkill for the job. Why? In most such cases, you will need a tool for building a dynamic user interface. In that case, you can use for example ReactJS. It will give you much more freedom. You will not have to spend your time working on a sophisticated solution dedicated for Single Page Applications (SPA) such as EmberJS and you can thus deliver a feature faster. If you do not know yet what you will need in the future, the solution should stay as thin as possible and EmberJS is not the best choice for you. EmberJS is more like a ready to use Swiss Knife, but it does not mean you always have to be prepared for a nuclear war.



Following every single rule is not an option. EmberJS is not the best place for being a rebel. Of course, even if you use EmberJS you can mess things up inside your application, but because it has plenty of conventions, it is much more difficult to spoil things than with other solutions. Do you like to do whatever you want? In EmberJS you can’t. With EmberJS you have some rules that you will just need to follow.



It may sound strange but thanks to EmberJS your coding is limited to the minimum. As I mentioned before, EmberJS is like a Swiss Knife. It has tonnes of built-in solutions and thanks to that, in many cases, you do not have to code too much to achieve your goals. For instance, if you want to start using JSON API, GraphQL or FireBase, all you have to do is to replace the adapter of the application. The adapter connects your data source (API) to the local data storage. When you follow the conventions, all of this happens auto-magically — just like that. If you like to write a lot of code, reinvent the wheel, EmberJS is not the best choice for you.

To conclude, we should always look for a right tool to do the job at hand. From my experience, EmberJS is one of the best choices for building a SPA at the moment. But before you pick the tool, ask yourself the key question: Am I really building a SPA right now?


Dawid Pośliński, Technology

Everything started with the idea of making web applications simpler and easier. It was David Heinermaier Hansson who put forward his concept and found other enthusiasts who, as the Rail Coreteam, created and expanded the Ruby on Rails Framework, a powerful development platform today. Since that time, numbers of web developers have been using the Rails and benefiting from many improvements.


Now, we are close to trying new solutions as, at the 2015 Rails Conference in April, David Heinermaier Hannson announced Rails 5, introducing some features added to this new version, which include Rails API and Action Cable. New directions, taken by the Rail team, stem from some changes that Ruby, as a programming language, has been undergoing over the years, and are intended to take advantage of these changes. One path is improving speed; for example, Ruby 2.2.0 enabled its garbage collector to pick up symbols to reduce memory consumption. Also, new Incremental GC will help to save on memory consumption on Rails applications. It is said that Rails 5 will work with Ruby 2.2.2 and newer versions. Besides, we will see some new syntax, adopted from Ruby 2.2.0. (e.g., Keywords, Arguments or Module#prepend).


Some other modifications to improve speed concern API deprecation and cleanup. They comprise removal of the following APIsAction MailerActive record, and ActionPack assertions as well as dead code and unnecessary tests (Chaves, 2015). Other factors that improve performance include fewer object allocations, immutable strings freezing, unnecessary dependencies deletion, and common operations optimization. As it was announced, Rails 5 also introduces new functionalities and new API, integrated into the framework, which results in no need for additional gems (Chaves, 2015).


The list of changes that have already been implemented or are still under development is much longer than we managed to mention in this short discourse. So are our expectations about the benefits, resulting from the presented improvements.


Read more at: