137
edits
Changes
Jump to navigation
Jump to search
Line 35:
Line 35: − +
small correction -- the Unix Y2K38 problem only affects 32 bit machines; 64 bit computers do not have a 2038 issue.
The shortage of programmers trained in legacy languages like [[COBOL]] in the late 1990's provided an opportunity for companies in low-cost nations like India to offer outsourcing services to new markets. Companies found that commodity-type assignments like Y2K remediation were a good fit for offshore outsourcing under these circumstances. <ref>http://www.lib.utk.edu/news/readyfortheworld/archives/the_world_is_flat/001189.html</ref>The momentum in using offshore programming continued and accelerated after January 1, 2000 had passed.
The shortage of programmers trained in legacy languages like [[COBOL]] in the late 1990's provided an opportunity for companies in low-cost nations like India to offer outsourcing services to new markets. Companies found that commodity-type assignments like Y2K remediation were a good fit for offshore outsourcing under these circumstances. <ref>http://www.lib.utk.edu/news/readyfortheworld/archives/the_world_is_flat/001189.html</ref>The momentum in using offshore programming continued and accelerated after January 1, 2000 had passed.
A similar problem will be encountered in the year 2038, when all computers running the UNIX operating system will exceed their time storage capacity.
A similar problem will be encountered in the year 2038, when 32 bit computers running the UNIX operating system will exceed their time storage capacity. 64 bit computers will not run into a similar problem for literally billions of years.
==Notes==
==Notes==