the process by which a web link becomes broken or irrelevant as time goes on
The site was plagued with link rot.
"Windows Rot" is the name someone gave the process by which a Windows machine becomes progressively slower the longer you use it and the more software you install on it.
I think I'll have to reinstall XP since the Windows Rot has slowed it down so badly...
A tounge in cheek explanation from programmers as to why an old program no longer works, even if it hasn't been touched in years.
Also applys to the decay of physical storage mediums.
Steve "I don't understand, it always used to work fine"
Sally "Must be bit rot"
The wincentile was invented by Microsoft in the early 90s, but is now found in just about every progeny of computer software. It is a percentile point which is bigger than the other 99, specifically one that takes a long time when a computer program is displaying its progress. Why these percentiles take longer than the other percentiles has always been a big mystery to end-users.
Usually a wincentile is the last percentile, just to cause the end-user additional stress and anguish, however wincentiles have been reported to occur earlier than that, especially in the Windows 95 installation process, where it is reported that several wincentiles even coexist in the same batch of 100.
Steven thought he would make it online in time to email his work in by the deadline, but that last wincentile took forever.
v., win·rot·ted, win·rot·ting.
1. The inevitable creeping, pernicious degradation of the integrity of Windows systems to the point where they run slowly, behave erratically, or stop working altogether.
1. To cause Windows to decompose or decay. “Adobe Reader winrotted my fresh install”.
1. The process of Windows rotting or the condition of being rotten: “The winrot spread quickly, rendering the system slow and unstable”.
2. Any of several Windows programs characterized by the breakdown of stability, speed or security. “Don't install Norton. It is absolute winrot”.
My nephew only used my computer for 10 minutes, but once he was done the winrot was so bad I had to reinstall Windows.
Computer code that starts out small, and through extensions gains a few "bad practice" changes. Over the years, extensions mirroring the bad practice start adding up, until physical symptoms begin to appear. The system may become slow and unresponsive but it still work, for example, so it continues to grow uncontrollably.
Once this happens, there are no good options. You are forced to choose between the software development equivalents of chemotherapy or radical surgery.
Like other forms of cancer, early detection and treatment is the best option.
16000 lines of code full of elseif statements that takes far too long to load and display a single invoice is a fine example of Code Cancer.
The story is called "Immutable Invoices" on "TheDailyWTF"
A piece of software that will never ever in a million years be completed. Use as-is, pick up up again, rebuild from scratch and leave it to rot for another five years.
Lets work on ResConnect and not get anything done.