{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiepd2fqmtgl4mfjcnpkajow7w2qxlpj23co6i5wtwehqoo2g7twqe",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mmmm7kyckvu2"
  },
  "path": "/viewtopic.php?t=33412&p=274615#p274615",
  "publishedAt": "2026-05-24T17:31:06.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> I’m going to keep working on it slowly, but Linux/*nix improvements are going to be bumped much lower in my priority list going forward if people are going to constantly complain along the way.\n>\n> One thing I’ve come to appreciate after switching to MacOS on my laptop is that you only have one target. One toolkit. One OS configuration. Same with Windows. On Linux/BSD/etc you have a ton of toolkits, daemons, system libraries and integrations, etc that all do the same thing and you have to pick one which pisses off everyone who prefers one of the other options.\n\nGlad to hear that, you worked hard on Qt support already and it seems like a waste to throw it away.  I'd be willing to help test it and maybe even contribute some code, but I can't do it alone because I don't daily drive Linux.\n\nCompletely agree with you there, it's part of why I just never came around to daily driving Linux even though I thought it was fun to play with. The trick I've learned is to just move forward with what I think is useful and not listen too much to user input. Don't get me wrong, I might listen to user input on a variety of options I think make sense, and then go with the most popular of them, and then implement that option in my way even if it's not their taste. Then just expect backlash. I mean, if we only did things all the users were happy with, we would never get anything done. The fact is, anything that gets done does mean angering some users while making others happy.\n\n\n> Apologies for my outburst and language earlier. I was speaking out of anger. Things like this are a massive reason as to why I decided to do that eUXP fork (I have no involvement with that project anymore for clarification).\n\nIt's okay, I understand the general community can be a bit much. Maybe more of these discussions about moving things forward should take place on the Gitea server rather than on the open forum... so that way the discussion mostly takes place among people who actually have the skills to contribute, or want to talk about build issues or regressions that are actionable. Just saying, it's an option...\n\nAnd while I've never created my own fork of UXP (at least not since my first encounter with the project where I thought I would have to do that to add SunOS support), what I have done before is actually keep my changes under wraps until the thing I want to do is mostly done. Because I worry if they see it before it's 99% done, they'll jump to conclusions, speculate, argue about direction, lead things off course, etc. Whereas if they see it in nearly complete form, they'll be more likely to suggest minor tweaks and improvements rather than push for something to be radically different. The difference is I just keep it on my own computer and move my changes around between machines with a git repo on a USB drive when I don't want people to either get their hopes up if I fail, or else try to be a backseat driver before I get very far in the process.\n\nAnyway, I guess we can get back on topic of the Qt port itself now. That may have been a digression, but I think it was needed.\n\n* * *",
  "title": "Browser Development • Re: Linux Pale Moon with Qt toolkit",
  "updatedAt": "2026-05-24T17:31:06.000Z"
}