Why put the interface at the bottom instead of the top? about angularjs-style-guide

[jackfranklin]

For me it's because I'm used to reading code from top to bottom, and I'm used to seeing what is exported by looking at the bottom of a file. This is a really common pattern in JS, particularly in NodeJS applications. Also, we think it makes more sense (at least to us) to have the definitions of the functions that are to be exported before the export of them.

[feelepxyz]

Adding to this, having exports at the bottom fit with how you usually structure public/private code. So you will put your private functions and variables at the top, then re-use them in public functions. Having public exports at the top would work if you are using function declarations, but not work for variables/func expressions, so you will then end up having private variables followed by public exports and then private function declarations. It's just a bit easier to reference undeclared variables/functions.

[dancancro]

Just one more question. Do you think there's a problem with having too many private variables in a class and if so would something that encourages you to use fewer of them be a good thing? That was a point made in the other conversation supporting the placement of the return at the top after a preferably short list of private vars.

[feelepxyz]

Interesting point, never really thought about it that way tbh. We have generally just kept a limit on the length of our functions.

[jackfranklin]

Do you think there's a problem with having too many private variables in a class and if so would something that encourages you to use fewer of them be a good thing?

Personally I don't think so - I'd rather a module have lots of private and fewer public than the other way round. Generally if a module is doing too much that will be apparent by it exposing way too many things that are often only tangentially related.