I'm so happy with this PR! Happy about a further 30% performance improvement to compile times, happy that more and more people are using Magnolia, and happy to welcome @jatcwang as a contributor!https://twitter.com/jatcwang/status/1247075350833582082 …
-
-
Replying to @propensive @jatcwang
Nice - I wonder how much improvements he can do with intentional optimization when the 30% were just accidental :)
1 reply 0 retweets 1 like -
There's probably a little, but not too much more to be gained... I did most of that work a couple of years ago. The 30% here was gained only for a (majority) subset of derivations.
1 reply 0 retweets 1 like -
Replying to @propensive @jatcwang
I'm always happy about performance optimizations. Guess I've worked too long in scrum driven companies where people always prefer features over "premature optimization" or call it "yagni".
1 reply 0 retweets 2 likes -
It can be quite addictive trying to find them, too. I don't do it often...
1 reply 0 retweets 0 likes -
Replying to @propensive @jatcwang
That's true. But imho it's worth trying just a bit (maybe timeboxed to use nomenclature that makes scrum evangelists happy). If not you might end up with apps like slack that are so unoptimized they drain your battery in no time.
1 reply 0 retweets 1 like
Yes, I agree. There's the adage "don't optimise prematurely" but so many projects look like they've interpreted that as "don't optimise, period". Many optimisations are cheap, and are worth applying "just in time", which isn't premature at all. +1 to the Principle of Least Power!
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.