The Zen of Python
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
Many Pythonistas actually believe that choice can be a bad thing, and they only need to point at the billion Java frameworks of very different quality, but all written to serve the same purpose, to underline their argument.
As for Noel's statement about many programmers --here-- having little skill: You would be really surprised how little skill you will find out there in the "real world" of "professional" programming. Around 4 million Java developers expect their IDE to do all the coding for them, because they are actually incapable of coding anything themselves, and they would certainly be completely lost without Eclipse or Netbeans.
But they are in good company - the typical C# and Visual Basic developers are no different, and probably most C++ application developers are also in that boat. The COBOL guys might still know what they're doing, but that is because mainframes don't have IDEs. (No, ISPF is not an IDE.)
And for all the things that are not bundled with their IDE of choice, "professional developers" just buy additional libraries and click their app together. Or does anybody actually believe that all those well paid Java programmers really read and fully understand all that horrible code that Netbeans' GUI builder creates for them? Visual Studio is not any better.
Which leads to the theory that IDEs make developers dumber; even Charles "Programming Windows" Petzold believes this:
http://charlespetzold.com/etc/DoesVisualStudioRotTheMind.html
So you might be better off NOT asking for a better IDE. MaxIDE does the job quite well. Only the documentation sucks.
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
Many Pythonistas actually believe that choice can be a bad thing, and they only need to point at the billion Java frameworks of very different quality, but all written to serve the same purpose, to underline their argument.
As for Noel's statement about many programmers --here-- having little skill: You would be really surprised how little skill you will find out there in the "real world" of "professional" programming. Around 4 million Java developers expect their IDE to do all the coding for them, because they are actually incapable of coding anything themselves, and they would certainly be completely lost without Eclipse or Netbeans.
But they are in good company - the typical C# and Visual Basic developers are no different, and probably most C++ application developers are also in that boat. The COBOL guys might still know what they're doing, but that is because mainframes don't have IDEs. (No, ISPF is not an IDE.)
And for all the things that are not bundled with their IDE of choice, "professional developers" just buy additional libraries and click their app together. Or does anybody actually believe that all those well paid Java programmers really read and fully understand all that horrible code that Netbeans' GUI builder creates for them? Visual Studio is not any better.
Which leads to the theory that IDEs make developers dumber; even Charles "Programming Windows" Petzold believes this:
http://charlespetzold.com/etc/DoesVisualStudioRotTheMind.html
So you might be better off NOT asking for a better IDE. MaxIDE does the job quite well. Only the documentation sucks.