User: Password:
Subscribe / Log in / New account

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

"...Developers will almost always want to run bleeding-edge code, to make use of the latest and greatest language and interpreter features. ..."

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.

(Log in to post comments)

On the maintainability of Ruby & Broken code

Posted Jan 20, 2011 11:49 UTC (Thu) by ms (subscriber, #41272) [Link]

Depends - if the language developers are sufficiently concerned with maintaining backwards compatibility then it's not too hard to run the latest release. Erlang is a good example of this - yes, I'd be quite happy to see them rewriting most of their standard libraries to get rid of a number of warts, but I'm also quite happy with them not doing so.

On the maintainability of Ruby & Broken code

Posted Jan 31, 2011 18:28 UTC (Mon) by smurf (subscriber, #17840) [Link]

This is why G*d invented test suites, language specifcations, and the idea of a "stable version" (all of which the Ruby people apparently haven't heard of yet).

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 security risks inherent in installing multiple competing environments for roughly the same language. Examples abound, just check the LWN archives.

Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds