rubenv

Tony Stark? You mean Elon Musk, right?

Care to back that up with sources or a reference?

Last release seems to be in 2012. Is this still maintained?

With rsnapshot of duplicity?

That's sort of not the point here. It's not always that "new fad" is better than "old and established", it might be the other way around.

What matters is what's most productive for the project, for the people working on it.

What doesn't help is making a fuss about it. Spend your time contributing and get over the fact that not everyone thinks the same. Or walk away, because nobody is forcing anyone to get involved.

Let's just stay constructive and respect what people are doing.

If you really want to do it differently, just go out and do it, prove people wrong with results, rather than arguments and flames. That way everyone wins.

Works both ways really, people might hate your project because you stick to old & known C, rather than write it in e.g. Go.

Chad_oliver is right: the impact is negligible. We wouldn't do it if it would deteriorate the user experience.

There's a lot of great documentation on the systemd site. An exact description of socket activation and its intended use cases is on there as well: this is definitely one of them.

Monit falls in the category of forever: it's a duplication of your process manager. I think you can do some of these things with upstart as well.

If you are currently running Ubuntu and use upstart, by all means leave it like that: don't fix it if it ain't broken.

But do know that you miss out on some very nice things :-)

That assumes that node itself will never crash, or that your server will never reboot.

Just keeping it running isn't the main point though: socket activation is great if you want to increase server density. And the whole-system monitoring + resource policies are very nice tools for system administrators.

There's a lot more to systemd and node.js than simply running node.