Hi, Python's simplicity allows programmers to focus on the job that they
originally set out to do (as opposed to getting side-tracked and
bogged-down by language overhead considerations). Very often a
procedure is challenging enough to work through without any unnecessary
overhead. Heck, I think it's safe to say that nobody needs overhead
added unnecessarily in any circumstance. BTW, there is the jython
language, which is exactly python with access to the jdk via python
syntax ... thereby making Java (appear as) a subset of Python (whereas
it's really an implementation of Python written in Java!). <br>
<br>As far as the teaching in general, I think introducing via procedural and motivating oop by example would be a good approach. <br><br>Best Regards,<br>Charles Cossé<br><br>(sorry for 2x emails Corey -- 1st one didn't cc edu-sig)<br>
<br><div class="gmail_quote">On Thu, Jul 14, 2011 at 9:20 PM, Corey Richardson <span dir="ltr"><<a href="mailto:kb1pkl@aim.com">kb1pkl@aim.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
I was discussing programing with some peers at an MIT summer program, and<br>
many of them came from the "JAVA AND OOP!" type of places to the point that,<br>
when the opportunity came up for them to learn the basics in a seminar, a<br>
few said "Pfff, but python sucks. It's too simple". Is it just me, or should<br>
simplicity be a Good Thing? </rant><br>
<br>
But, my real question to you educators is, which paradigm do you use when<br>
first teaching programming, and why? My peers cite OOP because, frankly,<br>
it's the only thing they've learned and have heard that e.g. procedural<br>
programming is bad. Personally, I like to use procedural (this is in<br>
Python, of course) for as long as possible. I don't even mention objects<br>
for a while, they aren't necessary or even desirable in many instances.<br>
I love using games as a project, and that's when I swoop in and bring up<br>
objects. My segue are usually the monsters of a text based game. I don't<br>
have them design an object for everything because it introduces complexity<br>
without benefit. Of course, it's not as flexible/correct a program as it<br>
could be, but it's a nice slow ease into OOP. But it certainly isn't the<br>
ONLY paradigm out there, and certainly not the most useful for everything.<br>
<br>
Any other insights?<br>
<font color="#888888">--<br>
Corey Richardson<br>
"Those who deny freedom to others, deserve it not for themselves"<br>
-- Abraham Lincoln<br>
</font><br>_______________________________________________<br>
Edu-sig mailing list<br>
<a href="mailto:Edu-sig@python.org">Edu-sig@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/edu-sig" target="_blank">http://mail.python.org/mailman/listinfo/edu-sig</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>AsymptopiaSoftware|Software@theLimit<br> <a href="http://www.asymptopia.org" target="_blank">http://www.asymptopia.org</a><br>