But does he have the time? can you really have something as unsubstantial and untouchable as time? you think you are in the present but are you? because you shall read this in the future than you are a being of future and am I a being of past? who are we to qualify ourselves based on the timeframe where our thoughts came from? not even the greatest confluence of minds should be able to solve this most effervescent but erudite topic for we are simple beings.. .okay I got bored with this shite.
It very probably is a very distressing topic. And that is from a non-programmer, who is just very glad to estimate this stuff and does not deal with it by himself.
Chaos = "Ladder" class Ladder: def user(self): print("Chaos is a Ladder") if Chaos != "Ladder": pass else: Person = input("Whotf is climbing it?:") if Person.lower() != "tom": print(":(") quit() print(f"Chaos is a Ladder and {Person} is climbing it") Item = Ladder() Item.user()
"uh, Tom, a bunch of people posted selfies on New Year's Eve and they all got their accounts banned for spamming because the antispam algorithm saw a negative time offset and went nuts"
Tom, Hank/John Green, Michael from Vsauce, etc; I’m just convinced these people are all part of some immortal council from the dawn of time who have guided humanity through dark ages.
As a dev who took up the task of maintaining their team's bonkers in-house implementation of date and time, I know that pain. An interface specification for a third-party system once contained, no joke: "Unix timestamp in local time". My colleagues never understood why this got me laughing hysterically like the Joker.
@@otesunki so when the spec authors said "local Unix timestamp", they actually meant "the Unix timestamp that, when *misinterpreted as a local time*, gives you the desired time in the local timezone". It still cracks me up, years after.
OOO MY FUCKING GOD YOU HAVE JUST TOLD EVERYONE THAT THIS DAMN VIDEO IS 1 SECOND SHORTER THAN WHAT IT REALLY IS YOU ABSOLUTE MORON YOU HAVE RUINED TIME ITSELF WITH THIS FOOLISH MISTAKE
That one second would be accumulative. Considering we have nuclear power plants whose internal mechanics are depended on doing stuff at the correct time, getting it wrong could literally mean the destruction of civilization as we know it.
Fun fact : a few terrorists in 1999 died because of timezones in Palestine. Basically the bombs were set with zionic time or something while the time and schedule they were following was something else and therefore the bombs exploded one hour before they were meant to and they all died on the way in the car
I know I'm a year late, but this has some very important implications in computers and finance where exact times are very important. There exists some atomic clocks meant to help keep this accurate, but for most everyone else they shouldn't have to interact with this problem.
@@SnoFitzroy Especially since countries didn't change calender all at once. And often not even the entirety of a country at once. And relativity. Gravity and speed dilate time enough that GPS satellites run 38 microseconds fast. That means positions would drift about 6 km per day and the time signal would be off by a second after about 72 years
@@Omar_Al_Seddik If flat earthers and creationists took their beliefs seriously, they would sound like any sane person. They are trying to remove reality and brute force creationism and the flat earth into it. But what they should be doing is implementing their beliefs into current scientific knowledge. They are just too stupid to figure out how to do something easy like that. it doesn't help than at least 70% of the "flat earthers" are just pretending, in order to wind up people who get mad at others for believing in something unscientific. Always fun to troll people like that. They've not a shred of a sense of humor...
he speaks about the people who made the spaghetti code as if they were the heroes of old that defeated a legendary beast seen only once every hundred years.
Once every 100 years is when the leap year is skipped. Except for every 400 years when it happens anyway. And it's still a day off every 5300 or so years.
It is said that a society prospers when old men plant trees they will never sit in the shade of. The modern correlary is people who write insanely complicated technical code and make it open source and those who do things like spend their time maintaining and expanding Wikipedia against the tides of internet entropy. Without the selfless service of these lunatics our modern way of life would not be possible.
I'm so glad Tom Scott doesn't exist in a time where we're moving around at high enough speeds that time dilation starts to have an impact. I'm pretty sure he'd lose his mind. Because these software libraries can't help you then, because you're literally the one who is creating new differences in time.
@@dionyzus2909 Yes your clock in the ship always looks like it's pasisng at the same rate to you, but it doesn't to people on earth or in other places. That's where the issue is. How do you easily calculate times when one person has had a literally different amount of time elapse compare to you? How do you keep track of all of this? Etc. It's the same exact issue Tom Scott is on about in the original video. When you convert between different locations the times are a mess and change all over the place, calculating the time between two different times is a mess, everything is. But at least you can just create a database of rules for time zones. You can't do that when every fast moving ship has its own time elapse differently to you. And similarly to the video, the time since the unix epoch doesn't work properly either with this. Normally at least that mostly agreees across the board, but when you start going really fast compared to other clocks, your clocks can get out of sync. One person can think X seconds has passed since the unix epoch while someone else can think it has been X - 1000 seconds since the epoch. It's going to be a mess. Tom Scott is going to lose his mind if he's still alive.
This is already a consideration for satellites. We DO live in a time where we're moving around at high enough speeds (or rather moving around different things with different proximities to Earth's gravity well) that time dilation starts to have an impact.
Unix Time: 23:59:59 Universal Co-Ordinated Time : Imma about to end this man whole career (adds leap time) Astronomical Time : Imma stop you right there! (adds random number of seconds/miliseconds according to astronomical alignment)
Becasue it was used in Inception trailer, so for many it's not "Zack Hemsey's song", but simply "Inception trailer music" sometimes even ommiting the "trailer" part and saying it's probably by Hans Zimmer...
As a programmer, I completely understand his frustration with time and timezones. Knowing how we have to handle it makes me want to shoot myself just thinking about it. Hopefully I'll never actually have to write code for it.
Funnily enough a couple of days ago I spent HOURS trying to solve an error where a client wanted a website to show a specific schedule at a specific timezone, since backend is at UTC, a conversion needed to be done from frontend (which showed UTC+2 hours), and it was a NIGHTMARE. So yeah, let's thank all the people that dealt with timezones so we don't have to.
That’s why I love people who entertain with logical facts and things such as how Tom Scott does, eventually they just lose it and start to blow thing up.
This implies that he wasn’t already “mad” (as you put it) before this video. Cause I’m pretty sure he reached that point before RU-vid, probably around the time the British government got mad at him.
Can confirm, had to work with time zones a few times now and it's more than a nightmare. This reaction is appropriate and dare I say on the more calm side
Also: Each second is a span of time. We don't really label the points when the second changes, we label the stretch of time between two of those points. So the :00 second is what's _between_ the start of a minute and the start of the next second in it.
@@monad_tcp Yeah - I have had to stop and think it through when describing unix time stamps. 0 was the second that started at midnight going into 1970, and ended when it ticked over to 00:00:01. What is still mildly confusing to me is what you do when you have different precision. Say you have a timestamp of 1 and another of 2.001 - what duration elapsed between them? The natural approach is to just subtract them and get a 1.001 sec span, but that means you're treating 1 as the point one second after midnight, instead of a numbered block of time that started at that point.
@@monad_tcp Depends on how picky the systems are about time and how physically close they are, I guess? With how Google stretches that one second over days, the offset will be smaller than the network latency to anywhere outside the same city.
When I started learning about programming I kept hearing "time is a nightmare", and I was like "yeah daylight saving time changes and converting timezones sure is a hassle". What a sweet summer child I was. Long ago.
didnt even know he ever talked about this, but I went down the exact same wikipedia rabbit hole years ago at 3am. Time, together with networking and analogue audio is one of those things that will ruin you if you look at it for too long
I work in software QA and we've had this one app go back and forth about 4 times now because every time I hand it back and the devs fix what I find, a new bug relating to dates and times appears. Currently watching a colleague enter this state of despair - it's just what time does to developers.
and there's a way to manipulate it. It's possible for the human mind to enter an extremely deep state where time slows down and compounds within itself to get you to a point where you'd possibly perceive ~300 000 years of perceived time within a single second. This is believed to be "suspended animation".
The Mayans: the world will end in 2012 (World doesn’t end in 2012) Me: what if the Mayans switched up the last 2 digits and the world ends in 2021!!!!!
