> pretty strong indication that their API will not be fully compatible If the compatibility problems are from an incomplete implementation of the API, it will

> pretty strong indication that their API will not be fully compatible If the compatibility problems are from an incomplete implementation of the API, it will simply be an inferior inferior implementation, perhaps optimized for different uses or environments. However,if the incompatibility is from an extension of the API introduced after initially embracing the de facto standard set by te widely-used original implementation that is outside their control, it will be a clear example of the Embrace, Extend, Extinguish[2] method. The canonical example of EEE is when Microsoft introduced an incompatible "security feature" in their implementation of Kerberos. Hopefully, Google won't do the same thing to HTTP with a new and supposedly-important "security feature" in their re-implementation of libcurl. [1] https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis... [2] https://web.archive.org/web/20140222133423/http://www.networkworld.com/news/2000/0511kerberos.html https://web.archive.org/web/20140222133423/http://www.networ...