Coffescript revisted…

…and thrown out

A few months ago, I wrote a post telling you all about thought of venturing into using CoffeeScript over regular JavaScript. Now that I’ve had some more time to think about this, I’ve come to a conclusion…

Thanks, but no thanks.

Don’t get me wrong, I like the idea of CoffeeScript. Specifically, the idea of limiting or removing usage of semicolons, curly braces, and/or parentheses sounds great in theory — the less to type the better, right? If you asked me back in August when I wrote that post, I would have definitely agreed.

However, with practice comes clarity. The more I used JavaScript, the more comfortable I became with it. I began to type those semicolons, curly braces, and parentheses like they were second nature. I wasn’t spending most of my time figuring out where that missing one went (we’ve all been there). Sure, I still forget them every once in a while, I’m not perfect.

Being perfect. Let’s talk about that. Will it happen? I highly doubt it. Can I get close? Absolutely! And that’s the last reason why I’m not going to venture into CoffeeScript right now. I’m still honing my skills with JavaScript — why re-learn how to code it in CoffeeScript when 1) it will just be compiled into JavaScript anyway and 2) I’m still learning and mastering JavaScript. This last point is also the same for why I haven’t begun and ReactJS training — I’m still trying to master AngularJS. Better to be very proficient in one than mediocre in many.

It’s a humbling thing to admit, but it’s the truth. And being honest with myself is the first step to bettering both me as a person and my skills as a developer.

So when it comes down to it, I think, at least for the time being, I’ll take my coffee in a mug and leave the scripting to JavaScript.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.