Re:Ruby concurrency is hard: how I became a Ruby on Rails co...
by letmeinhere on Wednesday November 23, 2022 @11:38PM
(#33727852)
Isnt the php concurrency story distinctly good, with every request spawning its own process?
[ Parent
| on HN ]
Re:Ruby concurrency is hard: how I became a Ruby on Rails co...
by colonwqbang on Thursday November 24, 2022 @02:21AM
(#33728609)
Anyone can do "concurrency" by starting from scratch with a fresh process each time. That isn't "having a concurrency story" it's rather the opposite I think. It's very wasteful of system resources, energy, etc.
Re:Ruby concurrency is hard: how I became a Ruby on Rails co...
by stevewatson301 on Thursday November 24, 2022 @04:01AM
(#33729145)
PHPs model would be okay if they used green threads/goroutines. That way, you can have a far larger number of workers, as most of them are blocked on database connections or HTTP requests to other services.
Re:Ruby concurrency is hard: how I became a Ruby on Rails co...
by heurisko on Thursday November 24, 2022 @08:08AM
(#33730890)
PHP's model is different, not a mistake.
It has proved successful so far. The shared-nothing, short-lived process avoids classes of issues such as with slow memory leaks, accidentally blocking event loops, and shared memory threading issues.
The language historically hasn't been that great, but its shared-nothing architecture has always been the good part.
Re:Ruby concurrency is hard: how I became a Ruby on Rails co...
by weatherlite on Thursday November 24, 2022 @04:56AM
(#33729503)
On the other hand its simple and works for many many people and apps. I wouldn't just discount it. The fact that "Anyone can do" it is a pro.