| From | Sent On | Attachments |
|---|---|---|
| Joshua Harlow | May 24, 2012 10:33 am | |
| Chuck Short | May 24, 2012 12:26 pm | |
| Joshua Harlow | May 24, 2012 12:31 pm | |
| Devin Carlen | May 24, 2012 12:40 pm | |
| Gabriel Hurley | May 24, 2012 12:42 pm | |
| Joshua Harlow | May 24, 2012 12:47 pm | |
| Gabriel Hurley | May 24, 2012 1:42 pm | |
| Joshua Harlow | May 24, 2012 1:45 pm | |
| Gabriel Hurley | May 24, 2012 1:48 pm | |
| Russell Bryant | May 24, 2012 3:37 pm | |
| Joshua Harlow | May 24, 2012 4:08 pm | |
| Devin Carlen | May 24, 2012 4:22 pm | |
| Joshua Harlow | May 24, 2012 4:27 pm | |
| Russell Bryant | May 24, 2012 4:42 pm | |
| Gabriel Hurley | May 24, 2012 5:45 pm | |
| Mark McLoughlin | May 25, 2012 12:53 am | |
| Thierry Carrez | May 25, 2012 1:47 am | |
| Thierry Carrez | May 25, 2012 2:04 am | |
| Simon G. | May 25, 2012 2:43 am | |
| Gabriel Hurley | May 25, 2012 3:26 am | |
| Russell Bryant | May 25, 2012 4:33 am | |
| Simon G. | May 25, 2012 5:40 am | |
| Jay Pipes | May 25, 2012 6:20 am | |
| Simon G. | May 25, 2012 7:39 am | |
| Thierry Carrez | May 25, 2012 7:51 am | |
| Thierry Carrez | May 25, 2012 8:09 am | |
| John Postlethwait | May 25, 2012 9:22 am | |
| Gabriel Hurley | May 25, 2012 10:53 am | |
| Kiall Mac Innes | May 25, 2012 11:41 am | |
| Gabriel Hurley | May 25, 2012 12:35 pm | |
| Russell Bryant | May 25, 2012 1:19 pm | |
| Gabriel Hurley | May 25, 2012 1:51 pm | |
| Russell Bryant | May 25, 2012 2:32 pm | |
| Adam Young | May 25, 2012 3:56 pm | |
| Gabriel Hurley | May 25, 2012 4:15 pm | |
| Adam Young | May 25, 2012 5:33 pm | |
| Gabriel Hurley | May 26, 2012 7:57 pm | |
| Thierry Carrez | May 28, 2012 7:20 am | |
| Matthias Runge | May 29, 2012 12:58 am | |
| Gabriel Hurley | May 29, 2012 9:29 am | |
| Adam Young | May 29, 2012 10:26 am | |
| Martin Paulo | May 29, 2012 9:18 pm | |
| Devin Carlen | May 30, 2012 1:36 pm | |
| Adam Young | May 30, 2012 2:14 pm | |
| Jan Drake | May 30, 2012 4:27 pm | |
| Gabriel Hurley | May 30, 2012 4:44 pm | |
| Caitlin Bestler | May 31, 2012 10:31 am | |
| Jan Drake | May 31, 2012 7:24 pm |
| Subject: | Re: [Openstack] Nodejs in horizon | |
|---|---|---|
| From: | Jan Drake (jan_...@hotmail.com) | |
| Date: | May 31, 2012 7:24:50 pm | |
| List: | net.launchpad.lists.openstack | |
I was speaking generally not specifically about this issue. Sounds like you're
taking this personally.
See prior comment on developers and languages. This is not about which language
is better: that's just crazy talk. :)
Adding node.js is clearly not onerous. And if most shops don't have JS
experience on staff I imagine interfaces and UX must be pretty sterile and
difficult to create so I think JS isn't an onerous skill to expect the community
to be able to bring to bear.
As I mentioned below I am not in favor of willy nilly addition of technology
solutions. Just warning the community to be aware about RTW and NIH and to use
as much leverage as possible to accelerate the delivery of the platform.
You see, I'm a customer. Give me the best product possible. I'll put up with
one more dependency in my deployment process. I already have thousands of them.
Jan
On May 31, 2012, at 10:32 AM, Caitlin Bestler <Cait...@nexenta.com>
wrote:
Jan Drake wrote:
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 limite
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).
If we were launching the project from scratch and the question was which
language would be better, node.js or python, I would
Strongly advocate node.js.
However, I do not think there is anything "myopic" about wanting to limit the
dependencies that the host OS must provide
to support your project, or the amount of learning that is required before a
team of developers can be proficient with the
code base for a project.
Once a second major ecosystem is introduced, whether node.js or just a different
python threading library, all of the release
decisions become more complex from that day forward. It is not just when to
support a new version of the python libraries,
but which python *and* node.js libraries will be supported in the next project
release. That extra release work must be undertaken
by each OS distribution that supports openstack.
Any shift in the ecosystem will be a major undertaking, it should only be
considered when the costs of not doing it become onerous.
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : open...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp





