I know that’s a major reason why I don’t use them more often. I was bitten by reject vs reject! In one of my more notable “oh shit. I just broke everything” events.https://twitter.com/nateberkopec/status/1038125248045047809 …
-
Gems are an entirely different animal though. They tend to have hotter hot paths than app code, and are more likely to live in the hot path than not. Plus as an author of a gem you have more of a responsibility to your users to pay attention to perf
But that doesn't mean that changes which are significant in gems are something that app developers should care about or are likely to benefit from, unless it's somewhere that there's a known perf problem.
-
-
Most pathological example -- I remember a few years ago way too many people were sharing an article "http://block.call is twice as slow as yield!!!!" telling app developers to stop using `&block` which was just...........
-
That case is VM specific, and also just not important. It's 8ns on my personal machine, which will not add up to a measurable difference in app or gem code. We have *one* place in Rails which cares https://github.com/rails/rails/blob/dd29fabebf1b702031213361b7757be5892cd59f/activerecord/lib/active_record/attribute_methods/read.rb#L67-L79 … and it's the hottest of hot paths
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.