I have to clear up a misunderstanding. As it appears, Martin and I (who are usually regulars at the dev meetings and barely miss one) have actually missed a crucial one where he was not present while I layed out my plan for moving forward and I didn't notice it until today - my sencere apologies for that, Martin.
I really like it that we are moving forward by getting budget approved to analyse the problem space around macOS performance and that Martin has taken the lead in getting this (among other things) through the door. However, we are now in a situation where his efforts are actually outpacing mine because I wasn't aware that I've never shared my intention with him to try one last thing (a public "call for help" for macOS performance) before turning this into paid contract work.
Honestly, I do think that we're going to end up with having to pay someone to do this job and that it's probably a foolish "I need to have tried this at least once to have a clear conscience" kind of thing why I would like to appeal to other macOS developers to help us out first. But still, before we are actually writing something up for contract work, I'd like a few more weeks to see if a public call for help will get us any responses.
As I have never dealt with something like this before, we will soon reach a point or have already reached it where we need to press the pause button to wait for possible responses of our call for help. (Hasn't been published yet, it's currently being worked on together with Vectors as we originally scheduled this to be picked up after the dust of the 1.1 release activities has settled.)
Am 07.06.2021 um 16:25 schrieb Martin Owens doctormo@geek-2.com:
On Mon, 2021-06-07 at 09:12 -0500, Ted Gould wrote:
I realize this is a short post, but I'm not sure what you mean by "exploratory mission". How will you know when the work is done and what will be produced? Perhaps a report? What should it include?
Also, I think we'll need to include some way to preclude all the issues that the GTK folks already found in the their OSX backend for GTK3 that encouraged them to rewrite a more performant one for GTK4. We wouldn't want to redo their work.
You answered your question with your suggestion.
The report is to include all the details that the Gtk project have found in terms of speed problems in macOS as well as advice on Gtk4 vs patching Gtk3.
I suspect that your suggestion is that the discovery should be done by volunteers. But this is serious work, it's desperate work, there's no reason not to do this right and get expertise to provide us with the right information to create the right next step to solve the problem for our mac users.
Rene, I'm paraphrasing the general argument here. If you want to step in and explain the plan in more detail if I've missed anything.
Best Regards, Martin Owens