3 ms·
I don't want to say "there was something horribly wrong with your code" but "there was something horribly wrong with your code." I've worked on a lot of large r
by brightball 3y ago
I don't want to say "there was something horribly wrong with your code" but "there was something horribly wrong with your code." I've worked on a lot of large rails codebases and never seen anything close to the performance numbers you're describing.
To each their own though. IMO Rails is significantly faster when it comes to being able to get a complete product to market with all of the trimmings. When it comes to specific programming problems here and there a lot of languages will be able to get the job done.
That holistic "get everything done well with a small team so we can be profitable" scenario is where Rails outshines most everything else.
Plus, if you're concerned about the runtime, just switch to JRuby.
- mortallywounded 3y agoThe code itself wasn't very complicated but there was a fair amount (~15KLOC of Ruby). I'm sure there were issues in there, but I could never figure out what they were. I am not a terrible Rails developer either-- prior to building my product I had done Rails professionally for five years at a startup. It's not like I was slinging Rails code like a bootcamp graduate :)
- brightball 3y agoIt really sounds like a memory leak based on what you’re describing. Those can be tough to track down too.
- Alifatisk 3y ago> That holistic "get everything done well with a small team so we can be profitable" scenario is where Rails outshines most everything else. Well said