We WrItE lIkE jAzZy KiDs In 2000s iN tHiS tHrEaD

i'm so fucking lonely

y2k comin computers cannot even comprehend

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

File: officer.jpg (15KB, 447x444px) Image search: [Google]

15KB, 447x444px

>>4981392
when people say the 80s why is it always 1980s and not 1780s or 1680s

>>4981402
soon it will be 2080s

>>4981402
coz is more resant

>>4981400
It's funny how people were saying that "Y2K was not a problem".

Yeah, because millions of man hours went in to preventing as many systems shitting themselves when those clocks hit 00.
They managed to protect a lot of old systems.

Sadly, some systems simply failed, some failed irreversibly.
Quite a few had data corruptions because the developers never thought to patch their file handling systems.

Y38k will be an even bigger problem.
This will, in the end, fundamentally shit on every old 32Bit system still in use.
If those OSes don't get patches, their unix time will fail disastrously.

>>4981402
Time to BREAK some minds! Ha ha!

Nineties.
Eighties.
Seventies.
Sixties.
Fifties.
Forties.
Thirties.
Twenties.
?!?!?!?!?!?!?!?!?!
Noughties / Oughties / Aughties.

>>4981411
omg soooo raladable xDDDDDddXDDd

File: IMG_2191.jpg (33KB, 290x481px) Image search: [Google]

33KB, 290x481px

>>4981392
le millenom girl

>>4981392
yeah this was totally me from 2000-2010