I don't understand why Dave objects to Feedburner in the "2a" point of his post. He seems to be saying that relying on Feedburner as a corporate API can or will burn you if Feedburner changes their policies.

But Feedburner lets you serve your feeds off your own domain (e.g. feeds.mattcutts.com) using a CNAME in DNS. Here's an article from 2007 that talked about how Feedburner made that functionality free after Google bought Feedburner: http://www.mydigitallife.info/how-to-activate-and-use-feedbu...

So if Feedburner ever makes you angry or disappoints you, people are still coming to your domain to get the feeds, and you can just swap Feedburner out with a different system. As far as commercial APIs go, that seems pretty developer-friendly.