One thing that is incredibly frustrating about certain classes of changes is that I have to implement 90% of it to find out if it's worth it
-
Show this thread
-
I'm incredibly lucky to be in a situation where I can go spend days or weeks exploring an idea that may amount to nothing (<3 Shopify)
1 reply 0 retweets 20 likesShow this thread -
I *think* I will have a significant perf bump for AR users this time though. I'll know for sure tomorrow (it involves
@rustlang)3 replies 3 retweets 21 likesShow this thread -
Oh awesome. I guess this involves porting something from Diesel to AR?
2 replies 0 retweets 0 likes -
Replying to @thepawandubey
This is moving our internal `Attribute` objects outside of Ruby's GC since they're tied to the lifetime of the AR::Base inst
2 replies 0 retweets 0 likes -
Replying to @sgrif @thepawandubey
Most things that are actually "porting" from Diesel end up getting written in Ruby. e.g. https://github.com/rails/arel/compare/f031a3b9aa6a8093802e0188abce58e0b997078e...bfb770dbcc8432b8d4c1824be0fb2b1ab1ce5d68 … is literally from Diesel
1 reply 0 retweets 2 likes
(https://github.com/rails/rails/commit/213796fb4936dce1da2f0c097a054e1af5c25c2c … is the corresponding Rails change and has more context)
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.