5 ms·
At 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 q
by sergiotapia 14y ago
At 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.
- masklinn 14y agoYou do know there are other Ruby frameworks than Rails, and other development environments than ASP and Ruby right?
- sergiotapia 14y agoYes, 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.
- JonnieCache 14y agoWhile that may be a passive aggressive comment, sinatra is bloody brilliant all the same. You can basically pretend you're writing rails code, but with a tiny fraction of the dependencies, and actual fast response times. Sinatra, sequel and postgresql is a dream combo. I wouldn't use rails for a new project these days, I got bored of the un-navigable code a while ago. These patches and regressions are the icing on the cake.
- masklinn 14y ago> Yes Because your comment didn't exactly hint at it considering its completely binary assertion of "Rails or ASP" > But thanks for the passive aggresive comment. I'm very sorry you found it passive, that was not intended.
- eduardordm 14y agoI'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 https://github.com/rails/arel/pull/174
- cooldeal 14y ago>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), of any framework at all. In fact, developing larger more complex software might not even be possible without adapting frameworks for your specific problems. Huh what? Stack Overflow with it's extreme load works quite well with ASP.NET. >try a google search on asp.net issues Okay, I did, what I am supposed to be looking at?
- JonnieCache 14y agoThe point is, SO almost certainly aren't using vanilla ASP.net. Nobody can succeed for too long without maintaining and cultivating their stack.
- atonse 14y agoI don't know about Vanilla ASP.NET but they are pretty much using stock config'd IIS and Servers. So I would be very surprised if they weren't using stock ASP.NET (with their own filters, etc using public APIs I'm sure)
- JonnieCache 14y ago
- Axsuul 14y agoWould 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.
- sergiotapia 14y agoThat's the thing! I find myself ping-ponging in my mind between "But Ruby and ActiveRecord are so beautiful and easy to use." and "But what happens if the 'magic' breaks?" Trust me, I have been thinking about what you say every day for the past 5 days.
- damoncali 14y agoYou're thinking too much. Unless it's a "the world is ending" level security fix like the recent yaml stuff, wait a couple weeks for this stuff to come out and get fixed. Then upgrade.
- static_typed 14y agoYou are now in the place I was recently -- the decision we tool was to migrate onto Python and their web ecosystem. We haven't looked back since -- well, we have given an glance or two back since, and viewing the slow-motion car crash that is Rails today, we just feel sorry for those left behind that are discovering 'The Rails Way'. Ironically, given DHH's comment on Rails about it being 'Omakase', I should point out that it translates as "I'll leave it to you" -- security, I'll leave it to you, software engineering, I'll leave it to you. Food for thought indeed. Remember -- Ruby to pose, Python for Pros.
- deleted 14y ago[deleted]
- lparry 14y agoWow, you're either one of those incredibly rare ruby devs who actually run windows, or you're going to switch your entire environment in order to switch frameworks. Something doesn't smell right
- sergiotapia 14y agoI'm a polyglot. I don't encase myself in any 1-thing. I use Mac at work, Windows at home for media and games, and Linux Mint 13 on my laptop for Ruby/Rails. I only used Linux because of Rails, but since I'm switching back (I have Visual Studio 2012 downloading as I type this), I'll have no need for Linux on my end-user machines anymore.
- emidln 14y agoIf you do not know your language/framework well enough to adapt it to your circumstances, you certainly are not well qualified enough with said software to list it as something you "know". This is one of the largest lies perpetuated on this site. If you know just enough of something to follow some tutorials and crank out cookie-cutter sites using Rails/Django/Asp/Grails/CodeIgniter/etc, but fail the moment you encounter basic ecosystem problems, you aren't a polygot. You're a liability to your team for not understanding anything well enough to work around common issues. You're probably curious and love to try new things, but the implied part of being able to proficiently wield whatever tool is correct, or at least on hand, is something escaping you. If by polygot you mean you know some syntax, the basics of the ecosystem, and generic system design, algorithms, etc while expecting to dive as deep as necessary into any given environment, you're still failing the definition. This would be the point where you RTFS so you know where to override/monkeypatch/workaround.
- sergiotapia 14y agoI disagree. I count writing and selling commercial software with said technology as 'knowing' something. Academics be damned.
- RegEx 14y ago
- calinet6 14y agoYou're on the cutting edge of an extremely popular framework. If you want, you're welcome to use Rails 2.3 or older and you'll encounter many fewer changes. I imagine the 3.0 branch will have much the same stability once major development moves to 4.0.
- rst 14y agoFWIW, the Rails security team says they're about to drop suport for 2.3, and this time they really mean it. (They say.) The current announced security policy is that once 4.0 gets released, they'll only be doing security patches for 4.0 and 3.2; 2.3 will be left out in the cold. It's quite possible that someone will pick up the baton, as there still are a number of production 2.3 apps out there, and porting to 3.0+ --- more a "port" than an "upgrade" --- is a real pain. But I'm not sure anyone has stepped forward yet, and until someone does, you're taking your chances.
- jjoos 14y agoYou should seriously consider running mono>=2.10 with asp.net mvc. It completely fixes your rails security issues, while still letting you use ruby as your main languages. Also you gain a _lot_ in security by obscurity and hipster points. I don't know about stability, haven't tried this myself. Check out the mono project for details: http://www.mono-project.com/Mono_Project_Roadmap http://www.mono-project.com/Mono_Project_Roadmap
- threedaymonk 14y agoI've not heard of anyone using IronRuby in earnest, and it doesn't seem to have been updated in a couple of years. Is it a realistic option?