It appears that Ruby on Rails really was the cause of Twitter’s problems. John Hardy Technical Labour February 20, 2018 1 Minute It appears that Ruby on Rails really was the cause of Twitter’s problems. Share this: Click to share on X (Opens in new window) X Click to share on Facebook (Opens in new window) Facebook Like Loading... Related Published by John Hardy Closures are a poor man's object. Objects are a poor man's closure. View all posts by John Hardy Published February 20, 2018
Private method, never called anywhere else. “enable_nazis()” is dead code to be… eliminated …by the optimizer. LikeLike Reply
Private method, never called anywhere else. “enable_nazis()” is dead code to be… eliminated …by the optimizer.
LikeLike
Not if optimizer itself is a (head) Nazi enabler.
LikeLike