Rails 3.2.13 - Performance regressions and major bugs
blog.bugsnag.com
Rails 3.2.13 - Performance regressions and major bugs
1–10 of 76 posts
Re: Rails 3.2.13 - Performance regressions and major bugs
#2You know when you're already having performance issues on Heroku having a performance regression is not fun.
Re: Rails 3.2.13 - Performance regressions and major bugs
#3At this point I'm seriously considering dropping Rails as my framework of choice and reverting back to ASP.Net MVC.
Why?
1. Security fixes are released very quickly (good thing), but more often then not they break existing code (bad thing) - and while you _can_ wait for the next patch to fix those break points, you're left wide open since everybody can see what was broken and how to exploit it.
2. I'm not nearly smart enough with Ruby to apply 'band-aids' I read people write in Rails source code. I just don't have the time and energy to fix code in the actual framework when I need to be fixing _my_ code.
======
So there you have it; I'm bailing.
It was a fantastic ride, Ruby is a beautiful language, but Rails is just a clusterfuck (_for me_).
I need stability and predictable behavior. If that means releases every 6 month to 1 year, so be it.
So long and thanks for all the gems.
Re: Rails 3.2.13 - Performance regressions and major bugs
#4At this point I'm seriously considering dropping Rails as my framework of choice and reverting back to ASP.Net MVC. Why? 1. Security fixes are released very quickly (good thing), but more often then not they break existing code (bad thing) - and while you _can_ wait for the next patch to fix those break points, you're left wide open since everybody can see what was broken and how to exploit it. 2. I'm not nearly smar…
You do know there are other Ruby frameworks than Rails, and other development environments than ASP and Ruby right?
Re: Rails 3.2.13 - Performance regressions and major bugs
#5As someone who is relatively new to Rails can someone explain to me why it seems to update more than anything else I've used?
Re: Rails 3.2.13 - Performance regressions and major bugs
#6At this point I'm seriously considering dropping Rails as my framework of choice and reverting back to ASP.Net MVC. Why? 1. Security fixes are released very quickly (good thing), but more often then not they break existing code (bad thing) - and while you _can_ wait for the next patch to fix those break points, you're left wide open since everybody can see what was broken and how to exploit it. 2. I'm not nearly smar…
You do know there are other Ruby frameworks than Rails, and other development environments than ASP and Ruby right?
Yes, I used to use ASP.Net MVC for pet projects, then switched to Rails - I also use CakePHP and Django for actual paying work/contracting.
But thanks for the passive aggresive comment.
Re: Rails 3.2.13 - Performance regressions and major bugs
#7At this point I'm seriously considering dropping Rails as my framework of choice and reverting back to ASP.Net MVC. Why? 1. Security fixes are released very quickly (good thing), but more often then not they break existing code (bad thing) - and while you _can_ wait for the next patch to fix those break points, you're left wide open since everybody can see what was broken and how to exploit it. 2. I'm not nearly smar…
I've been running Java and Rails since 2006 in my company (large), we use C# for a small number of desktop applications.
This will come out harsh, but I'm being honest: If you are not willing to fix/adapt/improve the framework you are using, you better not be using ASP.NET also (try a google search on asp.net issues), or any framework at all. In fact, developing larger more complex software might not even be possible without adapting frameworks for your specific problems.
That said, our run so far with Rails and Java (we are still using 2.3!!!):
- We have 38 patches applied to Spring
- 4 patches in apache santuario.
- One security patch on Grizzly (glassfish)
- Rails: One single pull request https://github.com/rails/arel/pull/174
Re: Rails 3.2.13 - Performance regressions and major bugs
#8Not happy? Do something about it: try release candidates, report bugs, and help triage and fix reported bugs.
Re: Rails 3.2.13 - Performance regressions and major bugs
#9You know when you're already having performance issues on Heroku having a performance regression is not fun.
How is this
> […] handing that task to Sprockets instead of resolving internally […]
even remotely related to performance issues because of random routing? You're mixing two issues that have nothing in common.
Re: Rails 3.2.13 - Performance regressions and major bugs
#10At this point I'm seriously considering dropping Rails as my framework of choice and reverting back to ASP.Net MVC. Why? 1. Security fixes are released very quickly (good thing), but more often then not they break existing code (bad thing) - and while you _can_ wait for the next patch to fix those break points, you're left wide open since everybody can see what was broken and how to exploit it. 2. I'm not nearly smar…
Would you really be willing to give up the productivity benefits and developer happiness over a few mishaps? Also, it's generally a good idea not to upgrade to the next software version until seeing the repercussions its had.