{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicv77jckkffsejrkwdn22yajpdx4avjer63hqqnaxtdaqmil22t74",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mluhp3c33j52"
  },
  "path": "/viewtopic.php?t=33437&p=274037#p274037",
  "publishedAt": "2026-05-15T03:15:26.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> …at some point you just have to blame the browser itself at times in terms of stuff like CSS and JS implementations\n\nAs Athenian has superbly explained elsewhere, CSS and JS implementations have been another arm of Google’s monopoly for many years. The fault is with Google, and with developers eager to play with the toys Google has made. If we were to suppose instead that web developers were, on the whole, happy to keep doing things the way they were done when you were born, then Google’s heterodoxies would simply be written off as a bad attempt to imitate Microsoft, bungled at the second E. As it stands, Google has mastered all three stages.\n\n* * *",
  "title": "Browser Support • Re: Why is Pale Moon so slow?",
  "updatedAt": "2026-05-15T03:15:26.000Z"
}