News for hackers. Stuff that matters.

A comment on 38% of bugs at Airbnb could have been prevented by using types. Parent comment

Re:38% of bugs at Airbnb could have been prevented by using ... by est31 on Monday February 11, 2019 @04:05AM (#19133003)
> the only "threading" that ruby and python support natively is the spawn-another-process-and-find-a-way-to-coordinate kind

Are Javascript workers something different?

[ Parent | on HN ]
Re:38% of bugs at Airbnb could have been prevented by using ... by akvadrako on Monday February 11, 2019 @05:05AM (#19133245)
According to the Node 11 docs, worker threads are more lightweight than processes, but still heavy.

That makes me think they run in the same address space, but use separate runtimes. So it's more scalable than ruby and python threads or multiprocessing.

[ Parent | on HN ]
Re:38% of bugs at Airbnb could have been prevented by using ... by jashmatthews on Monday February 11, 2019 @07:28AM (#19133908)
JRuby doesn't have a GIL to begin with so there's no requirement to use multiprocessing to host Rails apps etc.

They're an improvement over a single GIL but not by much. IIUC, they're like Racket's Places: a complete duplication of the VM but sharing an address space. The basic implementation doesn't really save much memory but it's a bit more convenient.

There's been a couple of attempts to implement subinterpreters for CRuby too.

[ Parent | on HN ]
Re:38% of bugs at Airbnb could have been prevented by using ... by regularfry on Monday February 11, 2019 @10:10AM (#19134954)
JRuby is an incredibly underrated piece of kit. That startup time, though...
[ Parent | on HN ]
Re:38% of bugs at Airbnb could have been prevented by using ... by hardwaresofton on Monday February 11, 2019 @07:26AM (#19133892)
A good article on them:

https://medium.com/lazy-engineering/node-worker-threads-b57a...

[ Parent | on HN ]