3 ms·
We thought this was the case as well for some internal apps using an ancient version of Rails. The problems start to arise when you bring in new people to work
by swanson 15y ago
We thought this was the case as well for some internal apps using an ancient version of Rails. The problems start to arise when you bring in new people to work on improvements to the project after the creators are gone. It is much easier to find someone that knows Rails 3 than to find someone who can dive into Rails 1/2 code. You have to know what the patterns of that "era" were and be aware of bugs and subtle differences that have been ironed out as the project matured.
Imagine trying to find a blog post explaining why your 4 year old version of an image upload gem doesn't work on JRuby. It's no fun :)
- kappaknight 15y ago> Imagine trying to find a blog post explaining why your 4 year old version of an image upload gem doesn't work on JRuby. It's no fun :) This really depends if you are running a hobby on a server, or running a business. I update client side apps cause it is exciting and it doesn't matter to me if it breaks. If it does, we cry foul and the developer updates a patch hopefully within a few days or weeks. On a production environment, this is much different. There's a reason why people say "if it ain't broke, don't try to fix it." A down time of 5 minutes could cost one company thousands while another company millions. If the cash printing machine is down, having a broken image uploader would be the least of their concerns.