Master

This PR includes just some minor cleanups that should not have any impact on the functionality
@tipiirai I understand what you mean and why we needed to use "==" on the render method. I added this tests that cover the that behaviour here. In the render method we are using the "==" inconsistency to our advantage but in all other cases we are not. Even tho it is 1 more character the identity operator "===" is faster because it don't try to convert values. 
 
The performance improvement of `===` very small, the reason why I think we should use `===` by default is to follow the standards. On the render we can still use the `==` because we have a good reason for that, but there is no reason for doing `==` on other parts of the code because it is confusing to do so and other developer won't know if we are using `== ` for a good reason, like on the render, or just for the sake of rebeling agains standards :P