I think it would be good to limit the number of languages used for WebKit
development. We already have important tools that use all of Perl, Python and
Ruby. To date, we've been gradually converging on new scripts being mostly in
Python. I think it would be really valuable for the project. Even
All other things being equal, I'd prefer to keep things in Python
since there are a lot more people that can support that than Go. But
if there are some real benefits to Go, I don't have any real
objection.
-- Dirk
On Wed, Dec 7, 2011 at 3:39 PM, Ojan Vafai wrote:
> Anyone have objections to me
I initially started this hoping to address some of the memory problems in
the Python app. It turned out not to fix them in the end, but the new
codebase is better written, much more thoroughly tested and likely more
performant, so I'm inclined to keep it. As for Go vs. Python specifics, I
have opin
Can you comment why you think that Go would be the right tool for the job here,
as opposed to Python, Perl, Ruby, or something else? I'm just curious, since I
have not used Go. :-)
-Filip
On Dec 7, 2011, at 3:39 PM, Ojan Vafai wrote:
> Anyone have objections to me using Go for the test resu
Anyone have objections to me using Go for the test results server rewrite?
I don't have any intention of using Go in other places in WebKit. There's a
few reasons this seems fine to me:
1. You already need to get the appengine SDK to interact with the test
results server, so getting the Go appengin
5 matches
Mail list logo
