Re:Ruby 2.6.0-preview2 released with JIT
by jashmatthews on Monday June 04, 2018 @09:47AM
(#17227749)
It's not required at all! Rails adds a completely avoidable massive overhead because of the way it overrides to_json see: https://twitter.com/jashmatthews/status/967423661908070401
Re:Ruby 2.6.0-preview2 released with JIT
by vinceguidry on Monday June 04, 2018 @10:22AM
(#17227986)
Have you ever used Ruby's JSON.dump? The second it runs into anything that it can't convert, you get "#<Object:0x00007fab05133078>" everywhere in your output.
Re:Ruby 2.6.0-preview2 released with JIT
by jashmatthews on Monday June 04, 2018 @11:13AM
(#17228515)
Of course! We use Oj.dump in Rails compatibility mode in production at ChartMogul.
Ideally, you'd serialize directly from the database, bypassing the application entirely. Easily doable in ActiveRecord, but it's an explicit action, not the default. Not even sure if it's available in other databases besides PostgreSQL.