By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,996 Members | 1,536 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,996 IT Pros & Developers. It's quick & easy.

QOTW from Ryan Tomayko

P: n/a
http://naeblis.cx/rtomayko/2005/01/2...setters-fuxors

"...Many people coming to Python can't believe no one uses IDEs. The
automatic assumption is that Python is for old grey beards who are
comfortable with vi and Emacs and refuse to accept breakthroughs in
programming productivity like IDEs. Then they write a little Python code
and realize that an IDE would just get in their way."
FuManChu
Jul 18 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a

"Robert Brewer" <fu******@amor.org> wrote in message
news:ma**************************************@pyth on.org...
http://naeblis.cx/rtomayko/2005/01/2...setters-fuxors

"...Many people coming to Python can't believe no one uses IDEs. The
automatic assumption is that Python is for old grey beards who are
comfortable with vi and Emacs and refuse to accept breakthroughs in
programming productivity like IDEs. Then they write a little Python code
and realize that an IDE would just get in their way."

FuManChu

[response]

It's also not true. Lots of people use IDEs - look at the
number of Python IDEs out there, and the number of
attempts (some of them reasonable) to add Python
support to Eclipse.

The thing is, there are relatively fewer programming
tools needed to work with Python than there are
for Java, for example, so the available IDEs are much
simpler.

Line oriented editors are an acquired taste, and they
are one I've never acquired regardless of the environment.
I've used both edit under TSO and vi on a timesharing
arrangement with an AIX system, and both of them suck
compared to the screen editors available.

John Roth

Jul 18 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.