yego.me
💡 Stop wasting time. Read Youtube instead of watch. Download Chrome Extension

Ruby Tutorial 6 - Comparisons


4m read
·Nov 3, 2024

Hey guys, this is Mac Heads 101, and today I'm going to be teaching you how to make Ruby answer questions that a baby could answer.

What kind of questions are these? Well, they're very basic comparisons. For instance, is 2 greater than 1? Now, you obviously know that two is greater than one, but the challenge here is to make Ruby tell us whether two is greater than one or not.

I'm going to be showing you a couple of different operators that you can use in Ruby to compare two different values, similar to the way you would do it in math. Ruby will actually be able to tell you yes or no answers based on whether the expression is true or not.

So, let me head up to the IRB console and give you an example of this. Let’s say I have a variable a, which is 1, and a variable b, which is 2. I want to ask Ruby if a is greater than b. Now, obviously, a isn't greater than b because a is 1 and b is 2, and 1 isn't greater than 2, but I want Ruby to tell me that.

So, all I have to do to do this is type a > b and hit enter, and it says false because a is not greater than b. Now, okay, what if I want to ask it if b is greater than a? Well, I just do the same thing; I just flip b and a, just like you'd expect. It tells me true because 2 is, in fact, greater than 1.

Now, there are a couple of different questions I could ask Ruby using different operators. For instance, I can say, is a less than or equal to b? I can say a <= b. Now, I can also ask, is a greater than or equal to b? I can say a >= b, and it'll tell me false.

All right, now let's have a look at the two other operators: there's equal to and not equal to. Now, how you might express these as an operator isn't as obvious as the other ones. So, let's say I want to check if a is equal to b. I wouldn't say a = b because that will assign a to b or b to a, rather. Now, I don't want to do that; I want to compare them.

The comparison operator because of this dilemma is actually ==, so it's two equal signs next to each other, no spaces. So, I say a == b, I hit enter, and it says false because 1 is not equal to 2. Now, what if I want to ask, is a not equal to b? Now this is the opposite of the equal to operator; it will tell me true if they're not equal, and it'll tell me false if they are equal.

I can say a != b, and by !=, I just mean exclamation point equal sign. So, let's go ahead and see what this says. It says true because a is not equal to b.

These don't have to be variables either. I don't have to say a < b or a > b or stuff like that; I can actually just say 1 > 2, and it'll tell me false. I can say 20 < 30, and it'll tell me true. And, you know, I can say 20 <= 20, and it'll tell me true. I can say 20 != 20, and it'll tell me false.

So, I can do various comparisons, and I can even mix variables and numbers. I can say a < 20, and it'll tell me true, and I can say a < 0, and it'll tell me false. In fact, I can actually find the value of a just by using less than or equal to. I can say, is a equal to 3? No. Is a greater than 0? Yup. Is a less than 3? Yup. Is a equal to 2? Nope. Is a equal to 1? Yep. And, you know, I found the value basically using comparisons.

So, this is a very straightforward way to get Ruby to answer a yes or no question when you're comparing two numbers. You can also compare strings. For instance, I can say "alex" == "alex" and it'll tell me true. I can say "alex" == "alex1" and it'll tell me false.

I can also use not equal to, right? Like that. So, equal to and not equal to actually work for strings as well as numbers, and you'll find that this actually works. You know, I can say, is 1.5 > 2, and it'll tell me it is not. I can say, is it greater than or equal to 2? Nope. Is it less than or equal to 2? Yup.

So, I can compare floating points, integers, strings, anything like that, and I can get Ruby to answer in a yes or no fashion. Now, this might seem pretty redundant right now, and you're probably thinking, like, why on earth do I need Ruby to tell me any of this? I can see it with my own eyes, and the answer is it's not that useful when you're writing some code in the Ruby console, but it becomes very useful when you send someone a script.

You want the script to do some logic. So, let's say the user types their age, and they say they're under 16; the script might tell them one thing, and if their age is over 16, the script might tell them something else. In order to do that, the script needs to be able to ask Ruby, you know, is this value less than or greater than 16?

And, you know, you're not going to be around to say yes, it is. You know, Ruby has to make that decision. So, comparisons are very useful for logic, for control flow of your program. They're not so useful in the IRB console.

So I was just making this video to introduce you guys to the various comparison operators. In the next tutorial, I'm going to be showing you if statements using these comparisons, which will allow you to control the flow of your program based on the result of different comparisons.

But anyway, thanks for watching, subscribe, and goodbye.

More Articles

View All
You Are The Center of The Universe (Literally)
A three story building is about 10 meters tall, six times bigger than you. In the opposite direction, six times smaller than you, you get things like a cute squirrel about 27 centimetres small. So the building is just as big relative to you as you are to …
My Advice for Each Stage of Life
There’s a life cycle, right? Your teens, your 20s, your 30s, and so on. Every phase is a little bit different, or quite a bit different. People have asked me, uh, in their 20s, what is good advice for their 20s? You are about to go independent. You were d…
This Video Will Hurt
Please, put on your headphones – I promise that there won’t be any loud sounds, but this video is going to hurt. There’s a study about hypersounds and how they cause headaches: these sounds are too high-pitched to hear – like the one added to this video, …
YC Tech Talks: Designing Game Characters with Deep Learning, from Cory Li at Spellbrush (W18)
My name is Corey, uh I’m the CEO at Spell Rush and I’m here to talk to you today about, uh, designing characters with deep learning. So, um, we’re Spell Rush. Uh, we’re a YC company as well. Uh, we’re building deep learning tools for art and artists. Uh,…
Rick and Morty Writer: Ryan Ridley
All right, man. We should probably jump into Rick and Morty at some point. Um, before we do that, uh, how about you just like give your background of up until Rick and Morty? So, I didn’t really know what I was doing with my life. I was a terrible studen…
Sal Khan chats with Google CEO Sundar Pichai
It’s huge treat to have Sundar Pichai, CEO of Google, here. And you know I will give a little bit of a preamble more than I normally do. I think a lot of the team knows this, but it’s always worth reminding the team we wouldn’t be here on many levels if i…