openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #00864
Re: Queue Service, next steps
I guess that's what I'm trying to say for this project. My opinion would be to stick with what we know. :)
Do we have enough Erlang knowledge right now? I would not want to see Eric get burned out because he can't get help. I've seen it happen before when Erlang was chosen and the project ended up a complete failure.
I'd like to learn Erlang better. But, I wouldn't to be able to help significantly any time soon... or at least not where I could contribute the quality of code that this project needs. It feels like I've seen a lot of similar replies.
- Chris
On Feb 21, 2011, at 9:27 AM, Jay Pipes wrote:
> For the record, I said I'd prefer C++ because that's what I know, but
> I wouldn't *mind* learning Erlang ;)
>
> -jay
>
> On Mon, Feb 21, 2011 at 8:34 AM, Chris Behrens
> <chris.behrens@xxxxxxxxxxxxx> wrote:
>> I am very concerned about seeing a lot of "I'd love to learn Erlang" on something we probably don't want to screw up. At the same time, I know there's a number of us very experienced with C/C++ (even with respect to concurrency/scalability).
>>
>> - Chris
>>
>>
>> On Feb 21, 2011, at 2:40 AM, Thierry Carrez wrote:
>>
>>> Quick comment on the languages from a dev community perspective:
>>>
>>> The Nova/Swift community is Python-based, so you won't directly reuse
>>> it, whether you use C++ or Erlang. For new contributors, you either
>>> target very experienced C++ developers (to get concurrency/scalability
>>> right), or moderately-experienced Erlang devs. Both probably come in
>>> short supplies... but you might find more people willing to learn Erlang
>>> than people willing to perfect their C++ skills (me for example).
>>>
>>> I've a slight preference for Erlang because it will probably be more
>>> difficult to do it wrong, and my gut feeling is that Python devs might
>>> be more convertible to Erlang than to C++.
>>>
>>> Regards,
>>>
>>> --
>>> Thierry Carrez (ttx)
>>> Release Manager, OpenStack
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help : https://help.launchpad.net/ListHelp
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
>>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
Follow ups
References
-
Queue Service, next steps
From: Eric Day, 2011-02-17
-
Re: Queue Service, next steps
From: Brian Lamar, 2011-02-18
-
Re: Queue Service, next steps
From: Eric Day, 2011-02-18
-
Re: Queue Service, next steps
From: Thierry Carrez, 2011-02-21
-
Re: Queue Service, next steps
From: Chris Behrens, 2011-02-21
-
Re: Queue Service, next steps
From: Jay Pipes, 2011-02-21