Comment: Re:Services (Score 4, Informative) 306
> it will also let services start on a trigger and stop when needed instead of running all the time.
Nice.
Although I have to wonder, why are "services" treated differently than other programs, in this context or any other? Does it have any positive effect?
First of all, it's worth noting that Service trigger events shipped with Windows 7.... they're just making better use of this capability in Windows 8. (This is a common flaw with Microsoft's development process for Windows.... they include some really smart new APIs but then take another 5 years to start really using them thoroughly in Windows itself.)
But to your main question -- why are services different from other programs? A service is actually a regular program, with one exception -- it hooks into the operating system to receive events telling it to pause, continue or stop its operation.
Why do this? Management. You don't want 20 different programs with 20 different ways of starting & stopping them.
A feature the Windows Service Control Manager offers is the ability to run your service in a single pooled process alongside other services that require roughly the same privileges on the system. You can see this at work in the Windows 7 task manager -- go to the Services tab and sort the list by PID. If you ever wondered what "svchost.exe" is on a Windows system, or why there are several running on your system, each under different user accounts...... there you go.