Re: [openstack-dev] Reasoning behind my vote on the Go topic

2016-06-09 Thread Clint Byrum
Excerpts from Michael Barton's message of 2016-06-09 15:59:24 -0500: > On Thu, Jun 9, 2016 at 2:49 PM, Clint Byrum wrote: > > > > Agreed it isn't done in uvloop. But it is done in libuv and the uvloop > > devs agree it should be done. So this is the kind of thing where the > > community can invest

Re: [openstack-dev] Reasoning behind my vote on the Go topic

2016-06-09 Thread Michael Barton
On Thu, Jun 9, 2016 at 2:49 PM, Clint Byrum wrote: > > Agreed it isn't done in uvloop. But it is done in libuv and the uvloop > devs agree it should be done. So this is the kind of thing where the > community can invest in python + C to help solve problems thought only > solvable by other language

Re: [openstack-dev] Reasoning behind my vote on the Go topic

2016-06-09 Thread Clint Byrum
Excerpts from Michael Barton's message of 2016-06-09 14:01:11 -0500: > On Thu, Jun 9, 2016 at 9:58 AM, Ben Meyer wrote: > > > > > uvloop (first commit 2015-11-01) is newer than Swift's hummingbird > > (2015-04-20, based on > > > > https://github.com/openstack/swift/commit/a0e300df180f7f4ca64fc1ea

Re: [openstack-dev] Reasoning behind my vote on the Go topic

2016-06-09 Thread Michael Barton
On Thu, Jun 9, 2016 at 9:58 AM, Ben Meyer wrote: > > uvloop (first commit 2015-11-01) is newer than Swift's hummingbird > (2015-04-20, based on > > https://github.com/openstack/swift/commit/a0e300df180f7f4ca64fc1eaf3601a1a73fc68cb > and github network graph) so it would not have been part of the

Re: [openstack-dev] Reasoning behind my vote on the Go topic

2016-06-09 Thread Ben Meyer
On 06/08/2016 11:05 PM, Chris Friesen wrote: > On 06/07/2016 04:26 PM, Ben Meyer wrote: >> On 06/07/2016 06:09 PM, Samuel Merritt wrote: >>> On 6/7/16 12:00 PM, Monty Taylor wrote: [snip] I'd rather see us focus energy on Python3, asyncio and its pluggable event loops. The work

Re: [openstack-dev] Reasoning behind my vote on the Go topic

2016-06-08 Thread Chris Friesen
On 06/07/2016 04:26 PM, Ben Meyer wrote: On 06/07/2016 06:09 PM, Samuel Merritt wrote: On 6/7/16 12:00 PM, Monty Taylor wrote: [snip] I'd rather see us focus energy on Python3, asyncio and its pluggable event loops. The work in: http://magic.io/blog/uvloop-blazing-fast-python-networking/ is

Re: [openstack-dev] Reasoning behind my vote on the Go topic

2016-06-08 Thread Gregory Haynes
On Wed, Jun 8, 2016, at 03:46 AM, Thierry Carrez wrote: > Another option (raised by dims) is to find a way to allow usage of > golang (or another language) in a more granular way: selectively allow > projects which really need another tool to use it. The benefit is that > it lets project teams m

Re: [openstack-dev] Reasoning behind my vote on the Go topic

2016-06-08 Thread Thierry Carrez
Samuel Merritt wrote: On 6/7/16 12:00 PM, Monty Taylor wrote: [snip] > I'd rather see us focus energy on Python3, asyncio and its pluggable event loops. The work in: http://magic.io/blog/uvloop-blazing-fast-python-networking/ is a great indication in an actual apples-to-apples comparison of

Re: [openstack-dev] Reasoning behind my vote on the Go topic

2016-06-07 Thread Jim Baker
On Tue, Jun 7, 2016 at 4:26 PM, Ben Meyer wrote: > On 06/07/2016 06:09 PM, Samuel Merritt wrote: > > On 6/7/16 12:00 PM, Monty Taylor wrote: > >> [snip] > > > > >> I'd rather see us focus energy on Python3, asyncio and its pluggable > >> event loops. The work in: > >> > >> http://magic.io/blog/uv

Re: [openstack-dev] Reasoning behind my vote on the Go topic

2016-06-07 Thread Ben Meyer
On 06/07/2016 06:09 PM, Samuel Merritt wrote: > On 6/7/16 12:00 PM, Monty Taylor wrote: >> [snip] > > >> I'd rather see us focus energy on Python3, asyncio and its pluggable >> event loops. The work in: >> >> http://magic.io/blog/uvloop-blazing-fast-python-networking/ >> >> is a great indication in

Re: [openstack-dev] Reasoning behind my vote on the Go topic

2016-06-07 Thread Samuel Merritt
On 6/7/16 12:00 PM, Monty Taylor wrote: [snip] > I'd rather see us focus energy on Python3, asyncio and its pluggable event loops. The work in: http://magic.io/blog/uvloop-blazing-fast-python-networking/ is a great indication in an actual apples-to-apples comparison of what can be accomplishe

Re: [openstack-dev] Reasoning behind my vote on the Go topic

2016-06-07 Thread James Penick
>rather than making progress on OpenStack, we'll spend the next 4 years bikeshedding broadly about which bits, if any, should be rewritten in Go. 100% agreed, and well said. On Tue, Jun 7, 2016 at 12:00 PM, Monty Taylor wrote: > This text is in my vote, but as I'm sure there are people who do

Re: [openstack-dev] Reasoning behind my vote on the Go topic

2016-06-07 Thread Amrith Kumar
Well put Monty. It is a tough choice and neither choice was inexpensive. -amrith > -Original Message- > From: Monty Taylor [mailto:mord...@inaugust.com] > Sent: Tuesday, June 07, 2016 3:00 PM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: [openstack-dev]

Re: [openstack-dev] Reasoning behind my vote on the Go topic

2016-06-07 Thread Jay Pipes
Well said and reasoned, Monty. On 06/07/2016 03:00 PM, Monty Taylor wrote: This text is in my vote, but as I'm sure there are people who do not read all of the gerrit comments for governance changes, I'm posting it here so that my thoughts are clear. Please know that this has actually kept me u