4 ms·
I know many folks in the Rails community wonder why anybody could still be using a years-old system. Once this statement is no longer true, Rails will be ready
by hvs 13y ago
I know many folks in the Rails community wonder why anybody could still be using a years-old system.
Once this statement is no longer true, Rails will be ready for the enterprise.
- freehunter 13y agoJust recently my enterprise retired our Windows 3.1 environment. It was kept running to support a system that supported a system that supported dial-up VPN access for a certain subset of users. And that's not incredibly uncommon...
- dhh 13y agoOnce that statement is true, Rails will BE the enterprise. Don't bank on it. (And by that I mean we'll continue to release new versions that at times will be backwards incompatible and require work to upgrade to).
- eduardordm 13y agoAlready is! I've submitted talks a few times about my experiences with Rails in an enterprise environment, no luck. Anyway, We run rails since 2006, we got large and became a bank. Numbers: 5032 models, 42 gems, 16 submodules, lots of C extensions and eventmachine servers running in threads. From our website to ATM servers, it's everything inside a single rails application. We managed to upgrade from 2.3 to 3.2 in 6 months. Already running 4 (took only a few hours). We just completed our migration from Oracle DB to Postgres.
- bryanh 13y agoThat is wildly interesting. If you could swing it, you should write up a full post about what that your Rails app looks like after 7 years in production.
- rurounijones 13y ago5032...models...I, whu... ONE application?! I would never have thought that was actually possible. A write-up regarding your architecture / challenges / solutions / future plans in a blog post would be extremely interesting. (How long does the test suite take to run!?)
- Capoferro 13y agoThis is enterprise. What test suite?
- unimpressive 13y agoI'd like to read more about this, if you're allowed to tell.
- eduardordm 13y agoI've been postponing writing about this for a long time, mostly because I wanted to talk at railsconf before writing a post (who am I kidding, I just procrastinate a lot), having submitted the talk for the last 3 years without getting in I'll definetly write a long post about it.
- steveklabnik 13y ago> having submitted the talk for the last 3 years without getting in That's a shame. If it helps any, all my talks were rejected this year too. :/
- ewalk153 13y agoPerhaps after receiving feedback on your post, you'll find one oe two aspects that you can refine or drill deeper on and will make a great railsconf talk for next year.
- patio11 13y agoI would pay to hear this talk.
- rmc 13y agoSounds like you have some interest from others here. Talk into a webcam for an hour. Sell the video.
- flazzarino 13y agowhat is your memory footprint?
- prawks 13y agoI was actually surprised reading that statement given Rails' maturity. When the large AD vulnerability was announced and many people were caught in the open for a while I had assumed there were a large number of people running version n-1 Rails.