Page 1 of 2 12 LastLast
Results 1 to 10 of 36

Thread: Dropbox Announces Their Own Open-Source Python

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    15,193

    Default Dropbox Announces Their Own Open-Source Python

    Phoronix: Dropbox Announces Their Own Open-Source Python

    The Dropbox cloud storage provider has announced Pyston, their own open-source JIT compiler to Python. The big focus with Pyston is on speed...

    http://www.phoronix.com/vr.php?view=MTY1NDc

  2. #2
    Join Date
    Dec 2010
    Location
    MA, USA
    Posts
    1,403

    Default

    Very interesting. Unfortunately, they're only targeting python 2.7. For a brand new design, you'd think they'd use 3.x since the JIT compilers for that are either rare, outdated, or unstable. At this point, most python libraries that actually matter are already ported to 3.x. If things like Qt and pygame/SDL work with pyston, I'm definitely going to try it out.

  3. #3
    Join Date
    Nov 2012
    Location
    France
    Posts
    596

    Default

    I would like the same thing to happen to their daemons.

  4. #4
    Join Date
    Jan 2014
    Posts
    31

    Default

    Python is dying. Its being destroyed on all fronts from Javascript/Dart to Go/Ruby. The devs just killed their own language with the 2.7 to 3.0 screw-up. Dropbox isn't even supporting 3.0 yet the devs continue down this dual language version path. It's a complete disaster.

  5. #5
    Join Date
    Apr 2012
    Posts
    4

    Default people have tried to use llvm to optimize python already

    An intern at google tried that and it's called unladen swallow [1].

    it seems alot more promising to look into the openjdk world. Some people are working on truffle a specializing ast implementation.
    There is an experimental branch that implements this for python3 ([2]).

    Actually LLVM is a pretty bad JIT. Some people tried to make an OpenJDK backend that uses LLVM to make a plattform independent JIT called Shark. It was very slow ([3]).


    [1]: https://code.google.com/p/unladen-swallow/
    [2]: https://bitbucket.org/ssllab/zippy
    [3]: http://icedtea.classpath.org/wiki/ZeroSharkFaq

  6. #6
    Join Date
    Aug 2011
    Posts
    29

    Default

    Quote Originally Posted by [wrd] View Post
    An intern at google tried that and it's called unladen swallow [1].

    it seems alot more promising to look into the openjdk world. Some people are working on truffle a specializing ast implementation.
    There is an experimental branch that implements this for python3 ([2]).

    Actually LLVM is a pretty bad JIT. Some people tried to make an OpenJDK backend that uses LLVM to make a plattform independent JIT called Shark. It was very slow ([3]).


    [1]: https://code.google.com/p/unladen-swallow/
    [2]: https://bitbucket.org/ssllab/zippy
    [3]: http://icedtea.classpath.org/wiki/ZeroSharkFaq
    They've also tried to use LLVM for a JavaScript JIT and it was pretty bad.

  7. #7
    Join Date
    Dec 2010
    Location
    MA, USA
    Posts
    1,403

    Default

    Quote Originally Posted by litfan View Post
    Python is dying. Its being destroyed on all fronts from Javascript/Dart to Go/Ruby. The devs just killed their own language with the 2.7 to 3.0 screw-up. Dropbox isn't even supporting 3.0 yet the devs continue down this dual language version path. It's a complete disaster.
    You clearly have no idea how python works if you think any of those languages you mentioned are competing with it - you're comparing apples to oranges. Ruby is the only language that is similar in usage/purpose to python, and it is notably less popular. Also, the jump the 3.0 wasn't a bad idea. While breaking the compatibility was a little annoying, python supplies scripts to convert your code. I had a roughly 2500 line code that I converted from 2.7 to 3.3 by hand and it only took me an hour to do.

    People don't switch to python 3.x because if they didn't write their code for it, there's a good chance it's going to be a pain to convert. As long as people are actively using 2.7, it isn't going to die, and if it works for them and is still being maintained, I don't really see that as a problem.

  8. #8
    Join Date
    Jan 2014
    Posts
    31

    Default

    Quote Originally Posted by schmidtbag View Post
    You clearly have no idea how python works if you think any of those languages you mentioned are competing with it - you're comparing apples to oranges. Ruby is the only language that is similar in usage/purpose to python, and it is notably less popular. Also, the jump the 3.0 wasn't a bad idea. While breaking the compatibility was a little annoying, python supplies scripts to convert your code. I had a roughly 2500 line code that I converted from 2.7 to 3.3 by hand and it only took me an hour to do.

    People don't switch to python 3.x because if they didn't write their code for it, there's a good chance it's going to be a pain to convert. As long as people are actively using 2.7, it isn't going to die, and if it works for them and is still being maintained, I don't really see that as a problem.
    Bullshit. Google's Go directly competes with python on the web server side. Javascript is directly competing with Python for server apps now too. Virtually every company I work with is switching away from Django to node.js and other options.

    You're the clueless one if you think Python has any chance int he next 5 years to remain relevant.

  9. #9
    Join Date
    Oct 2013
    Posts
    71

    Default

    Quote Originally Posted by schmidtbag View Post
    You clearly have no idea how python works if you think any of those languages you mentioned are competing with it - you're comparing apples to oranges. Ruby is the only language that is similar in usage/purpose to python, and it is notably less popular. Also, the jump the 3.0 wasn't a bad idea. While breaking the compatibility was a little annoying, python supplies scripts to convert your code. I had a roughly 2500 line code that I converted from 2.7 to 3.3 by hand and it only took me an hour to do.

    People don't switch to python 3.x because if they didn't write their code for it, there's a good chance it's going to be a pain to convert. As long as people are actively using 2.7, it isn't going to die, and if it works for them and is still being maintained, I don't really see that as a problem.
    Please consider the option of NOT responding to trolls. Any kind of rational response will just add fuel to the fire. If you ignore them they will eventually get bored and go away.

  10. #10
    Join Date
    Feb 2011
    Posts
    1,264

    Default

    Quote Originally Posted by litfan View Post
    Python is dying. Its being destroyed on all fronts from Javascript/Dart to Go/Ruby. The devs just killed their own language with the 2.7 to 3.0 screw-up. Dropbox isn't even supporting 3.0 yet the devs continue down this dual language version path. It's a complete disaster.
    I can't speak on the web server front, but on the scientific computing side there is no open-source language remotely in the same ballpark (the only thing close to it is Matlab, and Matlab is the one dying there).

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •