Monday, January 31, 2011

Python blows, why do people use it?


At work, its no secret we use python and C++. The python is used to do stuff like guide the initialization of the game, and set up things, like graphics.

The python advocates claim the following:
  • Its script! Just change it and you can see things right away, its great!
  • Type safe coding is sooo 20th century.
  • Compilers are lame.
  • No large projects are written in C++ any more.
Heres what really happens:

I get the C++ code to compile, then I have to make another stop in python code to write the 'glue'.
If the C++ code crashes, I can attach a debugger, this might be because the python is all jacked up.
The python code may not 'compile', which is a runtime step... It might even not compile 'later', or it throws an error after 5 minutes of running the game/app. Then guess what, I'm screwed. There is no reloading of that script.
How would I debug python? There is no debugger for it. I'm back to putting in print statements.

It's like I've stepped back in time to 1983, and BASIC.

Then there is the whole "white space defines scope', which turns out to cause no end of trouble. It basically feeds back into the "Oh, you ain't done until the code is executed"

Also, being one of these languages where everything is an object and dynamically mutable, there is no IDE that can provide any help for me, like auto-complete. Working on a large python project is a nightmare.

I cringe every time I have to delve into the python code. Hopefully that will be less and less as time goes on.


No comments:

Post a Comment