4 ms·

meanwhile, i have to work on a rails 3.2 app with ruby 2.2

• WJW 4y ago
  What's preventing you from upgrading?
  • MiraiY 4y ago
    the mindset "if it works, leave it there" edit: also it's a big project without specs, good luck at finding broken stuff...
    • weatherlight 4y ago
      Going to sound nuts but perhaps you can leverage ChatGPT4 to start generating some tests, based on some prompts for like 20% of your app. you just have to be pretty disciplined about how you write your specs.
      • MiraiY 4y ago
        actually, maybe not a bad idea
• awesomegoat_com 4y ago
  That's battle tested by now. Call it enterprise.
• caseyf 4y ago
  nothing wrong with Rails 3.2 :) get it on Ruby 3.1 if you can - https://railslts.com https://railslts.com
• mattbrewsbytes 4y ago
  Those versions are so far removed from receiving any security patches I'd probably want management to sign off that they heard me state this and they take full responsibility if shit hits the fan. Also, are you at least a little concerned about your career using a tech stack that old?
  • MiraiY 4y ago
    I work on multiple projects, the main one i work on i recently upgraded from 5.2 rails to 6.1, and ruby 2.7 => 3.0
  • Alifatisk 4y ago
    I learned Rails a year ago and haven't seen any sign that should concern me.
• TheRealDunkirk 4y ago
  This is fine, until someone comes along and asks can we "just" do <this>? Someone tried to foist a Laravel app on me, to update it with some new functionality. It was so old, I had to setup a Linux box with manually-downloaded versions of PHP and the framework. Not being familiar with Laravel, I needed lots of docs and examples. They were impossible to find, and it turns out Laravel from that long ago doesn't work very much like today's version. You're in luck here, because Rails 3 works pretty much the same way as 6 and 7.