{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreif52kzewy4z6whaohoascrr2d2k6pcd4xizovn5fzpzj55fgvpbb4",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mkhcx4qrq4z2"
  },
  "path": "/viewtopic.php?t=33381&p=272831#p272831",
  "publishedAt": "2026-04-27T04:47:48.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> But on Linux... it feels like we're becoming something else. Just a worse Firefox that can't keep up with modern standards, and which just barely runs with no NPAPI and ugly themes. That's... not a good place to be, you get what I mean?\n\nAnd just to clarify - Pale Moon has tremendous advantages on GNU/Linux desktops, including substantial advantages in resource usage and the ability to control resource usage. Also, recall that on many distros you obtain a program like Pale Moon by building it through use of a \"recipe\" or a \"port\" or a PKGBUILD, or you just manually build it because you have some optimizations you are building into it. When you have to build a browser, you REALLY want to be building Pale Moon or Basilisk, and not spending hours upon hours trying to build a chromium-based or Firefox-based browser only to have the build process crash. I can build Pale Moon on my current system in about 10 minutes, with reliable and workable results, which is just remarkable.\n\n* * *",
  "title": "Platform Development • Re: Future of GTK2 and Pale Moon",
  "updatedAt": "2026-04-27T04:47:48.000Z"
}