Coding style guideline for modules about espruinodocs HOT 4 CLOSED

And also since the modules can be minified to save the memory, I wonder what is your take on this.

Does it still make sense to manually obfuscate code (no spaces, new lines) etc to make it as small as possible? Or is it better to write readable code for these who want to learn/analyze and then serve a minified version to others?

from espruinodocs.

There was actually a bug for this here: espruino/Espruino#209

I suppose I could link to the www.espruino.com/Performance page? most of the performance-related stuff would be common.

The current 'template' module on that page is designed such that it'll minify down really well (at least the way we do it at the moment). However I guess if people write code in an inefficient (for Espruino!) way, minification won't help with that at all!

from espruinodocs.

Yes, I think the performance page should be linked in the Writing Modules tutorial, it has some really helpful and JS specific information.

But I was also thinking about something formal like Espruino/CONTRIBUTING.md i.e. do this, do not do that. Module base is growing (yes!) but everyone uses whatever style he likes which doesn't help if you are using linters or more advanced IDE.

I guess if one analyse the module example then he can figure out: oh two spaces, semicolons etc but it's not really obvious.

from espruinodocs.

Looks like it moved to #475.

from espruinodocs.