In my mind macro-optimizations = making things smoother while micro-optimizations = being clever in a way no one will notice.
-
-
-
macro is more like "restructure your code to do less work" while micro is "make each step take less time"
-
good macro optimizations require significant refactors, can be disruptive, etc. but have massive payoffs. Micro can be done in isolation.
End of conversation
New conversation -
-
-
I don't think that is controversial. Picking a better algorithm or data structure has much larger potential than micro optimizations.
-
It's just not what "people working on performance" usually do
End of conversation
New conversation -
-
-
in practice, the harder decision for me is what constitutes macro/micro optim vs effective/ineffective optim.
-
I tried to summarize here:https://twitter.com/wycats/status/906283202230157313 …
-
Thanks. Restructure feels like the right thing usually, esp. if you've got some miles on a project and know it will make the future easier.
End of conversation
New conversation -
-
-
+1 to macro first
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
"Premature optimization is the root of all evil" Knuth
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
But whats the fun on that?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
...eh, and a block for you
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
even sequentially? or rather as restructuring?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.