So far, we've seen examples of how to use dates and times in Ruby.

However, there's a lot more that we haven't taken into account,

things like time zones, offsets, daylight savings, and more.

Let's go into a bit more depth with dates and times now using Workspaces.

When we've been working with dates and times so

far, we haven't been worrying too much about time zones.

Different parts of the world use something called an offset

when taking time into account.

You probably have friends or relatives in a different time zone and may need to

mentally subtract or add hours so that you can call them at a reasonable time of day.

Now, the same thing happens in Ruby and

all programming languages when you're working with time zones.

Now, luckily there are only a few different time zones that we

have to deal with.

No, I'm just kidding.

There are a lot of different time zones in the world.

Each different one on this map is denoted by a vertical bar.

Now, we have just a ton of different time zones, and

you'll notice that they're represented using UTC and an offset,

and the offset is different depending on where exactly you are in the world.

So here's a list of time zones, but let's go ahead and

see how that works using Ruby.

Now, when we instantiate a new time object,

if we're not using time.now or time.new, we can specify it as the last argument.

So by default, let me go ahead and launch IRB here.

So by default, if we did a time.new,

it's going to use the time zone wherever the computer is.

Now, since we're using Workspaces, these servers default to UTC time,

which means if we want to create a time in a different time zone,

we need to explicitly tell Ruby that.

So I'm going to create this variable called time1.

And we'll say that's equal to the new time.

It's the year 2014.

It's July 1st at 12 o'clock.

And I'm going to use the offset four hours from UTC time.

So now we have that.

We have that into account, and we can see this time is different.

It says minus 0400.

Well, let's go ahead and see how that compares to another time.

And let's put that time, same day,

but with a five-hour offset.

Now, if we look at these two times, we can see time1 is not equal to time2.

But let's change time2.

Now, we're going to change this to be 11 o'clock.

With that same offset.

Now when we do that.

It's the same time as the other object, just in a different time zone.

Now, to make matters worse when dealing with times and time zones,

as if this wasn't confusing enough, some parts of the world add or

subtract an hour if a certain time takes place in daylight savings time.

Now, Ruby luckily allows us to answer this question if we're talking to a time object

to see if it took place during daylight savings.

We can do that by saying daylight savings time, with a question mark.

And if we look in the documentation, we can see this returns true if

the time occurs during daylight savings time in its time zone.

Now, when we're working with times, we can convert any time to UTC.

And we do that by using the UTC method.

Now, this will modify the time instance, so

if we want to have an unmodified time instance, we'll convert that.

So we'll say time1, and the dup method duplicates an object.

So if we did time1 and UTC,

we can see that this changes from 12 to 16 and

UTC, rather than having an offset of some sort.

Now, if we're looking at this UTC time1 object.

We can call this UTC offset method to see how far it

is from the Universal Time Zone.

And if we took a look at time1 and called the same method,

we can see it return this 14,400 number.

And that's the number of seconds.

We could convert that to hours,

which we would be more familiar with by dividing by 60, twice.

It's important to keep time zones and

offsets in mind when working with dates and times.

There are some gems that make this a little bit easier, but for right now,

just try manipulating and changing times on your own, using a Workspace.