Comment by shardulaeer

I built the tool simply to improve developer experience. Run `systemctl list-units` and the console is flooded with a wall of services, most of them are not mine. Run `ser status` and I only see the ones that I created. The activity state, CPU and memory usage is displayed so I don't need to run a separate command.

    hp@hp:~$ ser status
    +-----+-------------+----------+----------------+-------+--------+
    | pid | name        | active   | enable on boot | cpu % | memory |
    +-----+-------------+----------+----------------+-------+--------+
    | 0   | hello-world | inactive | false          | 0     | 0      |
    +-----+-------------+----------+----------------+-------+--------+
    | 0   | index.js    | inactive | false          | 0     | 0      |
    +-----+-------------+----------+----------------+-------+--------+

Another UX improvement is the template generation. I found myself googling it everytime. I f there is something more custom (etc sockets) I can use the `ser edit`, this will open nano with a pre-populated template that I can edit.

Finally why limit oneself to systemd? pm2 runs on Mac and windows, I aim to do the same. Same set of commands to create services everywhere, with details abstracted away (easier said than done, need to look into their APIs).