× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On Mon, Jul 6, 2015 at 12:08 PM Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 7/6/2015 11:51 AM, Jon Paris wrote:
Not sure I understand the logic on the “good fit” front.

The biggest challenge for most RPGers making the switch is generally the
OO aspect. That’s is why PHP has worked for many - because you can write
procedurally while exploiting objects written by others. Admittedly I have
not (yet) studied Python in depth, but everything I have seen to date tells
me that it is even more strongly OO than Java.

As one who struggles with the OO mindset, I do agree with this! Having
said that, the Python I write is quite procedural.


And you can write purely procedural python. Java requires you write one
class. Even if you use a library that uses classes, you can pretend the
class.member notation is some weird namespace thing, and not think too much
about it.


I’m interested as to why you two think it works better than (say) Java.

Java has these 3 issues that Python hasn't got:
CLASSPATH
Edit / compile / jar / deploy (vs interpreted)
Hierarchical folder structure (demands IDE vs simple text editor)

This exactly, Java makes a lot of assumptions that are hard to wrap your
head around if you are an RPG programmer. There's a little less pain in
python. Just stick all the files in the same folder, and import foo to get
all the stuff in foo.py. You can get fancy with subdirectories, objects,
etc, but you can "level yourself up" to those features at your own pace.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.