openstack team mailing list archive

["Simon G." <semyazz@xxxxxxxxx>]

Hello,

I don't want to be rude, but fast research about point *3c* and sockets => PyPi
search<http://pypi.python.org/pypi?%3Aaction=search&term=socket.io&submit=search>

   - http://pypi.python.org/pypi/SocketTornad.IO/
   - http://pypi.python.org/pypi/TornadIO2/0.0.3 ,
   https://github.com/MrJoes/tornadio2
   - http://pypi.python.org/pypi/django-socketio/0.3.3
   - http://mrjoes.github.com/2011/12/15/sockjs-bench.html

How mature are those projects? I don't know. I'm not an expert in python.
I'm just trying to find alternatives to Node.js if almost everything is in
python. I'm just testing Openstack and right now I'm trying to add
something to nova, but I really like horizon and if it's possible, I'd like
to avoid node.js. I'm not a fan of this technology even if it's popular and
fast, because I just have some doubts about Javascript and its
maintainability.

Decision belongs to you guys who really develop this part of Openstack.

On Fri, May 25, 2012 at 12:27 PM, Gabriel Hurley
<Gabriel.Hurley@xxxxxxxxxx>wrote:

> (...)
>
>
> *3c.* Node.js vs. Ruby: Looking out later in this release cycle and into
> future cycles, there are capabilities that node.js can facilitate which
> Ruby (or Python for that matter) simply can't. Node.js has proven itself to
> be stupendously capable in terms of real-time communications and massive
> parallelism. Node libraries like socket.io are quickly becoming part of
> the permanent landscape on the web. So while it may seem silly to use
> node.js just for CSS management here, in the longer term we have the
> potential to leverage it immensely.
>
> 4. LESS for dev, commit compiled files: I veto'd this one in Horizon's
> discussions. I've played this game being a committer for Django when we
> tried to maintain both "development" and "production" versions of the
> admin's javascript files. It was a nightmare trying to do due diligence on
> contributions to make sure they were always in sync, etc. It's also an
> added burden on the developers to understand this process and always adhere
> to updating both files. All in all, not a scenario I support in any way
> shape or form.
>
> 5. Client-side LESS vs. server-side LESS: If it is determined to be an
> unreasonable burden to make node.js a hard requirement, I will admit we
> could potentially hack a way to make node.js VERY STRONGLY recommended but
> optional for those who simply will not/cannot install it. I, personally,
> would never deploy LESS's client-side compilation code since it's a
> significantly worse experience, but that's just me. That said, see point 3c
> for why we'll likely have this discussion again in the future...
>
> Finding the right balance is important here.
>
> All the best,
>
>    - Gabriel
>
>
>
> > -----Original Message-----
> > From: openstack-bounces+gabriel.hurley=nebula.com@xxxxxxxxxxxxxxxxxxx
> > [mailto:openstack-
> > bounces+gabriel.hurley=nebula.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> > Thierry Carrez
> > Sent: Friday, May 25, 2012 1:48 AM
> > To: openstack@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Openstack] Nodejs in horizon
> >
> > Devin Carlen wrote:
> > > -1 to introducing formal processes around this.  This will happen from
> > > time to time.  Development may be briefly impacted on other platforms
> > > but hindering innovation and telling developers that they are
> > > responsible for package availability across every distro is not
> healthy.
> >
> > The PPB actually already ruled that new dependencies *need* to be
> > discussed on the mailing-list prior to their introduction, if only so
> that
> > downstream stakeholders learn about it and can work to solve it.
> >
> > Like others said, new dependencies impact our whole ecosystem and most
> > of the time a small amount of discussion can go a long way in choosing a
> > solution that is good for everyone, rather than firefighting after the
> fact.
> >
> > You are not responsible for package availability across every distro, but
> > you're responsible for playing as nice with them as you can. That's the
> > "Facilitation of downstream distribution" obligation of core
> projects[1], an
> > obligation that the PPB can enforce.
> >
> > [1] http://wiki.openstack.org/ProjectTypes
> >
> > 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
>

*
*




-- 
*Semy*