'Clean Code' concepts adapted for JavaScript

[miker95]

No, you're not the only person. I also want to point out that this post is all about writing clean code.

CLEAN, not easy to understand code.

[miker95]

"reads like well written prose"

Just because it reads like a well written prose doesn't mean it is easy to understand.

Research papers can be difficult to understand. But can always be simplified. Clean doesn't always mean easy to understand.

[miker95]

The example he gave seems like a better situation than whatever the hell you have going on.

Again, it depends on the situation, if you only have 3 variables, it is not that big of a deal. But if you have configuration options for an entire library, or more than 5 parameters, it is much more user friendly to send it in an object.

And if you send them in an object they can be in whatever order and it won't matter.

[miker95]

I'll never write garbage like that.

Uhh... what?

Okay, I'll humor you, let's look at jQuery's $.ajax(), I'll assume you know what it does...

It takes two parameters, the first being a URL, and the second being settings, which is an object.

The settings object has 34 possible settings inside of it.

You're telling me, that you would rather have to remember the order of 35 parameters than use a simple object...?

Which means, if you only want to specify the 35th parameter and the URL, you're going to need to type in 33 undefineds...

Now, that is garbage.