3 ms·
> the change would have involved fixing hundreds of thousands of pages Even if these pages are static files (although any site opetating at that scale should h
by CivBase 7y ago
> the change would have involved fixing hundreds of thousands of pages
Even if these pages are static files (although any site opetating at that scale should have some kind of page-generation system), this still sounds like it could be resolved with a simple find-replace using <insert your favorite text editor>.
EasyList is definitely in the right here. Adding an exception results in an unnecessary performance penalty and creates more complexity for the project. Both of these impacts are small, but they can't afford to accommodate for every website like that.
If they want their users to use their site, they should make it work on their user's environments. I doubt they would demand Google or Mozilla accommodate for them like that.
- eswat 7y agoSeveral years ago I worked on a monolithic website that used static files with no templating engine. The problem is they had so many contractors working on changes for specific ranges of content that there were a variety of ways that even a mundane meta tag with the same content value was written (is the tag self-closing, is the value placed before the property, are certain characters in the value encoded, etc.). Find & Replace can quickly end up becoming a bigger game of Trial & Error especially if there are no standards in place.
- jankotek 7y agoThey would have to change URL to those pages