HTTP Authentication comes in several flavours. I've not done it myself, but I think you can do interesting things to with Kerberos. Good for Intranet systems.
HTTP Authentication does have its places.
The only large public website that I know of which still uses HTTP Authentication though is http://www.123-reg.co.uk/
Compare to:
curl --anyauth --user login:password https://example.com/But my point is just: HTTP Auth is not the best-practices answer to non-browser web services auth. Both API-key and signed URLs are both competitive (and probably better) options.
(1) For most large apps, you're not really SSL in the provider's own network, so there's always the cross-app risk if something horrible happens.
(2) It's forcing app-to-app, business-to-business authentication into a username/password mold that doesn't many any real sense; a 128 bit random key (or an SSL client cert) makes more sense anyways.
Against those two problems --- which are marginal, I concede --- HTTP Basic offers... exactly what advantage? I don't see it.
If either (a) or (b) do not hold, Basic Auth is at least as hard as cookie auth.