This a textbook case of Chesterton's fence: before tearing down a fence, find out why it was put up.
This fence went up because plenty of people never figured out how to enable launch at login, kept missing their notifications, and let us know they weren't happy about it. So on-by-default is what causes the fewest headaches. It's also one click to turn off.
Hanlon's razor says never attribute to malice what's adequately explained by stupidity. In this case it isn't even stupidity, unless listening to user feedback counts. Can't make everyone happy!
That said, I'd be happy to implement a setup step on first launch where you choose this upfront. Have a triply nice day!
RexSystem1 voteoriginally by @benstor214 on GitHub OP
"This fence went up because plenty of people never figured out how to disable launch at login, kept being annoyed needing to close the window, and let us know they weren't happy about it. So off-by-default is what causes the fewest headaches. It's also one click to turn on."
You do realize that the exact same argument could be employed in favor of the opposite? I am also not sure if I would compare opt-out with a fence. Opt-out means you force a certain setting on the user and it befalls to said user to free himself from it. Opt-in implies the user entered on their own volition... kinda like entering a fenced off area. But I found your attempt of selling opt-out as the one more adhering to user choice most entertaining.
Just imagine on login all your steam games would start because all them have "Launch at login" on by default. That would be an experience. Not one I would enjoy, but still... an experience.
All those moronic game publishers not having their games start on login, or maybe it's malice?
Thread
Comment by Hampus
Comment by @benstor214