jelco wrote:EDIT: You can check on the current times around the globe right here.
Welcome 2009!
-
RabidZombie
- level5

- Posts: 2414
- Joined: Fri Nov 18, 2005 10:09 pm
Welcome 2009!
Bit late, sorry. Oh well. Happy 2009.
-
dunetrooper
- level4

- Posts: 832
- Joined: Thu Feb 19, 2004 7:28 pm
- Location: Middle of nowhere Wyoming.
-
dunetrooper
- level4

- Posts: 832
- Joined: Thu Feb 19, 2004 7:28 pm
- Location: Middle of nowhere Wyoming.
vanarbulax wrote:I am in awe of the amount of fail they accomplished here
Makes perfect sense if you read that from the random topic.
I wasn't here.
-
dunetrooper
- level4

- Posts: 832
- Joined: Thu Feb 19, 2004 7:28 pm
- Location: Middle of nowhere Wyoming.
jelco wrote:Uh, the problem in no way has to do with the Y2K problem (which was severly overhyped at that). In fact, it doesn't even come close - it has to do with the 'composition' of the year, not the year number. If you're going to make analogies (a la Y2K38 which also in no way is related to the Y2K problem) at least make them technically correct.
It's a problem caused by the clock, the similarity emphasised by representing the year in a form almost exclusively used to refer to the preceding bug. That's all the superficial detail one needs to draw an analogy, particularly in the context of a lighthearted, off-the-cuff joke. Indeed, the joke is in part drawn fro the fact that the analogy is a poor one; clearly the Zune has not actually 'caught up' the the year 2000, it's an inherently ridiculous proposition. It was not an especially funny joke, but condescending dissection has not helped in that regard. The point remains, you are making a fool of yourself.
Last edited by KingAl on Fri Jan 02, 2009 3:23 pm, edited 2 times in total.
You officially have no sense of humour. Please proceed to the nearest employment opportunity in the exciting field of Data Entry.jelco wrote:Uh, the problem in no way has to do with the Y2K problem (which was severly overhyped at that). In fact, it doesn't even come close - it has to do with the 'composition' of the year, not the year number. If you're going to make analogies (a la Y2K38 which also in no way is related to the Y2K problem) at least make them technically correct.
jelco wrote:...but I beg to differ with regards to me having ruined a joke.
Don't worry, there wasn't much of a joke to ruin
jelco wrote:I won't say my 'version' was funnier, but it certainly didn't seem particularly amusing to me that the analogy was a bad one, as you suggest was the intent.
The analogy is bad in both 'versions'. If the analogy to the Y2K bug is not present, then it's just an inert coining of a moniker for the issue, which is even less funny. Raising Microsoft's failings may be an end in itself, though, but... this is why joke 'correction' just isn't done
But enough drama, this is beginning to look like the Defcon forums. Albeit more... literate.
-
dunetrooper
- level4

- Posts: 832
- Joined: Thu Feb 19, 2004 7:28 pm
- Location: Middle of nowhere Wyoming.
Who is online
Users browsing this forum: No registered users and 4 guests

