Using >= Considered Harmful (or, What’s Wrong With

Using >= Considered Harmful (or, What’s Wrong With >=) « Katz Got Your Tongue?:

Guilherme Silveira , Posted August 21, 2010, 3:47 pm Its the dependency hell that every dependency library has (Ivy with .net or java and Maven with Java face similar issues). Just the example where the “weird edge-case is exercised in production, and which your tests would have caught.”, if your tests did not get the failures in your test and continuous integration environment, it means you did not test that corner case. So even if you change by hand the gem dependency you would not find the failure in your test enviroment. Of course, the minimum quality requirement here is that you use the same gems in production that you use in dev/test. But there is a huge number of people who does not, too bad. In those cases, its surely better to play safer and use ~>. It turns out that the question is, as with the other engines, do you want your tests to fail early or fail late? Do ...

Full article: http://yehudakatz.com/2010/08/21/using-considered-harmful...