|
|
|
|
|
|
by ooobit2
2107 days ago
|
|
|
I don't know the direct answer, but I have a deduction in my head to work with...? I'll just put it out there: I think speed is deeply impacted by high-level frameworks that parse or compile at runtime. React Native is a framework on Android, which is a framework on Java, which compiles at runtime. IDK if anything in that chain compiles down to Assembly or machine code before you open an app made in React Native. That tied with the bloat of JIC background services sitting idle eats bandwidth. Garbage collection checks operate in a loop, checking again and again if all these unused but loaded processes still exist at their addresses. And when you pile those on each other, it seems relatively easy to see how modern CPUs don't seem much faster than chipsets from 5-6 years ago. I stopped programming around 8 years ago because I hate the current MVC model most software is created and maintained with. What got me interested recently in dipping back in was a video on branchless programming. I love the idea of unit testing at the machine code level for efficiency, and then figuring out how to trick the compiler or runtime and the chipset into making quick, predictive outputs to reduce idling on branches or making 15 steps for something doable in as little as 4. That feels like a completely opposing direction to take given the current priorities of engineers across almost all industries, even oldtime ones like Gaming. |
|
|