News for hackers. Stuff that matters.
Re:Ruby has been fast enough for 13 years by silversmith on Monday May 16, 2016 @03:50PM (#11709083)
Counterexample: just yesterday I spent nearly two hours trying to understand why a bunch of records was not being updated to database. Turns out that when attributes on already persisted records get assigned in particular sequence, ActiveRecord suddenly decides that there are no changes to be saved. Swap two calls, everything suddenly works. And there was nothing to help me to get to that solution, just groping in the dark and trusting my years of RoR development for a general direction.

Rails is great, and I've been productive in it for a long time. But the complexity (some would call it bloat) is real, and there are nasty edge cases. And when you stumble upon one, well, good luck.

Re:Ruby has been fast enough for 13 years by dopamean on Monday May 16, 2016 @05:45PM (#11709886)
I'd like to hear more about this. Is it possible you could share an example that demonstrates what you're talking about? Thanks.
Re:Ruby has been fast enough for 13 years by ccallebs on Monday May 16, 2016 @06:15PM (#11710069)
That definitely sounds like it should be reported as a bug.