[rspec-devel] Splitting up the APIs

David Chelimsky dchelimsky at gmail.com
Sat Nov 25 22:50:10 EST 2006


On 11/25/06, Jay <jay at jayfields.com> wrote:
> You can (and probably should) unpack a particular gem locally in your
> project.  At that point, the API wont change at all. This doesn't
> solve your problems when you need a new version of the gem, but if
> the gem already does everything you need then it might help.
> Jay

That is sound advice. It gives you much more control over when you
absorb changes.

Thanks Jay!

David

>
> On Nov 25, 2006, at 7:07 PM, Wilson Bilkovich wrote:
>
> > On 11/25/06, aslak hellesoy <aslak.hellesoy at gmail.com> wrote:
> >> Christian (http://tinyurl.com/sr665) and Rick
> >> (http://tinyurl.com/y736tq) have taken the ideas they like from
> >> RSpec,
> >> reimplemented it in their own way (NIH) and released it to the
> >> public.
> >> Competition is good - as long as it brings something new to the
> >> table.
> >> I'm not sure what these two clones do better though.
> >>
> >
> > They don't change the API every 12 seconds. =(
> >
> > I've considered switching to Chrstian's even though I would miss
> > certain RSpec features, simply because it is less of a moving target.
> > _______________________________________________
> > rspec-devel mailing list
> > rspec-devel at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-devel
>
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
>


More information about the rspec-devel mailing list