News for hackers. Stuff that matters.
Re:Eliminating GIL in Ruby Through Hardware Transactional Me... by bsaul on Sunday September 21, 2014 @04:34PM (#8348187)
Is it me or does anyone here thinks that with the recent progress in static compiled language in user-friendliness, the path of optimizing the ugly parts of dynamic languages outside of the language design itself is a waste of time ?

Note : not saying this research isn't interesting, because it may lead to many different uses. Just about the example chosen itself.

Re:Eliminating GIL in Ruby Through Hardware Transactional Me... by jshen on Sunday September 21, 2014 @04:46PM (#8348237)
I have used many of the fancy staticly typed languages and still find dynamic languages more productive, and more accessible to a larger range of people.
Re:Eliminating GIL in Ruby Through Hardware Transactional Me... by NotAtWork on Sunday September 21, 2014 @05:13PM (#8348322)
I only find them more productive until about 300-500 LoC.

It's about at that point, particularly if there's multiple files, that I find myself suddenly wishing for stronger type systems.

That being said, most things I write (outside of work) aren't that long, and you can get started faster in dynamic languages.

Re:Eliminating GIL in Ruby Through Hardware Transactional Me... by jshen on Sunday September 21, 2014 @05:37PM (#8348406)
I haven't felt any improvement in productivity at higher KLOC counts with statically typed languages in my coding. I've also worked at several large companies and have watched teams using both types of languages, and I have not seen more productivity from those using statically typed languages.

More importantly, there is no conclusive empirical evidence either way.

Re:Eliminating GIL in Ruby Through Hardware Transactional Me... by cantankerous on Sunday September 21, 2014 @05:57PM (#8348475)
Which statically-typed languages are you using?
Re:Eliminating GIL in Ruby Through Hardware Transactional Me... by jshen on Sunday September 21, 2014 @06:45PM (#8348585)
I've used many of them. Java, Scala, Haskell, ocaml, etc.

Also, in the open source world there is no visible difference in robustness or productivity.

Edit: I forgot to mention go, and I thought HN was better than down voting someone that has a different opinion.

Re:Eliminating GIL in Ruby Through Hardware Transactional Me... by jgalt212 on Sunday September 21, 2014 @10:51PM (#8349037)
jshen: I feel your pain. I think there's been too much down-voting by the karma bullies on HN lately, and I think that's the number one reason there's been less comments on HN.

Of course, there are folks who will feel that even though there are less comments lately the level of discourse is higher.

Re:Eliminating GIL in Ruby Through Hardware Transactional Me... by luikore on Sunday September 21, 2014 @11:43PM (#8349123)
Removing-VM-lock-with-HTM has nothing to do with dynamic or static, compiled or not compiled. Many "staic compiled languages" can have global VM lock too.
Re:Eliminating GIL in Ruby Through Hardware Transactional Me... by evilduck on Sunday September 21, 2014 @05:20PM (#8348347)
That sort of neglects the impact of these sorts of efforts on existing codebases, and there's millions of man-hours poured into writing those.