[mikko-apo]

Code style shouldn't change the value of code in any way. If it does something went horribly wrong :)

For me code's value comes from what the code does and how elegant the overall implementation is. Code's value definitely doesn't come from formatting or "style".

[Jare]

Code is not only written and executed, it is also read and modified. Bad, broken or inconsistent style can harm readability, and thus maintainability, which detracts from the value of a codebase. It's often easy to fix compared to bad design or architecture, but it does have a cost.

[mikko-apo]

Yes definitely, you're right. What I mean is that bad design or bad architecture can take months to fix while most editors can fix formatting automatically with a few clicks. At the same time I prefer my own projects to have very clear and consistent style.

I think the original poster (and the topic here) is using way too strong words for such an irrelevant issue. It's airbnb's project, they get have their own opinion. Their style guide won't ruin the Javascript community.

Also, the original poster seems to be on a mission of his own. He forked the project @ github, did a few modifications and changed the documentation in a way that conflicts with the original MIT license. Poisonous attacks like that are what destroy communities.

https://github.com/JacksonGariety/javascript/commit/e06e9a46...

[route66]

Do we agree then over the absolute measure of "elegance"?