New to Python
Hi,
I've just started to toy with Python, because I like learning new (to me) programming languages.
However, so far I think it's horrible, because "Everything is an Object" and all the press around that, about how it's an object oriented scripting language. So far I'm dissapointed and disgusted (maybe too strong that) with the OO that I've found.
I'm reading through Dive Into Python, firstly, it seems to be possible to create procedural applications in this "everything is an object" language, i.e. I can create a module that just contains function defs, and a module that imports a bunch of modules like that and has a "main" method a la C. Which seems to be a bad thing to be able to do in a supposedly OO environment. This permits (and thus encourages if you listen to the people who critisize PHP etc for the exact same thing...) sloppy non-OO code in the OO language. Is this symptomatic of the rest of the language design? Am I going to find that other things are just as "wrong" or flakey. Or whatever the right way of describing this breach of principles?
Further on I find that the Dictionary data type is an object, which has methods to add, push and pop etc, but, to delete an item I have to pass the dictionary, with key specified to an external method that isn't attached to an object? Can this really be true? This is so not OO that it renders the "Everything is an Object" and "Python is an object oriented language" stuff totally fictional. How many more breaches of principle and sloppy design issues am I going to find? Is Python really as bad as it seems after just an hours reading?
Cheers,
Mike
I've just started to toy with Python, because I like learning new (to me) programming languages.
However, so far I think it's horrible, because "Everything is an Object" and all the press around that, about how it's an object oriented scripting language. So far I'm dissapointed and disgusted (maybe too strong that) with the OO that I've found.
I'm reading through Dive Into Python, firstly, it seems to be possible to create procedural applications in this "everything is an object" language, i.e. I can create a module that just contains function defs, and a module that imports a bunch of modules like that and has a "main" method a la C. Which seems to be a bad thing to be able to do in a supposedly OO environment. This permits (and thus encourages if you listen to the people who critisize PHP etc for the exact same thing...) sloppy non-OO code in the OO language. Is this symptomatic of the rest of the language design? Am I going to find that other things are just as "wrong" or flakey. Or whatever the right way of describing this breach of principles?
Further on I find that the Dictionary data type is an object, which has methods to add, push and pop etc, but, to delete an item I have to pass the dictionary, with key specified to an external method that isn't attached to an object? Can this really be true? This is so not OO that it renders the "Everything is an Object" and "Python is an object oriented language" stuff totally fictional. How many more breaches of principle and sloppy design issues am I going to find? Is Python really as bad as it seems after just an hours reading?
Cheers,
Mike
