3 ms·
I use Rails, but also Elixir, and in the past Java, .Net, and many other tech stacks. In my experience all large or very large scale apps upgrades (and I've do
by thibaut_barrere 8y ago
I use Rails, but also Elixir, and in the past Java, .Net, and many other tech stacks.
In my experience all large or very large scale apps upgrades (and I've done quite a few) are complicated in a way or another, no matter the stack. Technical debt stacks up in subtle ways (dependencies get obsolete, a specific feature used the framework in unusual ways, stuff can be rewritten with more built-in framework features etc).
I don't see how this article would give Rails bad publicity, personally; I'll add that the advice they provide is pretty much what I would recommend for any tech stack too.
- nambit 8y agoI've done upgrades on absolutely massive codebases for java to JDK7 and JDK8 and have never had anything but minor issues. Very rarely does something break backwards compatibility.
- thibaut_barrere 8y agoWell, I've upgraded an app from Struts 1 to Struts 2 and I don't want to do it again :-) - https://www.infoq.com/articles/converting-struts-2-part1 https://www.infoq.com/articles/converting-struts-2-part1 - https://www.infoq.com/articles/migrating-struts-2-part2 https://www.infoq.com/articles/migrating-struts-2-part2 - https://www.infoq.com/articles/migrating-struts-2-part3 https://www.infoq.com/articles/migrating-struts-2-part3 Granted, the "upgrading" situation has improved since then in the Java world, but it hasn't been always super nice in the past.
- callumjones 8y agoI'm not sure if you can compare upgrading a VM/platform that is usually designed for backwards compatibility to upgrading a framework.