openstack team mailing list archive

[Jan Drake <jan_drake@xxxxxxxxxxx>]

For what it's worth, I've noticed a generally myopic trend towards python only.  Node.js can play many very good roles as an implementation strategy for various openstack capabilities, especially at the edge.  I was excited to see it being included.  There's a balance to be struck in optimizing the development community, especially for core openstack, around a limited set of languages; however, I've never trusted an engineer who's ever only coded (or still only codes) in one language.

So, consider this a nudge in the direction of being open to additional technology sets and languages (not blindly randomly or chaotically).

Also, it might be good practice to declare, when offering an opinion, whether or not one has experience with the stack in question.  I do.  Node.js can be very useful.

Different != bad.
Stupid = bad.
If different = stupid then different = bad.

I'm starting to see NIH (not invented here) and RTW (Reinventing the wheel)  perhaps in areas that it isn't necessary.

Pot stirred,


Jan

P.S.  It is this perceived myopia that is primarily the reason I didnt open source our oauth and api mgmt solutions to the community.  I was told:  language not allowed.  Um Okay but then you probably wouldn't have had to rewrite keystone.  

On May 30, 2012, at 1:37 PM, Devin Carlen <devin@xxxxxxxxxxxxx> wrote:

> Long story short - we will work to make node.js an optional build time component and leave it as an distro packaging issue.  node.js was being evaluated as a potential solution to https://blueprints.launchpad.net/horizon/+spec/realtime-communication, but that blueprint isn't targeted for Folsom, so it's very future.  We'll have a lot of time to evaluate python based alternatives.
> 
> 
> Devin
> 
> 
> On May 29, 2012, at 10:26 AM, Adam Young wrote:
> 
>> On 05/29/2012 12:29 PM, Gabriel Hurley wrote:
>>> Without rehashing backstory which is available in public archives of this thread, while node is currently on the table for LESS it also may play a role
>>> in future needs as well.
>>> 
>>> As for your link, yes there are LESS compilers in other languages (there's even a nascent one in Python that's very much not ready for prime time) but requiring PHP or any other language besides Python opens a similar can of worms, and PHP gets us nowhere on any other fronts.
>>> 
>>> /me refrains from any other comments about PHP.
>>> 
>>> Moreover, the canonical LESS compiler which is the best supported and most stable is the main one written for node.js. Unless there were a 100% working Python version I see no reason not to favor the "real" LESS compiler.
>>> 
>>> All the best,
>> 
>> For LESS,  it think it is fine to use even server side Javascript.  The CSS should be compiled at RPM/DEB build time, and not at run time for live deployments,  so that is a bit of a non-issue.  I'd also be fine with using the client side LESS implementation, especially if we want to use the same implementation at development and live deployment time,  but I can understand if there are issues with doing this.
>> 
>> 
>> Node.js is a whole different server side technology,  and that should not be implemented at this time.
>> 
>> 
>>> 
>>>    - Gabriel
>>> 
>>> On May 29, 2012, at 1:00 AM, "Matthias Runge"<mrunge@xxxxxxxxxxxxxxxxx>  wrote:
>>> 
>>>> On 28/05/12 16:21, Thierry Carrez wrote:
>>>>> John Postlethwait wrote:
>>>>>> Sorry if I've missed anything below, this thread has become rather
>>>>>> fragmented and messy (at least in my email clients) but I will try to
>>>>>> address the main points I have seen so far:
>>>> Sorry, if I jump in late in this thread, I may have skipped some basics.
>>>> If I get it right, nodejs is just required to compile LESS to css, right?
>>>> 
>>>> There is at least one alternative without requiring nodejs:
>>>> 
>>>> https://github.com/leafo/lessphp
>>>> -- 
>>>> Matthias Runge<mrunge@xxxxxxxxxxxxxxxxx>
>>>> 
>>>> _______________________________________________
>>>> 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
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>