Language War - Scala versus Python (Part 2)
blog.zlemma.com
Language War - Scala versus Python (Part 2)
1–10 of 26 posts
Re: Language War - Scala versus Python (Part 2)
#2Regarding the last point, what's the latest & greatest in vim support for Scala?
Re: Language War - Scala versus Python (Part 2)
#3Regarding the last point, what's the latest & greatest in vim support for Scala?
Anything vim, I follow derekwyatt - https://github.com/derekwyatt/vim-scala
Re: Language War - Scala versus Python (Part 2)
#4"Yes, Scala has Lift but it can’t match the maturity of Django. This overrode the benefits of some of the other libraries/tools that Scala/Java have on offer. Python gets ahead again: 2-1."
How does one come to the conclusion that the maturity of an 8 year old web framework, beats out the benefits of the almost 20 year old battle tested Java ecosystem. Not to mention the Scala Ecosystem is included as Icing on the JVM cake. OP also compared Lift to Django. How does OP not mention Play? Although an argument about the better of the two would be based strictly on opinion, from my view Play has more momentum in the race for the premier Scala Web Framework.
Re: Language War - Scala versus Python (Part 2)
#5"Yes, Scala has Lift but it can’t match the maturity of Django. This overrode the benefits of some of the other libraries/tools that Scala/Java have on offer. Python gets ahead again: 2-1." How does one come to the conclusion that the maturity of an 8 year old web framework, beats out the benefits of the almost 20 year old battle tested Java ecosystem. Not to mention the Scala Ecosystem is included as Icing on the JV…
Most of the Java ecosystem you'd be using is not 20 years old.
Re: Language War - Scala versus Python (Part 2)
#6"Yes, Scala has Lift but it can’t match the maturity of Django. This overrode the benefits of some of the other libraries/tools that Scala/Java have on offer. Python gets ahead again: 2-1." How does one come to the conclusion that the maturity of an 8 year old web framework, beats out the benefits of the almost 20 year old battle tested Java ecosystem. Not to mention the Scala Ecosystem is included as Icing on the JV…
Most of the Java ecosystem you'd be using is not 20 years old.
On that same note, most of the Django ecosystem isn't as mature as Django either. What point are your trying to make?
Re: Language War - Scala versus Python (Part 2)
#7"Yes, Scala has Lift but it can’t match the maturity of Django. This overrode the benefits of some of the other libraries/tools that Scala/Java have on offer. Python gets ahead again: 2-1." How does one come to the conclusion that the maturity of an 8 year old web framework, beats out the benefits of the almost 20 year old battle tested Java ecosystem. Not to mention the Scala Ecosystem is included as Icing on the JV…
The Java ecosystem is not terribly usable from Scala - even if you can call all the methods, it's not idiomatic, it will expect Java collection types etc. And few of the worthwhile parts of Java's libraries are 20 years old.
You can build cool stuff in scala + e.g. wicket, I've done it, but there's an extra layer of awkwardness to deal with that doesn't exist with python/django.
Re: Language War - Scala versus Python (Part 2)
#8Earlier quoted context omitted.
Most of the Java ecosystem you'd be using is not 20 years old.
On that same note, most of the Django ecosystem isn't as mature as Django either. What point are your trying to make?
You can't claim that Scala is more mature than Python just because it's built on the (very mature) JVM. You have to look at the tools you will actually be using, and neither Play nor Lift are as mature as Django, nor is Scala the language as mature as Python.
Re: Language War - Scala versus Python (Part 2)
#9"Yes, Scala has Lift but it can’t match the maturity of Django. This overrode the benefits of some of the other libraries/tools that Scala/Java have on offer. Python gets ahead again: 2-1." How does one come to the conclusion that the maturity of an 8 year old web framework, beats out the benefits of the almost 20 year old battle tested Java ecosystem. Not to mention the Scala Ecosystem is included as Icing on the JV…
Are you suggesting that we should go with Lift/Play instead of Django? If so, can you elaborate on your argument? As you can tell from the article, I'd love to see Scala beat Python, but I can't see Scala scoring over Python on the web framework front.
Re: Language War - Scala versus Python (Part 2)
#10"Yes, Scala has Lift but it can’t match the maturity of Django. This overrode the benefits of some of the other libraries/tools that Scala/Java have on offer. Python gets ahead again: 2-1." How does one come to the conclusion that the maturity of an 8 year old web framework, beats out the benefits of the almost 20 year old battle tested Java ecosystem. Not to mention the Scala Ecosystem is included as Icing on the JV…
We were merely in search of a good web framework. Java has battletested libraries but so does python and a lot of other general programming languages. It still isn't answering our core question.
A decision on what web framework to use has much more to do with the framework itself(its philosophy and community) than with the language it is built in.
Coming to django, I would argue that it is the best documented project on this planet! Django has a huge number of plugins, quickens the process, and is based on some amazing philosophies(DRY) and you happen to admire what a big deal it is when you go deep into design of your web app.
Also, I can even argue that I can get a programmer who doesn't know python to start on Django in 4 hours. Now, I wouldn't bank on this point as it is a language ecosystem point, but it is a true fact, happened to me some years ago.
Lift, is cherry picking features from django/rails, which is actually a good thing, but I see it being a lot less progressive as compared to Django even at the scale at which Django is right now.
Play, I haven't used, so cannot argue much on that. I think Play2 is less than a year old? Surely, I cannot let my startup developers write more bytes than necessary. Why code something which is already done and that is precisely what happened with us when we started working with Django. Well tested libraries can be pip installed.