News for hackers. Stuff that matters.

A comment on Scala – 1 Star – Would Not Program Again. Parent comment

Re:Scala – 1 Star – Would Not Program Again by MetaCosm on Monday December 02, 2013 @03:17PM (#6836219)
Most of the stuff I work on is highly concurrent. GILs are the devil. Almost all the joy and ease you from GIL languages is lost as you try to go concurrent and have to use (in python for example) multiprocess and gevent ... then you start getting caught on the rough edges and poor ideas in those tools... and everything falls apart.
[ Parent | on HN ]
Re:Scala – 1 Star – Would Not Program Again by rdtsc on Monday December 02, 2013 @10:53PM (#6838362)
GIL is all evil. If your are dealing with CPU bound concurrency yes, GIL is there to take the fun away. But if your problem is most about IO concurrency (downloading from multiple sockets for ex) GIL is no problem. I get very nice speedup from Python's threads with a silly web crawler I wrote.
[ Parent | on HN ]
Re:Scala – 1 Star – Would Not Program Again by dragonwriter on Monday December 02, 2013 @03:33PM (#6836302)
GIL isn't a language feature, it's an implementation feature — in Ruby, at least, this is a significant difference because there a major implementations (Jruby, most notably) without it even though it is a feature of the MRI implementation.
[ Parent | on HN ]
Re:Scala – 1 Star – Would Not Program Again by MetaCosm on Monday December 02, 2013 @06:58PM (#6837528)
True, but JRuby comes with it own huge bag of rough edges (read: no C extensions for you without a bit PITA). IronPython is in a similar boat.

That said, I do prefer JRuby to Scala.

[ Parent | on HN ]
Re:Scala – 1 Star – Would Not Program Again by syllogism on Tuesday December 03, 2013 @09:00AM (#6840238)
Another option is to use Cython. You can declare a function "nogil", but then you can't call any native Python functions within it. It's good enough for some purposes, but not all.
[ Parent | on HN ]