[ruby-core:51463] Re: [CommonRuby - Feature #7549] A Ruby Design Process

> http://brixen.io/2012/12/30/a-ruby-design-process-talking-points

It says "The purpose of the proposed design process is to prioritize those
things that create a unified Ruby programming language.".
But I think it is not the fundamental purpose.
Just after the sentence, "For businesses and developers whose salaries
derive from writing Ruby, the value of a unified Ruby programming language
should be obvious." must be your true desire, isn't it?

Your proposal is misunderstood because you don't write this and your
proposal is not based on this.
You should write the proposal based on the fundamental desire and its logic
and method must always be derived from that.
And it should have merits for people other than businesses and developers
whose salaries derive from writing Ruby.


2013/1/1 brixen (Brian Ford) <[e-mail]>

>
> Issue #7549 has been updated by brixen (Brian Ford).
>
>
> I've written another post addressing many of the misunderstandings about
> my proposal expressed in this thread:
>
> http://brixen.io/2012/12/30/a-ruby-design-process-talking-points
>
> We are starting work on the Consensus application here:
>
> https://github.com/rubyspec/consensus
>
> Cheers,
> Brian
> ----------------------------------------
> Feature #7549: A Ruby Design Process
> https://bugs.ruby-lang.org/issues/7549#change-35171
>
> Author: brixen (Brian Ford)
> Status: Open
> Priority: Normal
> Assignee:
> Category:
> Target version:
>
>
> Matz,
>
> At RubyConf 2012, I gave a talk about a design process for Ruby (
> http://www.confreaks.com/videos/1278-rubyconf2012-toward-a-design-for-ruby).
> So far, over 12,000 people have viewed that talk. I think it is reasonable
> to say that many people are concerned about and interested in a design
> process for Ruby.
>
> On Monday, we had an IRC meeting of Ruby implementers. Most of the points
> in my proposal were discussed but I'm concerned that a lot of confusion
> remains.
>
> I have written a post that describes a Ruby design process and hopefully
> clarifies points that people found confusing:
>
> http://brixen.io/2012/12/11/a-ruby-design-process
>
> I would like to propose this process for making changes to Ruby. I am
> going to put a summary of the process at http://rubyspec.org/design and
> ask for people who support the process to submit their signature. I'd like
> to request that you consider the response from the community for my
> proposal.
>
> Thank you,
> Brian
>
>
>
> --
> http://bugs.ruby-lang.org/
>
>


-- 
NARUSE, Yui  <[e-mail]>