News for hackers. Stuff that matters.
Re:Rails has won: The Elephant in the Room by busterarm on Tuesday May 24, 2016 @03:31AM (#11759594)
I used Sequel once on a major project and as nice as it was, there was major pain. Pain I wouldn't have had with ActiveRecord.

I seriously would have gotten the job done in half the time, with less problems had I just used Rails...and I've written my own ORMs before - I have somewhat of a clue.

Re:Rails has won: The Elephant in the Room by bdcravens on Tuesday May 24, 2016 @04:03AM (#11759704)
I'm having the opposite experience, but I think that's because I'm working on a legacy database that really doesn't follow conventions. Even when overriding defaults in AR, I still found myself trying to hammer what I was doing into a AR-shaped block, whereas Sequel feels like it lets me craft a resultset as I desire regardless of what I'm starting with. But like I said, it's a legacy database and it was originally driving an app where writing raw SQL was the SOP, some of which really leans of higher-level SQL engine features for function and performance.
Re:Rails has won: The Elephant in the Room by vidarh on Tuesday May 24, 2016 @04:45AM (#11759854)
I'm curious what pain you experienced with Sequel, as I have the exact opposite experience.