torkell: (Default)
The Master Sword is a ship with which you can sail upstream and downstream through time's river... The port for that ship is in the Temple of Time...

While playing Ocarina of Time I started wondering about the time travel involved in it. For those of you who don't know, you start out as ten-year-old Link but after the first quarter of the game you travel seven years into the future. Later on, you get the ability to travel between both points in time.

The thing is, when you arrive in the future you've also physically aged seven years. So you've not so much travelled through time as slept through it. This makes some sense: when you pulled out the Master Sword, your spirit is sealed away for seven years until you're old enough to be able to weild it (young Link can barely reach to pull it out from the plinth in the first place!).

Anyway, you trundle along to Kakariko village, pick up the Hookshot, and then learn the Song of Storms. This one has always intrigued me. You learn the song from the windmill guy, who picked it up seven years ago when an Ocarina kid turned up and played a song which messed up the windmill. Ocarina kid? Well, it can't have been you, as you've never played this song before... or can it?

Potential paradoxes aside, at some point you'll head back to the Temple of Time. Here Sheik will appear and tell you that you can put the sword back in the pedastal, and by doing so you will travel back in time. This is where it gets weird. You never actually travelled forwards in time in the first place, but were just sealed away. And yet, returning the sword will not only take you back seven years, but when the blue light fades you're back in your ten-year-old body! This makes no sense by classical time travel theory, and no sense by the "sealed away" theory either.

The other puzzle, and what originally caused me to start writing this post, is *when* do you arrive? You don't return to the same point in time every time you use the sword, as things that you do as young Link don't get reverted. So the possibilities are that you return immediately (so that if someone was standing there in Past Hyrule, watching you, they'd see you grab the sword, a flash of blue light, and then you letting go of the sword), or that you travel back exactly seven years (so the watcher would see you disappear and reappear several days later)? I've never checked the in-game clock to work this one out.

You can also travel forwards in time again, though this is much more explainable: you get sealed away for seven years again. It's implied that you have no sense of what happens during these seven years - you blink, and you're a few feet taller.

Anyway, back to your younger self. After some more dungeon-crawling you end up back at the windmill again. Still no sign of that pesky Ocarina kid... but the only person in all of Past Hyrule that knows the Song of Storms is you, and so you play that song, teaching it to the windmill guy. The same windmill guy who seven years later teaches it back to you. It's a wonderful paradox, and just where did that song come from?

Just when you thought there was enough messing around with the time stream, you get the ending to the game (which I assume you all know, but stop reading now if you've somehow not finished it yet). The sages banish Ganon to the Sacred Realm, and seal him away for a long time. Future Hyrule is still a right mess: Hyrule Castle is a lava-filled crater, the town is a ruined shell, and monsters are roaming the land. So Zelda uses the Ocarina of Time to return you for the last time to Past Hyrule, though again I'm not sure when you arrive. You return to the Temple of Time, and the door is still open so Ganondorf can still waltz in and try to control the Triforce... except he's sealed away in the Sacred Realm. Even though that happened in the future. How does that work?

For added speculation, what happens to Future Hyrule? Remember, we've got a seven year period where for a large chunk of it Ganondorf ruled over all. This can't just disappear... can it? I remember an old TV cartoon where they sent someone to the past to defeat some evil. When their hero returned to the future and asked if he managed to stop the enemy, no-one knew who he was talking about. Does the same happen here: the Future Hyrule that we know morph into the new Future-without-Ganon Hyrule without anyone realising?

Did it really happen?
torkell: (Default)
Yay for nostaliga.

Following a random conversation with [livejournal.com profile] pleaseremove, I decided to track down the oldest file that I created. This is not that easy, because I have to do so by checking file modification dates (as all the creation dates are pegged to no earlier than 28/12/2002, which is probably around when I started using this computer).

There's all sorts of fun things here.

A scrap of code, last modified 15/7/1998 but in reality far older.
Some Windows help files for a program I once wrote, dated 20/6/2000.
An avatar of me from BT's exhibit in the Millenium Dome, dated 3/6/2000.
The video database I put together once, dated to at least 29/11/1998, if not earlier (this is the one with the blank password that taunted me for over 7 years).
Some school work, which if I'm reading this right was created with Windows 3.1 in the year 2000.
A bunch of files to do with a program written back in the year 2000, on what was at the time the family computer (that computer is Odysseus, now sitting silent next to me).

Cranking the time machine back a few more notches reveals more hidden gems.

A copy of Neko95, last modified in September, 1997.
An old version of FastLynx, from christmas that same year.
The Continuum map editor, SSME, again from that christmas.
A mountain of levels for Jazz Jackrabbit 2, none modified before the new millenium.
Some circuits in Crocodile Clips, dating from the start of 1998.

I remember when a 486 was fast, and the family computer had OS/2 Warp installed.
I know people who are still using Windows 98. I still use Windows 2000 on my main machine.

How time flies.
torkell: (Default)
So the USA is considering using leap hours instead of leap seconds, because of a couple of glitches that happened that last few times a leap second was added. And predicitably, the slashdot crowd has heard of it. Nevermind the fact that I thought it was us Brits in control of time and stuff, or did the Americans move the Meridan while they were at it? There is a reason why 0° longitude passes through the middle of London - it's not just because we won the arguement over it.

They've also got it wrong as to who the last bunch of people to mess with a calendar were - it was us, when Parliment stole a week or so from us back in 1752 (okay, Russia and Greece didn't adopt the Georgian calendar until the 20th century, but slashdot's still wrong).

Anyway, to the guys who suggested changing to decimal time, or to a 13-month year. It's been tried before, and for one reason or anothe never stuck. I seem to remember around the time of the year 2000 some noise about changing to a different calenday, which had 13 equal months and a 'worldday' every so often for holidays. Never heard of it again, and we still have the semi-random holidays which are more fun. Nice try, though.

To the idiot who suggested changing the second: well, that's fine, as long as you don't mind changing all the other core constants, and so screwing with most of physics while you're at it. Oh, and you'll mess up bits of maths as well. Still think it's a good idea? You do? Oh, that's because you're a slashdot troll.

Kudos to the one who saw the humour and sutpidity in it all by suggesting that we "adjust the planet's rotation and orbit so we have perfect intervals." The runner-up prize goes to the one who followed this to its logical conclusion by saying that we should "just blow up the moon" because "that little bastard is just slowing us down."

And one person has managed to see through the politicians and realise the real problem:

The article talks about lots of problems that leap seconds cause with software.

The problems don't come from the complexity of the underlying problem of adding leap seconds, but rather because leap seconds are added so infrequently that the code to handle the leap seconds isn't well tested.

So the real question here (to me, at least) is this: what do the leap second problems tell us about how software is developed?

December 2025

S M T W T F S
  1 2 3 4 5 6
78910111213
14151617181920
21222324252627
28293031   

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Dec. 25th, 2025 04:45 pm
Powered by Dreamwidth Studios