Could possibly just hotpatch my existing app, add this to the packed in javascript .asar resource file and not having to make a new build with updated Electron version.
Reminds me of the performance optimization somebody discovered in Super Mario World for SNES, where displaying the player score in was very inefficient, taking about 1/6 of the frametime allocated.
"SMW is incredibly inefficient when it displays the player score in the status bar. In the worst case (playing as Luigi, both players with max score), it can take about a full 1/6 of the entire frame to do so, lowering the threshold for slowdown.
Normally, the actual amount of processing time is roughly proportional to the sum of the digits in Mario's score when playing as Mario, and the to the sum of the digits in both players' scores when playing as Luigi. This patch optimizes the way the score is stored and displayed to make it roughly constant, slightly faster than even in the best case without."
I remember dropping parallel hashmap into my C++ app after years of using the standard library containers, and being honestly positively surprised my app got significantly faster after that.
Metal allows Apple to squeeze that extra performance out of their devices.
They have full control over, and can implement whatever they need to deliver Apple Vision Pro for example.
With Vulkan, they would have to wait for a committee to approve required changes, and still they could not probably optimize it to match their GPU an CPU hardware profiles in such an efficient way.
And not least at all, to optimize the developer experience and tools. Apple GPU debugging tools are probably the best tools you get for graphics development debugging, and you get that only on macOS.
IMO Metal is a nicer API than Vulkan. At the same time, you can ask, why should Microsoft get to keep DirectX, and not just write a Vulkan driver ?
I love mate. It has probably saved my life as a software developer, not tolerating the strong effect of coffee on my sleep, but yerba mate, and especially freshly stored in vacuum bags, slightly dried but not smoked is my favorite.
Meta Mate (https://metamate.cc/) makes a total bomb of a mate product, can highly recommend if you are in Europe and want to try out their refreshing Meta Mate 23.
Have to order another batch from them now, I've tested many mates but theirs just tastes and works the best for me.
Was introduced to mate by a fellow software developer back in the day, happy that he did, would not have figure out it otherwise.
Well, that is a noble goal. Hope you can manage even portion of it.
Would be nice to have a way to deploy macOS applications on other platforms, but seeing it is already difficult enough to make sure macOS applications even work on different versions of macOS, that is a difficult task to achieve.
But godspeed to your project, Objective-C, Cocoa and the whole NeXTSTep visual identity is a nice combo.
I'm generally speaking about the state of X11 vs macOS or Windows. Like configuring multiple monitors, getting your mouse working just right or other tasks that sometimes can just be freaking difficult with X11. But not wanting to go into that flamewar now.
I would be surprised if it's better than Qt, in fact I know it's not. GTK+ also has had a lot of work during the years, but they have dropped the balls many times over major revisions, so in that sense it might be a better framework than GTK.
But then again, it all comes down to who uses these. Qt is widely used beyond Linux in application development, and modern QT is actually a very nice development environment.
Wayland is also in a state of not-complete. What I'm trying to say here is that the display technologies behind most Linux environments are not in a good state. They work, yes, but some things just don't work or are impossible to setup compared to eg. macOS or Windows.
This is mostly due to open source fragmentation and legacy code in my view, and the fact that everybody and their brother would rather fork out their own desktop environments than decide to make couple of good ones, but hey that's Open Source. Also missing commercial support of course.
Sounds like a cool hobby. But solving basic desktop tools, sounds like bikeshedding to me :) Not to disrespect the project, I find Objective-C and the Cocoa model nice, but realistically looking at it almost nobody uses GNUStep, so why write apps for it ?
Yeah this was a really interesting project when it got started, like in the late 90s ? Now, realistically, even though I like the idea, who is going to use this ?
Maybe like a compatibility setup for old NeXTStep applications ? Or porting some old macOS applications to Linux environments ?
Working on top of the X11 implementation also doesn't really provoke trust to look into the project.