Linked by Thom Holwerda on Wed 30th Jan 2013 00:31 UTC
Thread beginning with comment 550953
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: Comment by BeamishBoy
by galvanash on Thu 31st Jan 2013 03:12
in reply to "Comment by BeamishBoy"
RE[2]: Comment by BeamishBoy
by BeamishBoy on Thu 31st Jan 2013 03:34
in reply to "RE: Comment by BeamishBoy"
Python expresses complexity clearly.
Java/Scala/Akka clearly express complexity.
Your way might end up faster, but I doubt it would be very nice to look upon...
Java/Scala/Akka clearly express complexity.
Your way might end up faster, but I doubt it would be very nice to look upon...
I disagree. I dearly love Python since it's the first language that I ever felt truly competent with. But experience has taught me that approaching concurrency using multiple threads and shared state - even microthreads a la Stackless Python - is a very messy business. Actor models, in my opinion, are far cleaner conceptually and scale much better. Hence my preference for Scala over Python in this instance.





Member since:
2010-10-27
As far as I can tell from reading this and other articles, the size of the battle was impressive only because the back end of EVE Online is written in Stackless Python. Using Stackless for something like this is rather like conducting the Berlin Philharmonic through Tristan using Morse Code. From your base on the moon.
A combination of Java/Scala and Akka could have handled this without breaking a sweat.