Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

merlyn (47)

merlyn
  merlyn@stonehenge.com
http://www.stonehenge.com/merlyn/
AOL IM: realmerlyn (Add Buddy, Send Message)
Yahoo! ID: realmerlyn (Add User, Send Message)

PAUSE-ID: MERLYN [cpan.org].
See my home page [stonehenge.com].

Journal of merlyn (47)

Tuesday June 05, 2007
06:37 PM

Perl to Python

[ #33438 ]

"Our team has been spearheading the transition from Perl to Python at the facility", says Grant. "There are three primary reasons for this. The creation of Python bindings to a C++ library is very easy and allows us to utilize core R&D libraries in the rest of the pipeline more quickly. The object-oriented nature of Python is very attractive given our new asset model and should allow us to make changes to that asset model much more easily in the future. And, Python is a first-class citizen in many of the third-party software applications that are used in our industry."

from DreamWorks Animation "Shrek the Third": Linux Feeds an Ogre

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • If that quotation is re-written reversing Perl and Python, is it just as true? If so, it does not give any meaningful reason for switching from Perl to Python...
  • 'We chose to transition our application from Technology Y to Technology X primary for it's superior meta attribute handling. Technology X has been shown to be better and more effective in programming teams for the standard new model of development. Additionally, most blogs now tout the superior productivity of Technology X programmers, and Technology X application users. "Above all, Technology X provides us with end results that are on average upwards of 50% more shiny than Technology Y given the same pr

    • Sorry for my cynical comment here - had a bad coding day today and took the third class citizen thing personally :-)

  • ... the one point I would concede is that because Python is easy to embed, it may well be easier to integrate into some of those weird film animation programs.

    While I don't know specifics, if their choices came down the raw c, python and say javascript, I'd probably pick Python too.
    • I’d go for Javascript…

      • I wouldn't. JavaScript is ok for a light dusting of scripting over the top of something, but it makes for a hideous language to get any real work done in.
        • Really? I was quite delighted to find out how nice it really is when I dove into it in anger a few years ago. To me it feels like a cross of Perl and “something” (which I guess I’d know was Self, if I knew Self), trying to hide behind a C/Java-ish syntax.

          At least it has multiline/-statement closures…

    • Like they said, accessing their C++ libraries is a lot easier in Python. While I'm not familiar with doing that in Python, I'm sure it can't suck as much as in Perl. Or is there some other reason that there are oftentimes no Perl bindings (or ancient and badly supported) for a particular C/C++ library, whereas there are for Python. Is it just that Python is more popular, or that Python as a language matches up better with C++, and nothing to do with the suckiness of XS?

      I wonder myself why they don't use L [wikipedia.org]

      • Lua is minimalist. Even though it looks like a wonderful technology for embedded scripting engines, it doesn't have a history of many mature and varied libraries to get you up quickly. It seems like the people at game programming get over it because they really just need the scripting engine and all else is hand-rolled with the game. I don't know if that's the same for film industry.
  • I remember seeing a Perl job posting at DreamWorks [perl.org]. I thought that would be a sweet job, if only I had computer animation experience. Now it looks like it would be more of a legacy-app maintenance job...