Coding Fun
Aug. 7th, 2010 07:27 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
I've spent the afternoon playing a bit more with Google App Engine/Python.
So far it's ok - the language is simple enough, and I can make it do the bits and pieces I want so far. The main thing I miss is static typing and intellisense - everything takes so long when I have to keep looking up help files rather than having intellisense present me with a list of useful options, and the lack of type mismatch checking means finding type mismatch bugs at compile time, which seems pretty silly.
I'm also baffled as to why there's both a datetime type and a struct_time type. You'd think that something as basic as date/time representation would be baked in...
So far it's ok - the language is simple enough, and I can make it do the bits and pieces I want so far. The main thing I miss is static typing and intellisense - everything takes so long when I have to keep looking up help files rather than having intellisense present me with a list of useful options, and the lack of type mismatch checking means finding type mismatch bugs at compile time, which seems pretty silly.
I'm also baffled as to why there's both a datetime type and a struct_time type. You'd think that something as basic as date/time representation would be baked in...
no subject
Date: 2010-08-07 06:59 pm (UTC)no subject
Date: 2010-08-07 07:57 pm (UTC)no subject
Date: 2010-08-07 08:08 pm (UTC)IME you rarely if ever have to use the time module and should always use datetimes, especially in a high-level environment like App Engine.
no subject
Date: 2010-08-07 08:12 pm (UTC)The reason I bumped into it is that the Feed Parser code produces the struct_time, while the other code I was using was clearly newer.
no subject
Date: 2010-08-09 04:58 pm (UTC)You're welcome!
Coding Fun
Date: 2010-08-08 07:49 am (UTC)Re: Coding Fun
Date: 2010-08-08 03:51 pm (UTC)