<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 6, 2015 at 11:00 AM, Derek Atkins <span dir="ltr"><<a href="mailto:warlord@mit.edu" target="_blank">warlord@mit.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":y2" class="a3s" style="overflow:hidden">If I write a RoR app<br>
today and use a bunch of gems, if I want to then share that development<br>
with another group it's just... hard! Every system needs to have the<br>
exact same environment. And then god help you if you need to pick up a<br>
system a year later; everything has moved on and you can't get the old<br>
gems anymore and the new gems have changed something fundamental such<br>
that your app doesn't work... :-(<br>
<br>
So you're basically in a situation where you're constantly using<br>
bleeding-edge code because if you don't (and don't keep up) you get<br>
stuck.<br>
<br>
But this has nothing to do with Ruby as a language.</div></blockquote></div><br>That was the biggest problem with the application. But it doesn't help having to deal with all of that on top of the language. Which is why I have limited my comments strictly to the language.</div><div class="gmail_extra"><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>James Sumners<br><a href="http://james.sumners.info/" target="_blank">http://james.sumners.info/</a> (technical profile)</div><div><a href="http://jrfom.com/" target="_blank">http://jrfom.com/</a> (personal site)</div><div><a href="http://haplo.bandcamp.com/" target="_blank">http://haplo.bandcamp.com/</a> (band page)</div></div></div></div></div>
</div></div>