Windows favors multi-threading, which means that a service is implemented by one single process.

In a previous life I wrote the software that controlled my physics experiments. That software had to deal with all kinds of possible failures in equipment. That is probably where I learned to rely on multiple safety nets inside and around my systems.

I don't expect an overnight change of all desktops to what the US Military used to call B3 level security. And even that would not stop users from shooting themselves into the foot.

For many people my software is something that you install and forget. I like to keep it that way.

One bug in an SMTP server can open up the whole machine for intrusion.

However, writing software without defects is not sufficient. In my experience, it is at least as difficult to write software that is safe - that is, software that behaves reasonably under adverse conditions.

Writing software that's safe even in the presence of bugs makes the challenge even more interesting.