sure. @samccone tweets *a lot* about code *on* the critical path. in that case, parse time is real, yeah? @tbreisacher @tdreyno
-
-
accidentally making lazy code eager, dynamically generating code that deopts, etc. 3/
-
you might be thinking, well sure, but those people made stupid mistakes; in my experience 4/
-
these are smart people making "smart mistakes" that nobody could be blamed for. the only way out 5/
-
is to understand where the costs are coming from & how work is parallelized, and then work to 6/
-
pare down those costs without inadvertantly introducing others. 7/7
End of conversation
New conversation -
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.