[#78633] ruby/spec needs help from CRuby committers — Benoit Daloze <eregontp@...>
Currently, ruby/spec is maintained mostly by individuals and enjoys the
13 messages
2016/12/13
[#78963] Re: ruby/spec needs help from CRuby committers
— Urabe Shyouhei <shyouhei@...>
2017/01/04
I did ask attendees of last developer meeting to join this
[#78642] Re: ruby/spec needs help from CRuby committers
— Eric Wong <normalperson@...>
2016/12/14
Benoit Daloze <eregontp@gmail.com> wrote:
[ruby-core:78642] Re: ruby/spec needs help from CRuby committers
From:
Eric Wong <normalperson@...>
Date:
2016-12-14 02:52:33 UTC
List:
ruby-core #78642
Benoit Daloze <eregontp@gmail.com> wrote:
> Dear CRuby developers, what do you think?
> What are your concerns with this approach?
As I've stated in the past, I will not depend on non-Free
services or software (including JavaScript and remote APIs)
or any GUIs (too fragile, and Ruby itself doesn't need one).
There does not seem to be a mutually acceptable way for me to
communicate with other rubyspec developers while sticking to my
principles. I don't want to burden anybody to have them go out
of their way to accomodate me, either.
Otherwise, I would've been happy to help with the *_nonblock API
changes I did in 2.3. At least I documented them in NEWS in the
hope it would be easier for other implementers to find.
Anyways, I do not expect to have any future as a developer.
Just saying my piece and moving on...
P.S. spec DSL is annoying and abuses dynamic core classes;
hurting debuggability and predictability compared to
(test/unit|minitest); but that's a minor issue.
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>