Re: [scala-user] Scala viability for large scale projects (was Re: Why does scala have "new"?)

View: New views
1 Messages — Rating Filter:   Alert me  

Parent Message unknown Re: [scala-user] Scala viability for large scale projects (was Re: Why does scala have "new"?)

by Erik Engbrecht :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Please move to debate.  This is a worthwhile conversation but shouldn't clog the main list.

On Thu, Sep 3, 2009 at 4:16 PM, Sébastien Lorion <sl@...> wrote:
I am currently learning Scala with the intent of using it in a large
scale project, and what David Flemström said below is also becoming a
concern for me.

What is the opinion of people on this matter ? Would you objectively
recommend Scala for a massively online game where performance,
flexibility and maintainability are all prime factors in the adoption
of a platform/language ?

Sébastien

On Wed, Sep 2, 2009 at 16:32, David Flemström<david.flemstrom@...> wrote:

> I thought that was part of the Scala "philosophy", if you will; to reflect on
> the language itself, to analyze options and embrace language features that
> enhance the language. I'm not proposing that the instantiation system of Scala
> should be replaced, but there are things that could be done to improve the
> current situation anyways.
>
> To me, Scala is slowly becoming in a way like what Perl is today. New features
> are added all the time (Implicit methods? Named arguments? Package objects?
> etc) and the language is becoming more and more complex and more obscure
> problems arise because of that. It's not there yet, but that's where it's
> going, slowly but surely.
>
> That's why I brought this discussion up to begin with: Is it really too late
> to bring the language back to the (supposed) root principles it took from
> functional programming, where a language is simple but powerful and not
> complex, broad and filled with workarounds because you have to fight the
> language itself? How many threads are there about "double" implicit
> conversions? How often do questions pop up along the lines of "how does type
> variance work together with existential types and what does the compiler mean
> by '[?] forSome { type ? <% $2 }'"?
>
> I might be seeking a solution to a problem that doesn't exist, but isn't that
> what progress is all about? And wouldn't the language benefit from simplicity?
>
> Thanks. :-)



--
http://erikengbrecht.blogspot.com/