10 engineers on Hacker News describe using Active Record first-hand: 2 endorse it, 3 regret it, 1 are mixed.
“since it was a bunch of Active Record hacks, there's a number of data-related features we couldn't do”
regret · production · rudyrigot · 2020-05-27 · source ↗ · wrong label?“I've moved away from full, ActiveRecord-style ORMs. They don't work particularly well for my use cases”
regret · production · dfcowell · 2017-12-09 · source ↗ · wrong label?“I found AR to be perfect for them to the point that I want to disguise Ecto as AR”
endorse · production · pmontra · 2017-10-27 · source ↗ · wrong label?“Plus ActiveRecord is slow, especially with collections.”
regret · production · briantakita · 2014-12-01 · source ↗ · wrong label?“I've worked on dozens of projects using ActiveRecord. ... About 90% of the time, the ORM does the right thing.”
endorse · production · ekidd · 2011-09-17 · source ↗ · wrong label?“Sure ActiveRecord was buggy too, but in a totally different way. The bugs didn't crash it, or put weird data into the tables”
mixed · production · agavin · 2010-12-15 · source ↗ · wrong label?“Using `#map` will instantiate a `Tag` object and do all the slow(er) metaprogramming”
neutral · production · joshmn · 2020-11-15 · source ↗ · wrong label?“We did integrate ActiveRecord/Support”
neutral · production · esilverberg2 · 2018-10-15 · source ↗ · wrong label?“The PostgreSQL adapter warns NOTE: ActiveRecord 4.2 is not (yet) fully supported by AR-JDBC”
neutral · personal · pmontra · 2015-07-23 · source ↗ · wrong label?“In my company, we write migration scripts (activerecord migration) to modify table structures.”
neutral · production · yliang · 2014-12-02 · source ↗ · wrong label?