- No need to register your application with browserid.org

- No need to use an oauth library (just 1 GET request)

- Oauth provides access to user data on the provider, while browserID provides no data. Less anxiety for the users.

- No request_token/access_token pairs

- In the future, the user will (hopefully) be able to change his default browserid and as a developer you just don't care.

thanks, I thought you meant it was easier _as an end user_ and could not see why.

The implementation using browserid.org, to an end user, will not get any easier or harder than OAuth or any other third-party service. On the other hand, a browser-based implementation could simply bring up a browser notification saying "Authenticate to example.org using your email address?", to which you could click "yes".