Why Android change 'compile' to 'implementation' configuration in Gradle dependencies?

Question

As seen in Android Studio 3.0 (canary 3.0), we now add depedencies by declaring implementation instead of compile configuration.

Answer 1

It seems like compile has been deprecated and api or implementation should be used instead. According to The Java Library Plugin - Gradle User Guide Version 3.5:

The compile configuration still exists but should not be used as it will not offer the guarantees that the api and implementation configurations provide.