Hacker News Reader

IMO it's such a good thing about PHP that I think other stacks should follow that model (I assume ROR does).

I think it's a superior model to the long-running application. Unless your company has 0 developers in it who make a memory leak, or make a fatal uncaught exception.

View on HN

Hm. This is this and that is that. It is perfectly possible to write a stateless service hosted in a stateful process.

In fact, the popular PHP-FPM way to host PHP does just that.

If you want to take it to the extreme, there's always CGI, of course.

Ruby on Rails lives inside a long-running application server. In development, it has dynamic class loading and will reload on file changes, but in production an app can have a lengthy startup time. It does have the memory problem, but I have never seen the server crash outright as a result of an exception while handling a request.

Reply on news.ycombinator.com