{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifipmw6qb3hcninff4tmqlv3iau6s777kshno47htotfppba7mcfy",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3ml7o2nlcvte2"
  },
  "path": "/viewtopic.php?t=33412&p=273591#p273591",
  "publishedAt": "2026-05-06T20:19:57.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "by 2015 had a port that could be built showing their gtk3 progress",
    "until the release of gimp 3.0 in March 2025",
    "gimp's own historical chronology",
    "https://github.com/darktable-org/darktable/issues/20433"
  ],
  "textContent": "> Well, actually... GTK2 support ended in 2020. GIMP kind of hurried to move from GTK2 to GTK3 because of that. So it's not so much that they knew where the safe path was, they just were able to do a port to GTK3 relatively quickly when they heard GTK2 wouldn't get security updates anymore.\n\nGimp started the transition process in 2012, and by 2015 had a port that could be built showing their gtk3 progress. The final gtk3 pieces weren't in place until the release of gimp 3.0 in March 2025. The long, laborious process of transitioning from gtk2 to gtk3 by gimp was well documented by tech outlets like Phoronix, and gimp's own historical chronology page notes the tremendous amount of work required to transition [the 2024 date may be referring to the 3.0 RC1 release]:\n\n> Notice the long gap between 2.10 (2018) and 3.0 (2024). That span was consumed by the enormous effort of porting GIMP from the GTK2 toolkit to GTK3 - A rewrite of virtually every widget in the interface. It was unglamorous, difficult work that yielded no new user-visible features for years, but it was necessary to modernize the codebase and restore HiDPI display support on modern hardware.\n\nNot that that's good, it actually shows evidence of what a giant pain in the butt the transitions can be, which is rightfully part of your concern. Also I am sure that you are right that their efforts got a lot more urgent after 2018, when the axe was about to fall on gtk2. Fortunately, you already have a lot of code on the gtk3 side for Pale Moon.\n\nThe Darktable photography project posted an interesting AI generated gtk3 to gtk4 migration assessment: https://github.com/darktable-org/darktable/issues/20433\nCould make for a useful comparison. Darktable is estimating 3-4 months transition time for its own codebase.\n\n* * *",
  "title": "Browser Development • Re: Linux Pale Moon with Qt toolkit",
  "updatedAt": "2026-05-06T20:19:57.000Z"
}