The Arc CMS was supposed to be a key to The Washington Post’s future. It became a problem instead. #journalism
New at Media Nation: https://dankennedy.net/2024/09/25/arc-was-supposed-to-be-a-key-to-the-washington-posts-future-it-became-a-problem-instead/
#MediaIndustry
@[email protected] The website seems to demand massive HTTP references to both WaPo and third party sites - so loading it very much depends on a large number of simultaneous TCP connections, something that is not allowed by the old Chromebook.
Just now I loaded the WaPo website on a vastly more powerful Macbook that can handle gobs of simultaneous TCP connections and it still took the WaPo website layout perhaps ten seconds to fully settle down. I just turned on the browser developer tool to show the network connections and watched the display scroll connection attempts - so many that it looked like the waterfall display in a Matrix movie.
I’ve seen the WaPo website stop cold when some 3rd party trackers (or DNS lookups) become slow or non-responsive.
(On this Macbook I short-circuit everything to Google’s trackers, which greatly speeds up nearly every website, I can see that it is greatly speeding the WaPo load time as well.)