If you've watched Toward a Design for Ruby http://www.confreaks.com/videos/1278-rubyconf2012-toward-a-design-for-ruby … and didn't like it, I haven't heard from you. Please tell me your thoughts.
@brixen I don't think Ruby should have a single memory model unless MRI abandons the GIL. I also don't think they should abandon the GIL...
-
-
@bascule can you elaborate why a single memory model is bad? -
@brixen what would it be but the GIL? -
@bascule to me, the semantics with the GIL are a subset of the semantics without the GIL. -
@brixen GIL errata lets people get away with things that are totally broken without the GIL -
@bascule I understand that. It's not an argument for NOT having a single, defined memory model instead of the ad hoc current situation. -
@brixen all that said you're not going to get the memory model you want from ruby-core. matz said he's "not the thread guy" -
@bascule lol, hence the rest of my talk. :) -
@brixen yeaaaah good luck with that ;) - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.