Re: GO vs Python

References	<CABRP1o8pG8rq3OHJPwZYPdmGbhqusUaNxapM9nn36gThYy4CLQ@mail.gmail.com> <CAOFF+Z0Tb+YJ-koEocQSQrcA-5n-15qKiSnJJgxwcOCQk+yFJw@mail.gmail.com> <CAPTjJmq3wPmBPVjW1Svfn0chNCORtTPgT=smXhazOp0p2X3-yg@mail.gmail.com> <CAOFF+Z1F0d8NDXBJPi7jHbGYMKzUcJT0KqZnqbLO4dys8oaB7w@mail.gmail.com>
Date	2014-08-25 13:41 +1000
Subject	Re: GO vs Python
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.13400.1408938102.18130.python-list@python.org> (permalink)

Show all headers | View raw

On Mon, Aug 25, 2014 at 1:27 PM, Sam Fourman Jr. <sfourman@gmail.com> wrote:
> I remember doing some browsing around, and the pooco people that make jinja2
> were not fans of python3(I forget the blog post), I got scared because a
> very large portion of my income was based on a single client... So since we
> were having scalability issues anyway, I moved them to GO, and it was a Win
> - Win, the GO standard lib does so much, and the scalability gains we
> received over python were so large, that we were able to reduce out AWS bill
> so much that I could hire another coder.

There are some communities that, for some reason or other, dislike
Python 3. That doesn't mean you have to. The Py2 model is a bit easier
for boundary code (it lets you stuff your fingers in your ears and go
"LALALALALA there are no character encodings"), but the Py3 model is
way easier for application code. Text is text, no matter what
characters it has in it.

> I really like python, and we use it a ton, but a python like compiled
> language did wonders for us when we needed it most.

Sure. And your reduction of AWS bills sounds great. Just make sure you
don't consume the entire extra coder's time doing things that Python
would have done for you. Go's character model is inferior to Python
3's (or at least, it was last time I checked - stuff might have
changed since then), so you may find yourself doing a lot of
unnecessary work to make sure your code works correctly. Do be sure to
test everything thoroughly, with characters from all over Unicode.

Personally, when I want "Python but faster", I go to Pike. Same
character/string model (even the same style of internal
representation), same broad object model, but a stronger focus on
networking and on staying running 100% of the time.

ChrisA

Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: GO vs Python Chris Angelico <rosuav@gmail.com> - 2014-08-25 13:41 +1000
  Re: GO vs Python Rustom Mody <rustompmody@gmail.com> - 2014-08-25 01:01 -0700
    Re: GO vs Python Marko Rauhamaa <marko@pacujo.net> - 2014-08-25 11:52 +0300
    Re: GO vs Python Chris Angelico <rosuav@gmail.com> - 2014-08-25 19:48 +1000
    Re: GO vs Python Roy Smith <roy@panix.com> - 2014-08-25 08:06 -0400
      Re: GO vs Python Rustom Mody <rustompmody@gmail.com> - 2014-08-25 05:24 -0700
        Re: GO vs Python Michael Torrie <torriem@gmail.com> - 2014-08-25 08:13 -0600
          Re: GO vs Python Marko Rauhamaa <marko@pacujo.net> - 2014-08-25 17:26 +0300
            Re: GO vs Python Rustom Mody <rustompmody@gmail.com> - 2014-08-25 07:38 -0700
              Re: GO vs Python Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2014-08-25 16:44 +0200
                Re: GO vs Python Marko Rauhamaa <marko@pacujo.net> - 2014-08-25 18:04 +0300
                Re: GO vs Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-08-25 17:40 +0100
        Re: GO vs Python Olaf Hering <olaf@aepfle.de> - 2014-08-25 16:32 +0200
        Re: GO vs Python Roy Smith <roy@panix.com> - 2014-08-25 21:21 -0400

csiph-web