# Concerns ## Introduction Gradle's architecture strives to meet a set of key concerns. By properly addressing these concerns in our architectural description we hope to convince our stakeholders that these fundamental and key concerns are satisfied by Gradle's architecture. ## Concern List | Concern Name | Evidence | | -- | -- | | <a name="n1"></a> Gradle can build projects written in popular languages such as Java and C/C++. | This concern represents a main functional capability of Gradle. It is the main concern which drives Gradle's architecture. | | <a name="2"></a> Gradle builds will be faster than Maven. | Performance is a key advantage [Gradle has over Maven](https://gradle.org/maven-vs-gradle/). Performance is also advertised as [a key feature of Gradle](https://gradle.org/features/). | | <a name="3"></a> Gradle should be more extensible and flexible than Maven. | Flexibility is a key advantage [Gradle has over Maven](https://gradle.org/maven-vs-gradle/). It is also the main reason why Google, a stakeholder<sup>[1](https://hackmd.io/RTlC56qhToG6Qej3yxdeiA?both#Note)</sup>, chose Gradle as its default build tool for Android.