| | In 2038 the world of computers will be completely different. And nobody will be using 32 bit computers anymore  .I would think 2048 would make a lot more sense with the whole base thing. |
|
|
|
Wow! I'm sure it will get fixed though. 2000 came and it was all good. I wasn't holed up like other ppl. I was drunk and relaxed till I threw up in the b-room. lol
The bug might be a joke though. My PC i remember handled it just fine in 2000. We didnt stock up on any food or any of that sort.
Wow, I would have never thought about this, I am glad that this came out long before it would happen. At least it will be fixed before the date occurs and save us from a lot of uneccessary trouble and annoyances. If this never got out and wasn't fixed there could have been a major disaster. I'm glad I know of this now for when im working on my programs to check this and make sure my applications will keep working.
  I just was under a lot of pressure and it so happened that by skipping to write 2 simple checks my bug triggers if a certain function of the app is called exactly on the fist day of the last month of the year...and probably a sideffect would have been the first day of the first month of the next year...well I did't had the chance to check the 2nd thing because the system crashed bigtime during the test that fist day....and to think I was off from work that day, and not even in a 200km radius. Well sh*t happens. I fixed it in exactly 15 minutes....maybe less. 
They made a big fuss about the Y2K thing so I'm betting this will be the same. If it is a problem, they will just make some kind of bug-fixing update that will correct it, and nothing will happen. If it was a big enough problem, wouldn't they have said something about this years ago?
Well I believe time is relevant and that it doesnt really matter what the day is... or the time, because You can always set your machine back correct? What a bunch of idiots to come up with some theory, it's just usally to scare you and make you buy software... like Y2k... Whatever!!! I guess the will do anything to sell software..
Did you know, that because of this problem, on Palm OS, in the calender on OS5.4 you can't get it to go past a date past 31 Dec 2037....try it
 Not that I'm planning ahead or anything....I get the feeling that if manufacturers only give you a three year warranty they aren't expecting the product to last 35 years, and also expect you to buy a new and improved version without this problem in 10 years time: though at that rate Palm OS might be replaced by Windows Pocket Vista or similar :-( (Also it isn't 2048 because the calenders on software doesn't start on the year 0: it's soemthing like 1910 instead...very weird)
I've been saying it for years. Why the hell would they make UTC time start at Jan 1 1970? We should have at least reset it back to 0 after the new millennium. Websites that store time will also have similar problems. This bug might not crash all computers around the world, but some websites that aren't prepared ahead of time may be left with huge security holes.
I really seriously and extremely doubt that we will be using the same network oriented programs that we use today. The network will probably be a whole lot faster and different by then. Maybe we will be beyond 64 bit by then.
It's a UNIX problem, so unless you're running something based on a 30 year old kernel, you should be fine. This means Linux, The Windows NT series, and *BSDs such as OpenBSD and OS X shouldn't have these problems. The only people vulnerable are those using SCO operating systems, possibly IBM, HP and Sun operating systems as well. I wouldn't be too concerned about such old technologies being used in 2038 with emulation of these applications on BSD systems if there is no possibility for port. But really, what is a flip of a date going to do? Say you wrote files 50 years ago? Cron jobs wouldn't be affected greatly. There might be a slight problem with reminders, though.
|
|
 The Year 2038 Bug |