I was more commenting in the laziness of people. -sc
> -----Original Message----- > From: Ben Scott [mailto:mailvor...@gmail.com] > Sent: Friday, October 01, 2010 2:01 PM > To: NT System Admin Issues > Subject: Re: The end of the BIOS is nigh... > > On Fri, Oct 1, 2010 at 12:10 PM, Steven M. Caesare <scaes...@caesare.com> > wrote: > >> It's interesting to note that Y2K bugs keep happening, even in > >> entirely new code. It's amazing how many programmers just don't > >> expect users to enter a two-digit year, or assume tm.tm_year is the > >> current year not -1900, or whatever. I've saw years like "109" show > >> up on Verizon's website as recently as last year. > > > > Everybody programming now will be dead in 3000... why should they > > bother? > > Point was, Y2K problems don't show up only around the turn of the century. > > And 2100 will actually be the next time, not 3000. There's a good chance > some people reading this list will be alive for that. > > -- Ben > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ > <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: http://lyris.sunbelt- > software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
