Re: [Stellarlegacy-developer] Anyone out there?

[Satya <sl...@th...>]

On Wed, May 11, 2005 at 02:52:38PM +0100, Darren Winsper wrote:
>1) Perl is reasonably popular still, but mostly amongst hard-core types.
>It's not very accessible to newcomers and is rapidly being replaced by
>other high-level languages as "the scripting language to know."  I think
>it would be a really, really bad choice.

Why is accessibility to newcomers an issue? *No* language is accessible
to newcomers.

>2) Python is indeed getting quite popular.  I don't use it much myself,
>but I can understand why people do.

I don't think popularity should be the primary condition. The
capabilities and the core developers' familiarity should be the primary
conditions.

>3) Java was, IIRC, originally considered before we chose C++.  The
>concerns back then were the arguments that it's too slow, Swing is icky
>and a number of the coders wanted to use C++ anyway.  Well, it's not
>really that slow any more and there are other toolkits or binding to
>toolkits available.  However, Sun are gits.

I consider Java itself icky, but it seems to me that a lot of OO
languages are icky -- simply due to syntax and namespace issues.

>4) I'm going to get called all-sorts for this, but has anyone considered
>going with .Net/Mono?  .Net is the future of Windows and Mono is picking

Yup, you're going to get called all-sorts :-P

>up a lot of steam on non-Windows platforms.  Making client applications
>in .Net is quite a pleasant experience and it'll give us greater
>flexibility over what languages we choose to use for various things.
>For example, we could use IronPython as a scripting engine, satisfying
>your Python needs :)

You can pretty much count me out by going with .NET/Mono. I know that
doesn't anything much since no one here knows me (and so has no reason to
want me) anyway.

-- 
Satya. http://www.thesatya.com/
BREAKFAST.COM halted... cereal port not responding.