Yup. It happens to me too when I talk about stuff I love :)
@matthewrease23763 жыл бұрын
I like how, with 32 bits you have about 70 years. And then you double that, to 64 bits, and suddenly increase the time span past the estimated lifespan of the universe. Numbers are great.
@michakrzyzanowski85543 жыл бұрын
it's not doube, it's raised to the power of 2
@lonestarr14902 жыл бұрын
@@michakrzyzanowski8554 He meant you double the number of bits.
@sammyspan6492 жыл бұрын
Y10K
@wil-fri2 жыл бұрын
it also depends on how much precision you want
@problemecium Жыл бұрын
only problem is that the year 292 billion and change is nowhere close to the actual estimated life span of the universe. With any luck there'll still be a thriving civilization of future people (obviously quite different from us, but our descendants nonetheless) who will have to contend with this problem just as we do today. Maybe they'll already be using higher bit widths in their computers, or more likely they'll have long since done away with Unix time. But as far as we can tell with what we know of physics today, the universe will very much still be there and not terribly different from today. The familiar galaxies will be completely changed, and most of the familiar stars will be long gone, but there will be new stars in their places (and red dwarfs like Barnard's Star or Proxima Centauri stand a decent chance of lasting that long).
@AsbjornGrandt10 жыл бұрын
32 bit computers themselves aren't really the problem, as long as the software counts the time in 64 bit. I have a 4 bit computer, which handles 64 bit numbers just fine. (HP-48)
@soundslave9 жыл бұрын
Another Y2K thing that'll be fixed before it actually becomes a problem.
@henrytoss9 жыл бұрын
soundslave I believe this too, it will be fixed before the problem arise.
@harrytsang15019 жыл бұрын
soundslave Developer should not write x86 code as main anymore, it MUST completely replace by x64 before that day
@OriginalAphala9 жыл бұрын
soundslave time_t m7
@Navhkrin9 жыл бұрын
***** No they dont, they could but they dont, because its inefficent to calculate numbers using multiple numbers. And btw, it will probably play a more dramatic role. They will probably keep it until the date comes and reset the whole value, ending an old era and starting a new one using 64bit counter. Until that one runs out too. Which wont end anytime soon
@nameguy1019 жыл бұрын
+Navhkrin This is the cringiest comment thread in history
@aadityabrahmbhatt10 жыл бұрын
Cool This means when you were showing your screen counting the second in Unix manner of 1340197909... It was Wed, 20 Jun 2012 13:11:49 GMT !!!! BUT the video was published on "Jan 29, 2013" & it worse thing that your awesome video was pushed in your Hard Disk for about 223 Days !!! WHY???? But Publishing Date Jan 29, 2013 Is amazingly the exact 1 year before I am viewing the video on "Jan 29th, 2014" !!!! HOW AMAZING :-) This is real NumberPhile ;-)
@yessopie10 жыл бұрын
Everyone seems to be making the same mistake: it doesn't make a difference whether you have a "32-bit computer" or a "64-bit computer". A 32-bit computer can deal with 64-bit numbers perfectly easily, and a 64-bit computer can deal with 32-bit numbers perfectly easily. It's just slightly more efficient to use a matching length. The point: switching to a "64-bit computer" is neither necessary nor sufficient to solve the problem.
@shambhav95342 жыл бұрын
Yep, 16 bit Unix machines back in the day also probably stored it as a 32 bit signed integer.
@sanjacobs62612 жыл бұрын
@@shambhav9534 >signed Are you sure about that?
@shambhav95342 жыл бұрын
@@sanjacobs6261 Unix & C love signed integers and HATE unsigned stuff for some reason.
@sanjacobs62612 жыл бұрын
@@shambhav9534 What do you mean by hate?
@shambhav95342 жыл бұрын
@@sanjacobs6261 Even if negative integers aren't an option, they'll still make it a signed int.
@doogleisfat11 жыл бұрын
More videos with James please Brady - this guy is great, his contribution to this channel has already been brilliant.
@charliefoxtrotthe3rd3359 жыл бұрын
The company I work for still, to this day, has this old green screen management system that runs on it's own special hardware platform that was obsolete in 1990, so we purchased all the spares we could get are hands on to keep this dinosaur running. It's called AS 400. It's a first generation IBM server. It works so well for our application and is so fast that I cannot get the old timers to upgrade to a new Oracle system or something like that. The green screen will burn holes into your eyeballs from staring at it for long periods. The actual machine is this big, clunky, noisy thing with fans blowing all around to keep it from igniting. Anyone else deal with a system like this?
@abdalazizaljurf6339 жыл бұрын
+Täking Thë High Roäd Yep, government consoles in Syria. These things are scary.
@MelindaGreen8 жыл бұрын
+Täking Thë High Roäd I've programmed on punchcards. The punching machine was a horrible monstrosity even though it seemed sort of cool at the time. Monitors were just then coming out and THAT was beyond cool.
@compu858 жыл бұрын
+Täking Thë High Roäd A client I supported had a similar RS6000 machine doing their payroll and check processing. I'd tell the CFO that every time I walked past the machine I saw a Loony Toons style cartoon bomb with the fuse sizzling.
@allanrichardson14688 жыл бұрын
+Jimmy Smith Ironically, when a system begins to reach obsolescence, it gets donated to a school, so the techs of the future train on the machines of the past.
@MelindaGreen8 жыл бұрын
Allan Richardson Until we invent time machines, all students will train on machines from the past.
@hydroxenon93648 жыл бұрын
They celebrated on September 9, 2001. Little did they know what would happen in 2 days
@lebanthen8 жыл бұрын
celebrated what
@hydroxenon93648 жыл бұрын
+Alex Lehtinen 1,000,000,000 in UNIX time. Watch the video
@Thomasynthesis8 жыл бұрын
+Alberto Sanchez ARE YOU ABLE TO READ? HE SAID 9/9 NOT 9/11
7 жыл бұрын
They're not American, so that was no big deal.
@billybassman217 жыл бұрын
+Alberto Sanchez Then you wonder why there are people that want to deport your kind in the USA.
@clickrick Жыл бұрын
"Some of your viewers were too young for the millennium bug." I was there, I was part of the crew that was desperately fixing those legacy systems. Actually, I was using Unix in the 1970s and marvelling at this beautiful new operating system, and knew even then of the shortcomings of the epoch-based times, and knew in 1999 that the millennium bug was going to be nowhere as bad as when the Unix time hit the brick wall.
@Frankoman644 ай бұрын
Exactly! I hate when people make fun of y2k. It was a real problem that people like you fixed.
@jamesthurlow4668 жыл бұрын
I saw that number and just thought, max cash stack on runescape
@hieriseli18 жыл бұрын
Omg
@scathiebaby8 жыл бұрын
WTF iz Runescape
@hieriseli18 жыл бұрын
scathiebaby what?!? A game.
@static_motion7 жыл бұрын
RuneScape taught me the maximum value of a 32 bit integer well before I knew what "32 bit integer" meant.
@wandatoress82287 жыл бұрын
Felipe Varela how?
@fmincer211 жыл бұрын
well, i realy like numberphile, but alot stuff said here is simply explained wrong. the problem is not in the hardware. the problem is that unix itself reads out the RTC (that runs with the 3V battery) and stores its information in a 32bit signed integer and uses this for all time/date informations. it has nothing todo with the hardware itself and changing to 64bit unix(most easy solution) is what makes the 64bit hardware nececary.
@RutiYT8 жыл бұрын
You recorded the video on June 20 2012 :) You however uploaded it on January 29 2013... Hmmm.....
@DanDart8 жыл бұрын
The world has already been destroyed a tonne of times, but it's in a plural zone.. soooo :p
@nolle8 жыл бұрын
nah they "published" it. If you edit even a small thing in your already uploaded video, it will display the date where you made that edit.
@HashimAziz17 жыл бұрын
Even if you edit metadata like the description?
@dylanpritchard49815 жыл бұрын
nolle Omg whoa... this is actually a huge change...
@ClySuva9 жыл бұрын
I remember this 1 000 000 000 timestamp causing lots of issues as well. Many amateur PHP/MySQL systems actually sorted timestamps alphabetically. In this case the 1bil numbers came before anything else which began with 9. I just recently saw some production system that sorted files by date by concatenating datestamp to string, alphabetically sorting them, and then removing the timestamp. :D
@locomotivetrainstation6053 Жыл бұрын
I find it weird that 10^X would cause problems
@ragamuff1n8 жыл бұрын
Just wanted to make a small nitpick - Clewett states that an 8-bit unsigned integer can hold a range of values from 0 to 256, when in fact the maximum value is 255.
@schopengaard97962 жыл бұрын
No, he says "it can count up to a maximum of 256". Which is correct. I don't hear anything about any value in his phrasing. 5 years later so I don't even know why I'm commenting =)
@PauloConstantino1672 жыл бұрын
@@schopengaard9796 No. An 8 bit unsigned number can count up to 255 only, not 256.
@sanjacobs62612 жыл бұрын
@@schopengaard9796 "256 numbers" would be correct, but not just "to 256". And he did say a maximum of 256 and a minimum of 0.
@dp0558 ай бұрын
Upto 256 means 0 to 255
@bbbl678 жыл бұрын
Now, say what you will about the limits of 32-bit numbers, but one question is why did they use signed 32-bit numbers in a counter that only goes up? That immediately reduced the range of dates by 1 bit. If they used unsigned 32-bit numbers, then that would've put off the impending doom date by another 70 years, to 6:28:16 am EST Sunday, February 7, 2106!
@JesseUnderscoreMartin8 жыл бұрын
Oh, ya know, time travel and all that... ;)
@FredrIQ8 жыл бұрын
Presumably because they wanted to have the ability to deal with dates before 1970.
@stensoft8 жыл бұрын
Becuase if you subtract 2016 from 2006 with unsigned numbers, you will get a date very far in the future instead of the correct -10 years, and back in the 1970s, they considered this easier computation to be much more important than going past 2038.
@bbbl678 жыл бұрын
You can still subtract unsigned numbers properly.
@stensoft8 жыл бұрын
bbbl67 You can but it's not as easy as with signed numbers
@ChaosTheSalamander11 жыл бұрын
um...DAD? I THINK THE COMPUTOR IS GONNA DIE!
@general_prodigy7 жыл бұрын
No prob son, i got you "another one"
@firstnamelastname29715 жыл бұрын
Soo... my new 2016 audi RS7 will not be able to be driven in 2038
@rebeccairwin90625 жыл бұрын
Computer
@screamsinrussian57734 жыл бұрын
@@rebeccairwin9062 cewmputah
@CoreFinder1009 жыл бұрын
by 2038, I can't see why people would use 32bit..
@brotalnia9 жыл бұрын
CoreFinder100 Retro PC Gaming? I have a pentium 3 pc that i play dos games on. I don't really think this date thing will be a problem tough, i'll just rewind the date in the bios settings.
@Navhkrin9 жыл бұрын
mPky1 SystemCurrenttimemillis returns long value, you just said longs are 64bits, but you also said currenttimemilis is 32bit, dafuq?
@RobinLynn3319 жыл бұрын
this thread is still going? o.o
@TheSwagGuy50007 жыл бұрын
Alquimerico
@davidolsen12227 жыл бұрын
The software was compiled with 32 bit time in software. Even on a 64 bit computer the registers are the same. The command in 32 bit x86 is the same you move 32 bits from this register to that one. You could use a different register with the full 64 bits. But, you would have to recompile the programs. But, moreover you would have to change the sourcecode to use longs rather than ints. And that actually changes things a lot of time. If a programmer called 0xFFFFFFFF to be -1 because it is, when you use an int but you converted to longs without fully bug checking everything, you could cause serious problems. And this would require everybody recompile their code anyway to switch to 64 bits. But, stopping mission critical systems to change software can introduce bugs and cost billions. It's simply a giant risk to upgrade to new software when the older software has been working great for 20 years.
@DanOfAwsome9 жыл бұрын
Computer time: June 20th 2012 Upload date: January 29 2013 holy shit, you guys take for ever to upload. And I know it takes less then 7 months to edit an 8 minute video. but then again, you could be just running this channel part time. Either way, I should be thankful you're making this content in the first place.
@MataxaWhite3 жыл бұрын
they waited for exactly January 29th
@michakrzyzanowski85543 жыл бұрын
when the channel dies, we still have year of videos
@Gavarillo8 жыл бұрын
I thought he was writing Pi
@hizy80938 жыл бұрын
+Gavarillo not the only one
@hieriseli18 жыл бұрын
Same
@unitedstrike-mcpelegogames10378 жыл бұрын
XD
@neppy68046 жыл бұрын
Gavarillo i can remember the first 8 :)
@randomdude91355 жыл бұрын
@@neppy6804 3.141592
@PrimusProductions10 жыл бұрын
Will you do a video on whether 2001 should be the millennium or 2000 and problems with the Gregorian Calendar of not having a year zero?
@arrowed_sparrow15065 жыл бұрын
Well, it's 2019. And I recently fixed a McDonald's register "system"..... It was running WINDOWS 98!! Why? Because it just works.
@pabloski10k3 жыл бұрын
You made me remember something. When Windows abandoned its support for the XP and left it vulnerable to viruses, it was discovered that almost 90% of ATMs in the World were still running on a XP computer. Why? Because it just works.
@Anti-proton10 жыл бұрын
Just change the data width, recompile the kernel, and keep trucking :P Of course, another idea is keeping your times in your software as offsets from a base-time. I usually use an unsigned long integer and just count milliseconds.
@davecrupel28176 жыл бұрын
antiprotons or use a 64bit number
@hamstermo5 жыл бұрын
For anyone who's wondering, the video was filmed on 20th June 2012 at 1pm (UTC)
@SirJavaGaming9 жыл бұрын
The video has been recorded on 20.06.2012 1:12pm (UTC). Why was it uploaded half a year later? :)
@sdmcelroy9 жыл бұрын
You should do a video on Plan 9 from Bell Labs. It's a fascinating story and brings massive advantages by simplifying our interactions with computers.
@epicmarioplush23129 жыл бұрын
so my 64-bit windows 7 computer will be fine?
@isaackarjala79169 жыл бұрын
Probably, but not because it had a 64 bit kernel, since the bitage of the kernel and the timestamp are unrelated.
@chsxtian9 жыл бұрын
epicmario plush Windows doesn't use a unix timestamp in the first place, so you're fine.
@lemur28709 жыл бұрын
epicmario plush You'll probably have a new computer by then anyway. It's more than two decades away yet.
@Navhkrin9 жыл бұрын
epicmario plush No, the value is 32bit, even if your computer is 64bit.
@isaackarjala79169 жыл бұрын
Michael Longhurst just like with y2k, the issue isn't end-user systems, it's servers.
@xXx-un3ie8 жыл бұрын
4:10 Im sure he meant a min of 0 and a max of 255, not 256. He got the other signed margin right though
@dstarfire425 жыл бұрын
Glad I'm not the only one who noticed that. The maximum value you can represent with any number of binary digits (assuming it's at least 1) is ALWAYS an odd number. Also, studying computer subnetting really drilled the binary maximums into my memory.
@bleh189811 жыл бұрын
It's actually going to be 1901, since the integer in which the number is stored is signed (it holds a plus/minus sign). When the byte "Fills up" the only bit left to flip is the sign bit, turning the number into the negative. So 2147483647 turns into -2147483648.
@BunnyRaptor8 жыл бұрын
You filmed this June 20th 2012? Wow, it really does take you a while to upload these videos. A lot of work, perhaps.
@audiblemagician67518 жыл бұрын
+Чики Брики They probably thought they uploaded it and then on Jan. 29 they realized it never got uploaded and they uploaded it
@gunterchain8 жыл бұрын
Shut up bandit
@wajideu50059 жыл бұрын
I think it's kind of a dumb idea to make assumptions about integer sizes on a machine. For C, the best practice imo is to use a big number library like gmp. If the integer size is supported by the machine, you can override the functions with preprocessor macros that do the math normally. This way, there's no performance hit when the integer size is supported and you can easily increase the size of the integer whenever you need to. The only limit on numbers then is how much ram you have.
@peterpickaxe0911 жыл бұрын
Brady! I love your work and what you do, a few of your videos seem to be computer science based, just wondering have you ever thought of making videos on that subject? thanks!
@yatox89 жыл бұрын
Well at least we have 23 Years to get our systems up to 64-bit computing. This is just a great show to tell that if you live in the past, you will fall. Times change, so should our perception of humanities future; Resistance is futile!... ALL HAIL HYPNOTOAD!!
@ludvighoelstad3267 жыл бұрын
two seconds in and I love this guy allready
@dhy81111 жыл бұрын
I love his laugh at the end... Like a nervous way to deal with the morbidity of what he just said
@Shiri_Yam2 жыл бұрын
I probably won't live up to this, but I kinda want to go back to this video in 2038. I want to watch this video again in 2038 and compare it to what actually happens lol
@JesseUnderscoreMartin8 жыл бұрын
Didn't something like this happen with that Korean dance video that went viral? Wasn't youtube storing the amount of views as a 32 bit int?
@tanan81168 жыл бұрын
Yes.
@BaxzXD8 жыл бұрын
yes
@saltyasian44627 жыл бұрын
It was confirmed as a joke by Google as the integer was always 64 bit.
@user-zz6fk8bc8u7 жыл бұрын
Z source?
@shehannanayakkara41627 жыл бұрын
Z Nah what happened was that they changed it to 64-bit several months before when they saw Gangnam style approaching 2 bill views. So yes, the view counter 'breaking' was a joke but it wasnt always 64-bit.
@Wyzwon10 жыл бұрын
He's wrong about the heat death statement. Red dwarfs live for a trillion years. The universe wont be particularly active then but stars forming now will be here four times as long. luckily, they don't run on Unix time :P
@GameShowFan90015 жыл бұрын
The heat death is supposedly going to happen in something like 10^120 (or so) years from now, way more than the 2 billion figure that was provided in the video
@memk3 жыл бұрын
It's 2021. We are one more year closer to the end of time.
@GregInHouston2 Жыл бұрын
I thought about this problem back in the 90s when I was designing a software package. The problem was that my compiler didn't handle 64 bit integers. I also stored hourly data in a file. Each record had a timestamp. A 64 bit timestamp increased the file size considerably. At the time, we were using floppies and size mattered. I never settled on how I was going to handle it but decided that I stored a 32 bit date offset in the configuration section of the file. But the problem was that I didn't think that would work well in 2038 when that value would cross from 0 to 1. The lower 32 bits would be zero at the start of the data but would overflow during the middle of the collection period. Such things were considered too inconsequential at the time and I was terminated.
@Autoskip10 жыл бұрын
You've got me curious, I've now set my iPod to as far ahead as possible - midnight 1st of January 2038. Now to wait 19 day, 3 hours and 14 minutes...
@br45entei9 жыл бұрын
I understand why we use the current time system, but I really don't see why we couldn't just make it so that the day, month, and year are saved independently as well as the normal 00:00:00 - 24:00:00 time value. One number to represent all of that seems a little silly to me really.
@nikolaibelinski5937 жыл бұрын
cus if they are working together we can develop time travel and the computers will be the ones to send us there
@0zfer9 жыл бұрын
06/20/2012 @ 1:12pm (UTC)
@joemuis239 жыл бұрын
SirJavaGaming i did :P
@aislingoda60269 жыл бұрын
0zfer I was so confused when I saw this. Being an Australian, seeing the six first made me think "you're wrong, it's the twentieth of June!" I then realised that the twentieth isn't a month, and I figured out from there that you had the same result as me.
@EanaHufwe7 жыл бұрын
That's why some people write it as 20 JUN 2012, like me. I do that all the time.
@HashimAziz17 жыл бұрын
Or just adopt the British (i.e. superior) system: DD/MM/YY.
@fluent_styles67207 жыл бұрын
Hashim Aziz yeah
@ArcherInRook7 жыл бұрын
Just discovered 32 bits time will end on your exact birthday is amazing
@thirdislandmile10 жыл бұрын
Mmm, I could listen to (and watch) James explain this kind of stuff all night.
@PianoVidz11 жыл бұрын
2,147,483,647 what is up with that number? it shows up everywhere when dealing with maximum numbers in computers???
@try6767youtubacc7 жыл бұрын
It equals ((2^32)/2)-1 In other words, it's the top (positive) value of a 32-bit variable, which is comprised out of 32 binary bits. So the range of numbers that can be represented with it (as explained in the video for 8 bits), is either 0 to 4,294,967,296, or -2,147,483,648 to 2,147,483,647. In order for the time-calculation mechanism of computers to be able to handle past dates the latter option was chosen, so if you start from 1/1/1970 as your zero-time (aka the Unix Epoch) and count the time in seconds it equals around 68 years, in either direction.
@shobithchadagapandeshwar97647 жыл бұрын
A 32-bit computer can represent 2^32= 4,294,967,296 numbers essentially from -2,147,483,648 to 2,147,483,647.
@MarkGamed7 жыл бұрын
(2^(32-1))-1
@SuperFranzs9 жыл бұрын
I'm just screaming in side me at the beginning: LINUX!
@ieattapes9 жыл бұрын
NEEEEEERRRRRRRDDDD!!!
@SuperFranzs9 жыл бұрын
ieattapes have you ever actually used ubuntu?
@nameguy1019 жыл бұрын
+Kim André Moen Bjørkede (Super Franzs) Linux uses Unix time as well
@SuperFranzs9 жыл бұрын
+Nameguy That's why I was screaming it at the beginning.
@Newbyte6 жыл бұрын
Hardly any home users use Linux though, compared to Mac or especially Windows.
@davidthomas497810 жыл бұрын
Could they not just set the counter back to -2 147 483 648 when each computer starts and set it to the current time? Surely the value of a counter can be set to a different starting point.
@TechnoMinarchist9 жыл бұрын
+David Thomas Not without an IBM 5100 to debug the legacy programs for you.
@amigojapan9 жыл бұрын
Jacen Solo Psy el Conrgoo!
@clausnymann5527 Жыл бұрын
At the peak of my nerdom, I attended UNIX's 1 billion-second birthday, when it was celebrated in Copenhagen, Denmark. Thanks DKUUG, SSLUG and BSD-DK for that event! 🙂
@tomdonaldson6988 жыл бұрын
I didn't realise this was a numberphile video!
@ForkGenesis3 жыл бұрын
~16 years left, guys
@LiborTinka9 жыл бұрын
Yep, that's why I store Unix time in LONG everywhere :-)
@zeddash9 жыл бұрын
You should store it as ulong, because you can.
@AB-om2qp9 жыл бұрын
+FinnShack world war 1 and 2, Women getting the right to vote. That's only s few ;)
@nameguy1019 жыл бұрын
+Andrex Plays what
@AB-om2qp9 жыл бұрын
He said nothing important happened be4 1970
@AB-om2qp9 жыл бұрын
***** ohhh I feel like such an idiot now
@YnseSchaap9 жыл бұрын
Wasn't there supposed to crash a comet onto earth in 2038 ?
@theq46029 жыл бұрын
We have nukes. And rockets, and a extensive global program devoted to finding and tracking asteroids and comets that could hit the earth. As long as WWIII doesn't disrupt that program we should be fine.
@fmlAllthetime9 жыл бұрын
+David Vermillion Blowing up a massive asteroid would be one of the worst things you could do :I
@theq46029 жыл бұрын
fmlAllthetime Other than hitting satellites what could it hurt?
@fmlAllthetime9 жыл бұрын
David Vermillion Really think about what you're saying for a second.
@ElPastalero4 жыл бұрын
Fun Fact: 2,147,483,647 is 2 off from being one half of a previously featured number on Numberphile - 4,294,967,296 (2,147,483,647 x 2 is actually 4,294,967,294, not 4,294,967,296)
@user-uc9fm8bn9o10 жыл бұрын
They where recording this video on Wed, 20 Jun 2012 at 13:11:51 GMT
@PikarinePlays9 жыл бұрын
20th June 2012 eh?
@macwas59009 жыл бұрын
"The end of Gangnam Style views" ammirite?
@saatvikjain39 жыл бұрын
it was based on the same thing.
@deletevil7 жыл бұрын
exactly, they stored view count variable as signed integer despite the fact that view count can not be a negative integer ever. A Noob's mistake.
@jakewhite99677 жыл бұрын
Mac Was always
@soyoltoi7 жыл бұрын
Sumit Singh Google programmers aren't noobs. They had a reason for that. I believe you can find it on their style guide.
@areebjamaliam6 жыл бұрын
It was a joke
@JonnyInfinite8 жыл бұрын
"Planes will fall from the sky, Nuclear reactors will meltdown..." remember all that millennium bug bollocks? Absolutely sod all happened.
@brianmiller10778 жыл бұрын
+JonnyInfinite because we put a lot of time into fixing that issue to keep it from happening.
@JonnyInfinite8 жыл бұрын
+Brian Miller yeah right. Pull the other one
@JonnyInfinite8 жыл бұрын
+Joshua Bruton where is your proof?
@JonnyInfinite8 жыл бұрын
+Nubbitude 'Jack' sounds like a right scam
@JonnyInfinite8 жыл бұрын
+Philip Rambaran I think it was used to crowbar money for something that wasn't much of a problem.
@conorreedR2C11 жыл бұрын
I just realized that this video was uploaded on my birthday....... All the best.......
@ZiMilkMan11 жыл бұрын
He said in the video "Most of you at home probably have either Windows or Mac, and they have a little counter buried in that system that's been ticking away every second, that's been ticking away since January 1st, 1970" he was referring to the Unix counter
@fhtem782810 жыл бұрын
Oh god the end of time itself is on my birth day!
@SimLPs9 жыл бұрын
Isn't that the really famous tetris player?
@cjomero53428 жыл бұрын
2038 will be the end of all 32-bit things, like today's technology.
@LeBourineur8 жыл бұрын
+Cj Omero still working on 16bit technology
@maedafeelscoke56848 жыл бұрын
the end of 32-bit is at Mon Jan 18 22:14:08 2038 but i want 128-bit cpu before the year 292271025014 xD the year 292271025014 = the end of 64-bit
@boomerboxer35748 жыл бұрын
Jowat Defuc 128 bit is probably 387498723847284782374874827987348728374827875847892798789579021772347832787179287348718975764817877897582747852784758287945975847857002786786927486758678275878476827578765878278768728776767364827658782475409672904068927876376455038453048-345e5978-396-54-539-4593-495-95e-045prod;fkvghhjcxbvbuvru34gv64
@iambalkan8 жыл бұрын
+BoomerBoxerReal damn 🤖
@boomerboxer35748 жыл бұрын
iambalkan i actually got a random piece of pi and just started mashing my keyboard
@thatguy_apu7 жыл бұрын
Am i the only one who noticed that he was wrong about the 8-bit thing ? 8 bits can only be 255, a range of 2^0 to 2^7. 8 bits only don't allow 256, because that would be 2^8, which would require a ninth bit. The maximum single-bit number that you can display with 8 bits is 128, and the maximum total 8-bit number is 255.
@GoldTrousers11 жыл бұрын
If the would have used an unsigned integer for the GP count like they should have, since they don't need to worry about negative values in item counts, the max 'stack' would be max unsigned 32-bit which is 4,294,967,295. Anyways, the maximum number of anything in any 32-bit game (Score, Money, XP, Position Co-ordinates, etc.) is one of those two max integers depending on the signage.
@samiraperi4678 жыл бұрын
"Time will "end" for 32-bit computers on 19 January, 2038." Yeah no. Only if they use 32-bit time_t. I have a 32-bit computer that runs out of time some time in the 22nd century, because AmigaOS uses a different epoch and IIRC an unsigned 32-bit int.
@tresbrown6842 жыл бұрын
What date does it run out at?
@charlesisbozo9 жыл бұрын
At least then people will finally move off XP...
@markdudley757510 жыл бұрын
We'll have 128 bit computers or even higher by 2038
@romanivanovich67177 жыл бұрын
nope
@Sqaaakoi7 жыл бұрын
Mark Dudley ...
@gooz16917 жыл бұрын
UNIX time with 64 bit will run out after the Sun inhales Earth so no point really
@ultru35257 жыл бұрын
+Pan kurczak You're already using numbers way bigger than 128 bit; when it comes to cryptography, the number of atoms in the universe won't cut it, RSA keys are up to 1154 orders of magnitude larger.
@gooz16917 жыл бұрын
Why do so many people get this wrong? 128bit is not twice as big as 64bit. 65bit is twice as big.
@daedra4011 жыл бұрын
James makes any video an instant favourite :P
@Christopher.E.Souter11 жыл бұрын
There is a tiny rechargeable battery inside inside the machine, which powers the CMOS clock, which is the part that does all the counting. That battery gets charged every time you run the computer, even when you're only running it on battery power.
@patsonical7 жыл бұрын
Guys, Unix Timestamp = 1.5 billion 14-07-2017 at 02:40:00 (am) Mark your calendars!
@sebastianespejoloyaga76037 жыл бұрын
Nothing happened...
@tieb14077 жыл бұрын
That's my birthday :D
@jalualex6 жыл бұрын
nothing happened
@tanan81168 жыл бұрын
I think in 2028 32-bit is going to be completly usless because of the exponential amount of RAM increasing in average home computers.
@chestersnapdragonmcphistic57910 жыл бұрын
Oh noes! Teh next Y2K! Lets all go buy bread and milk and hide in our shelters!
@TesterAnimal13 жыл бұрын
You one of these denialist nutters?
@bruceeinhorn808211 жыл бұрын
Though you're correct about the Mac OS being a variant of UNIX, (NetBSD and FreeBSD) to be exact, you're wrong about the X. That does indeed stand for 10, in case you're not familiar with Roman numerals.
@AJenbo11 жыл бұрын
Windows actually doesn't use Unix time but a bunch of different mechanisms. It's file system (NTFS) uses 64bit from year 1601 divided by 100. But the counter for the running time can only count as much as 50th day since last boot. There are lots more of these issues to look out for if you are developing for Windows.
@its_noli65438 жыл бұрын
Guys dont freak thats not the end of time it will end in 10 million years until the sun will centerpiece with earth and rip it into the suns inner peice and bam destroyed
@DanDart8 жыл бұрын
That's not the end of time either, just the Earth.. hopefully whatever becomes of humans will have escaped by then... also it's more like 10,000 million years
@demuriffic71528 жыл бұрын
Not only the Earth, but could be the whole solar system
@Fetidaf8 жыл бұрын
Kathie Dart I think it's even more than that 😂
@red_isopat8 жыл бұрын
sun has nothing to do with time
@demuriffic71528 жыл бұрын
Gentel Noober Everything happens with time. PAST PRESENT FUTURE
@Andranadu8 жыл бұрын
64 bit time would end in the year 1169108100477
@zoltanpataki13078 жыл бұрын
what about a 1024bit pc/phone??
@petaflopminecraftmore23388 жыл бұрын
+zoltán ifj.pataki That would not be needed. We needn't ever create a 128-bit machine, let alone 1024 bit.
@eLJaybud8 жыл бұрын
Not needed unless some form of mathematics has a specific requirement.
@4345ghee5 жыл бұрын
Convert.ToInt64(unixTime); I’ll be collecting my royalty checks now kthxbye
@pfever9 жыл бұрын
so you filmed this on Wed, 20 Jun 2012 13:12:11 GMT? but uploaded until 29 Jan 2013? 0.o
@lambsum8 жыл бұрын
Fun story: A few weeks back I was playing on my iPod on a trip when it ran out of battery. When we got to the place I charged it but since it couldn't connect to wifi (we didn't have any at the place). It couldn't find out the time from that and so it just automatically went to 1970. I took some photos which I thought were disappearing and being deleted for some reason until I realised they had all gone to the top of my camera roll.
@lonestarr14902 жыл бұрын
You got lucky that you didn't got your password wrong three times, for it would have make you wait for 46 years until you could try again.
@rchaffer11 ай бұрын
Happy new Unix Epoch!
@AlarmClock6511 жыл бұрын
I think you're right. I got 06/20/2012 too at approximately 1:12 UTC, which is 6:12 AM in UTC-7 and 6:12 PM in UTC+5.
@Mathhead200011 жыл бұрын
Actually, 1970 is 0 as a Unix Timestamp, but when it rolls over, it will be -2^31 not 0 (because it is a signed 32 bit integer.) So it will be about 1970 - (2038 - 1970) = 1902
@jazzpi11 жыл бұрын
Depends on the lang you're talking about. For Java e.g. it's sizeof(int) = 32; sizeof(long) = 64.
@rich105141411 жыл бұрын
My mother worked for Trades publishing, which published the Y2K magazine. None of us believed the hype, but it was her job. Well, the electric company had scheduled an electrical maintenance at 11:59pm friday, which happened to be 1 minute before new years. Talk about freaking out. It freaked so many out, it made the news and the electric company had to make a public apology.
@DaveScottAggie9 жыл бұрын
It is interesting to learn how these situations come about.
@StereoBucket11 жыл бұрын
By the way. It's the number and not the OS. Sure with 64 bit OS you can get more stuff but the whole number that is used for a clock is a signed 32 bit integer. You can make 128 or 256 bit PC but that number is still 32 bit signed integer. You have to change it manually to 64 bit integer. The 64 bit installation of windows does not do that. Neither do other OSes with 64 bits.
@PanicProvisions11 жыл бұрын
I was looking exactly for this.
@jack91x11 жыл бұрын
It's "unix-like". It is a direct evolution of Unix cia GNU, BSD, and MINIX. Whereas Unix is a copyrighted program, Linux is its open-source "clone" that was created so everyone would have access to similar tools.
@tugno96394 жыл бұрын
We’re going back in time baby
@stephblackcat11 жыл бұрын
it's not built on it no, but the original version WAS based (as you said "like" or to simulate) on Unix. From what I remember from the Linux part of my networking class a good deal of the little invisible ways that things are done are still VERY Unix like including still using the Unix time variable.
@kikeonline9 жыл бұрын
it was film on 06/20/2012 @ 1:12pm (UTC)
@Elsid111111 жыл бұрын
Don't know much, but guessing it doesn't work like that. Unix time is basically just a giant number counting in seconds up from 00:00:00 1 January 1970. So if you change the date on your computer, you aren't increasing the number of unix seconds you have counting on some little component in there, just the date which the computer attaches to that number. Don't actually know if this is true, but what I'd guess.
@tristanbay3 жыл бұрын
Wouldn't that 3:14:07 on 1/19/2038 be slightly off, though, do to any leap seconds we may add to the time? Or do we add a second to UNIX time as well?
@thekidfromiowa2 жыл бұрын
3:14 = pi o'clock
@MatthiasVanGestel11 жыл бұрын
it's about 32 bit computers. And I think it is unix bound. Also in 32 bit systems you can fix this by using another 32 bit register (2 in total) to count the time effectively increasing the possible time.
@LUXITANE11 жыл бұрын
What about 16 august,year 2880?
@Wallamanut11 жыл бұрын
So, I'm not exactly sure if I'm right on this, but I calculated that this video was recorded somewhere around May 8th, 2012 at 3:26, which would mean that this video took them a while to upload. Has anybody else gotten anything different?
@mike20001710 жыл бұрын
This issue has nothing to do with 32bit vs 64bit architectures. It has to do with the library code. POSIX-compliant systems provide a standard set of time functions, which also happens to be the ISO C standard time functions (in the time.h header), which did not require a specific minimum size for the integer representing the time. Most OS implementations just decided to use 32bit integers for this (long before 32bit computers even existed) because it seemed "big enough" at the time. Now, most OSes have expanded to 64bit integers (whether you have a 32bit or 64bit computer)... but there are still many very old systems around that still carry an old enough OS version to have 32bit integers for time, and assuming they will still be in use in 24 years, then they'll need a long-overdue replacement.
@lister_of_smeg65456 жыл бұрын
And this isn't just limited to operating systems. You also have the problem of legacy software which was compiled using the 32-bit time_t (or which used their own implementation of UNIX time rather than the standard libraries) for which the source code is not available.
@muffinV1362 жыл бұрын
So since I'm using a 64 bit computer will it still work?
@uditrawat240411 жыл бұрын
really loved the fact about computing ,what if we manually set the time to that point ?