Ruby x JavaScript???

Adao Natalino
3 min readJun 11, 2020

Time is flying faster than I can think it’s, especially due to Covid-19, so I am already in the middle of mod 3 (out of 5) of the course at Flatiron School.
This mod is about the front-end development, so we are learing HTML, CSS and JavaScript at the same time. Of course JS is the most important one and where the cool thiings happens!
Because we learnt Ruby the previous mods, its natural to compare JS and Ruby as languages, so I’ll mention some comparations that always come to my mind.

Ruby == friendly and nicer!
Ruby has a syntax that is more restricted, it follows it’s conventions. But is straigh foward and easy to read. On top of that, Ruby tells you specifically what kind of errors the code has, as well as which line it’s, so its easier to debbug the code.
JavaScript doesn’t care much about it, and the browser will try to run everything, even with some mistakes.

JS is “flexible”
Because JS is the most used language in Web Development, we can find much more material about JS than Ruby, to be specific, over 6 times more “results” on google!

This makes it easier to find information, but at the same time, it’s harder to find the correct one because JS has different possible syntax and a lot of distincts ways to follow and solve the same problem (ES5, ES6 and counting).

They can also remember each other!?

Yes, they can remember each other a little bit, here are some examples:

And so on so forth, we also have filter in JS (select in Ruby), reduce, find and others.

The big point is, there’s NOT a lot of options, whether I like it or not, I have to learn, and I’m starting to get it!

I think…

I hope…




Adao Natalino

Software Engineer with a Mechanical Engineer background.