inDigiNeous
Joined 14 years ago
Joined 14 years ago
These days if you want to support macOS, Windows, Linux: I say good luck to you, Electron can save you there.
Electron is not crap, but many javascript developers are crap. You can make fast and memory efficient apps in Electron, if you know how to code.
(Note: Slack or Discord developers don't have that skill)
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.
"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."
So thanks for the developer of this!
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 ?
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.
I think you have to decide at some point: "This is done."
Maybe it requires stripping out some parts, or major parts, of the software you had in mind to reach that, but I feel it has to be done at some point, the feature creep will settle in otherwise and you will never be done.