News for hackers. Stuff that matters.
Re:Fork() without exec() is dangerous in large programs (2016) by btilly on Tuesday June 14, 2022 @09:46PM (#31748216)
When I see what most people try to do with "a real, fully mature thread and process model", I wind up shaking my head about bad engineering processes.
Re:Fork() without exec() is dangerous in large programs (2016) by jiggawatts on Wednesday June 15, 2022 @05:38AM (#31750865)
Bad... how?

From my perspective watching the various techniques used by a multitude of operating systems over many decades, the Windows-style process+thread model seems to be winning out over the UNIX fork() model.

For example, PostgreSQL seems to suffer greatly from the "forked process per connection" model, necessitating front-ends that do connection pooling. Database engine after database engine seems to go through this phase and then "upgrade" to either a single-process thread pool model, or start using async IO in some way. (Web servers also.)

For reference, Microsoft SQL Server back in the 1990s could on Windows NT 4 could handle more connections than PostgreSQL in 2020...