1–10 of 27 posts
Something that when the rest of someone's computer is slowing down, this can stay responsive.
Not everyone has the fastest hardware or much ram; people like to have 100s of tabs open; and CPU's overheat and throttle, especially laptops.
You're not going to hit your responsiveness goals otherwise. And it's not going to feel native otherwise (if anyone actually cares about that anymore, I dunno)
Linux/Windows/MacOS: https://github.com/libui-ng/libui-ng
If you want the fastest cross-platform native app. Build a native app for each platform and have the design teams review each other's work so everyone stays roughly on the same page. You're not going to hit your responsiveness goals otherwise. And it's not going to feel native otherwise (if anyone actually cares about that anymore, I dunno)
The question still remains then of which to use for each platform.
On macOS there is Cocoa (Swift or ObjC(++) or pure CPP) and Swift UI.
On Windows there is .NET C# or CPP and a bunch of other stuff.
Any thoughts?
Yeah so without having to overwrite some very deep OS settings, which will likely raise some red flags for your app requiring administrator privilege to run, you aren't going to get this. If someone has a browser thats taking up most resources, its gonna throttle everything.
There is generally very little reason to write anything but web apps these days for things that don't need to touch specific hardware. If you stick to as much native js/css/html as possible (i.e avoid large libraries), it will load blazingly fast and use way less resources then web apps that are considered fast.
>Something that when the rest of someone's computer is slowing down, this can stay responsive. Yeah so without having to overwrite some very deep OS settings, which will likely raise some red flags for your app requiring administrator privilege to run, you aren't going to get this. If someone has a browser thats taking up most resources, its gonna throttle everything. There is generally very little reason to write an…
I think modern frameworks are so bad at perf because they assume people just have so much compute available and are focusing on one app at a time.