Why performance optimization is hard work
Why performance optimization is hard work
purplesyringa.moe
Why performance optimization is hard work
You're viewing a single thread.
7 comments
-
Most performance optimisation can be done through improving algorithms and data structures, and knowing well the language you're using.
I don't think I've encountered any performance issue that wasn't either:
- Unavoidable because of what I'm doing
- Coming from an inefficient data structure or algorithm
- Coming from a bad use or pitfall of the language.
Of course there are specific cases such as low-power environments and such, but that's not what most people talk about when they talk about performance.
I also would like to point out my confusion with the obsession towards performance when it's not needed (such as "is languageA 10% faster than languageB?") but then everyone putting web technologies everywhere, from games to desktop software. It's starting to feel like performance is more of a cult than a pragmatic question at this point.
-
Yeah I've noticed a rise in electron apps. Just because it is technically cross platform doesn't make something efficient. In a lot of cases, devs and large enterprises would be better off simply rewriting code from scratch in Kotlin, Flutter, etc., if performance is the name of the game.
-
Just because it is technically cross platform doesn't make something efficient.
If you want performance you'll surely won't go with cross platform. The more general something is the less efficient it is.
-
Precisely, but I mean in terms of developer hours. Long term, apps that are developed natively for their target platform are much easier to extend and maintain.
-
-
7 comments