|
Cnet blocked by Sidki's filters
|
|
Nov. 10, 2008, 06:33 PM
Post: #15
|
|||
|
|||
|
RE: Cnet blocked by Sidki's filters
Mele;
To put paid to the account (to answer your original question), the reason a given filter might not work is simply that when it was written, it did work, but since that time, the page code has changed. For whatever reason (and believe me, some page authors do know about The Proxomitron, and do write code that attempts to foil it), the code monkeys are constantly making unneeded and unwanted modifications to perfectly good working code. It's called "job assurance", or something like that. But it's really just acting like the first three letters of that word. ![]() Way back when, in the days of 40Meg hard drives and Extended/Expanded memory above 640KBytes, we called such idiocy "feeping creaturism". Later it was called 'code bloat', but now it's just accepted as common practice, and no one sweats the cost of memory (virtual or real), so they don't carp about it. Bah! Why, when I was a young whippershapper, I used to assemble my own code, right on my very own Altair 8080... uphill.... both ways! ![]() Kids these days! ![]() Oddysey I'm no longer in the rat race - the rats won't have me! |
|||
|
« Next Oldest | Next Newest »
|

Search
Member List
Calendar
Help



It's called "job assurance", or something like that.
But it's really just acting like the first three letters of that word. 




![[-]](images/ONi/collapse.gif)