{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifs2xqno43qqf36ufyusjit7xa6llpewbfwyfvgn5zuiofq32vsra",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3moiahvwb7wr2"
  },
  "path": "/viewtopic.php?t=33534&p=275700#p275700",
  "publishedAt": "2026-06-17T00:14:34.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> Not planning on dropping older GTK support if this gets merged are we? I don't plan to ever release a GTK4 version of Basilisk.\n>\n> Cool use of AI though, glad it's spitting out usable code for you. Some of the more difficult parts of the QT6 port was AI-based too, although a lot of it was code I had worked on myself.\n\nI don't think the timing of dropping older GTK support has to do with when GTK4 is added. I actually nearly stopped working on this when you told me you were working on Qt6 (I kind of had a feeling Qt6 might work better once you told me it was on the table or you thought it was feasible), but then started it back up when that whole incident happened between you and Drugwash. I figured it would be easier to continue with what I already had than to pick up where you left off, if it came down to it and you'd lost interest.\n\nNow it seems like we have multiple options (which is good honestly). I think at some point we could wind up focusing on releasing builds using newer toolkits than GTK2 (maybe in say, 2030, who knows), but I don't think we'd have an incentive to remove the code.\n\n* * *",
  "title": "Platform Development • Re: Apparently Codex can port Pale Moon to GTK4...",
  "updatedAt": "2026-06-17T00:14:34.000Z"
}