openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #00885
Re: Queue Service, next steps
It's been discussed a fair amount already, but I think this is a good list of pros for erlang:
- less code to do the same thing (dramatically less in a lot of cases)
- more robust development environment (far fewer sharp edges in erlang compared to c++)
- this is exactly the type of project where erlang shines
- lends itself towards more hands in the source code pie since there are fewer correct ways to do things in erlang
Both are good choices but erlang has gained a ton of momentum in recent years for the reasons listed above.
Personally I'd love to see us choose erlang for this project. I think it's a great fit.
- Devin
On Feb 21, 2011, at 10:51 PM, Eric Day wrote:
> While Erlang is a dependency most folks usually don't have installed
> by default, it is a fairly simple and predictable dependency. All
> major distros have it, and if they don't or are too outdated, the
> packages from the Erlang website are straightforward to install.
>
> Any dependency (C/C++ compilers, autotools, Erlang) will always have
> its quirks, but I think either choice would be fine in the long run.
>
> The advantages for choosing Erlang right now are speed of development,
> code safety, and trivial multi-core/machine use. The advantages for
> C++ are runtime efficiency and familiarity. I'm pretty split and don't
> think there is an incorrect choice here, but it feels like more folks
> are leaning towards C++.
>
> -Eric
>
> On Mon, Feb 21, 2011 at 02:47:21PM -0600, John Purrier wrote:
>> I agree with this. Unless there are significant, obvious advantages to
>> Erlang I would suggest we stick with C/C++.
>>
>> John
>>
>> -----Original Message-----
>> From: openstack-bounces+john=openstack.org@xxxxxxxxxxxxxxxxxxx
>> [mailto:openstack-bounces+john=openstack.org@xxxxxxxxxxxxxxxxxxx] On Behalf
>> Of Tim Bell
>> Sent: Monday, February 21, 2011 2:08 PM
>> To: Eric Day; openstack@xxxxxxxxxxxxxxxxxxx
>> Subject: Re: [Openstack] Queue Service, next steps
>>
>>
>> Please bear in mind the long term maintainability of the openstack package.
>> One of the attractive features at the moment is that there are not
>> significant pre-reqs to set up the environment and most mass market
>> environments can support it.
>>
>> Using C++ would not significantly change this situation, whereas using
>> Erlang may create some more difficulty further down the line. Anything that
>> makes porting/rebuilding more difficult needs to be carefully thought
>> through.
>>
>> Tim Bell
>> CERN
>>
>>
>> _______________________________________________
>> 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
-
Re: Queue Service, next steps
From: Chris Behrens, 2011-02-21
-
Re: Queue Service, next steps
From: Eric Day, 2011-02-21
-
Re: Queue Service, next steps
From: Tim Bell, 2011-02-21
-
Re: Queue Service, next steps
From: John Purrier, 2011-02-21
-
Re: Queue Service, next steps
From: Eric Day, 2011-02-22