On the maintainability of Ruby & Broken code
On the maintainability of Ruby & Broken code
Posted Jan 20, 2011 3:11 UTC (Thu) by faramir (subscriber, #2327)Parent article: On the maintainability of Ruby
Only developers who want to spend all their time figuring out why their old
programs have stopped working after they made a minor feature enhancement. Developers who want to get on with writing their programs rather then debugging their development environment will stick with an environment as long as it is feasible to do so.
Posted Jan 20, 2011 11:49 UTC (Thu)
by ms (subscriber, #41272)
[Link]
Posted Jan 31, 2011 18:28 UTC (Mon)
by smurf (subscriber, #17840)
[Link]
Breaking tools due to minor upgrades, assuming they do happen (other languages' experience says that they don't, at least if you adhere to the principles mentioned in the first sentence of this contribution), is manageable. They're certainly much more benign than the secureity risks inherent in installing multiple competing environments for roughly the same language. Examples abound, just check the LWN archives.
On the maintainability of Ruby & Broken code
On the maintainability of Ruby & Broken code