ideas of further coding conventions

[maybeec]

This ticket can be seen as experience report and collection under construction, where anybody can introduce and discuss coding conventions.

• never change prototypes after instantiating it or inheriting from it! -> very slow due to runtime implementations
• use parseInt and parseFloat to fix the number radix rather than use implicit type coercion
• use === over ==, document == uses!
• No expressions without a dot! (especially for templates & scope access)

[maybeec]

I would like to evaluate the angular1/2 style guides by johnpapa. We then should reference this style guide and my make changes based on that.

As an example for change: do not specify a service api by a return object containing function references on top of the service. This confuses newbees and makes code look odd, especially if the service implements further service global variables.