It depends what level of abstraction you're working at. At the level of sockets, you're right that a mail server receives a connection from a sender when a newsletter is sent, whilst an RSS aggregator initiates connections to each feed's source when it polls, even if there are no new articles. At a lower level, the server's doing polling to check for new connections, but that's a fast local operation so it doesn't break the higher-level abstraction.
I wouldn't say there's much difference from a user point of view, i.e. "clicking". Polling for feeds with an RSS reader is comparable to polling for new messages with a mail client. Both can be made fast by fetching mail and/or news in the background, either using a client or using an OS service.
You are quite correct. But for vast majority of real world users RSS is quite misterious piece of technology. Emails are ok, everyone 'knows' what the email is? But 'feed'. Can I save it for offline use? Can I forward it to friends and family?
Author of Kill the Newsletter! here. Thank you for your comment. I think it’s
cool that you’re using an email reader that doesn’t require any clicks :)
But, seriously, of course the tool I developed is for a niche. In particular, I
had only my own use case in mind. I know the benefits of newsletters. So much so
that Kill the Newsletter! starts with copy saying “I love newsletters …”.
The name Kill the Newsletter! is only a joke. I’m sorry that you seemed not to
appreciate it. After all, joking with death and killing is not exactly
G-rated. So the joke is actually on me and I apologize if it caused you any
inconvenience.
I hope you can still consider Kill the Newsletter! an option if you ever run in
the inteded use case.
