{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihp3eahjy3l2rbjyhr4iy3fkwwpkokc2bdm3gos75yyn7yr7tlmka",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mls5uqgqa5v2"
  },
  "path": "/viewtopic.php?t=33412&p=273986#p273986",
  "publishedAt": "2026-05-14T04:58:13.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "Rob's backports",
    "available apps",
    "available"
  ],
  "textContent": "> The biggest downside is it means anyone targeting GTK4 would likely have to target a specific desktop that uses it, since they'll likely be using libadwaita (GNOME), libgranite (ElementaryOS), libclassic (probably future MATE/Cinnamon), and whichever one you compile against... that's what your application looks like.\n\nWell I'm still unclear on this one but if it's as you say then it would definitely lead to a huge fragmentation of the Linux community, and certain developers might simply give up rather than build X flavors of their app - one for each possible desktop.\n\nIn my mind I still hope that we just slightly misunderstand the concept, and that it's possible for an application built against a raw GTK4 - as you say - to simply \"connect\" to the GTK4 version on the target machine, embracing the style used to build _that_ particular copy of the GTK4 toolkit for the respective desktop. That would definitely make sense for a smart design. But maybe I'm giving them GTK team too much credit...\n\nI'm of half mind to try installing GTK4 here from **Rob's backports** and perform some test with the **available apps**. But I'm a little afraid not to bork this system now when it's so close to [my view of] perfection. Qt6 was already a gamble, and I passed - for now - on upgrading Qt5 from 5.9 to 5.15 which is also **available** from Rob's backports. I'll think about it.\n\n* * *",
  "title": "Browser Development • Re: Linux Pale Moon with Qt toolkit",
  "updatedAt": "2026-05-14T04:58:13.000Z"
}