News for hackers. Stuff that matters.
Re:Ruby concurrency is hard: how I became a Ruby on Rails co... by EdwardDiego on Thursday November 24, 2022 @03:41AM (#33729032)
What do you mean by "get more wrong answers faster"? Given that volatile / synchronized have largely gone the way of the dodo, ditto Object.wait etc. , and that concurrency safe atomics and collections are de rigeur, how do green threads reverse that?

I spent years working on concurrent Java apps post JSR 166, and the only concurrency issues I met were PEBKAC, and some of the awful things people did with Vert.x and it's event bus.

Re:Ruby concurrency is hard: how I became a Ruby on Rails co... by dtech on Thursday November 24, 2022 @04:36AM (#33729374)
Do you have a good resource or summary on why volatile / synchronized are problematic and java.util.concurrent should be preferred?

I always remembered the same, but was recently in a conversation with Java devs who contradicted it, and could not articulate well why this is the case. and could not find good resources on it.

Re:Ruby concurrency is hard: how I became a Ruby on Rails co... by EdwardDiego on Thursday November 24, 2022 @05:29AM (#33729716)
Not off the top of my head. Just experience that they're easily used wrong.