groovy VS Gradle

This time, I visited Groovy. Given my biased first impression about Java and the JVM, I wasn't too exited! But I couldn't have been more wrong! 😁

The default programming language is Kotlin instead of Java. Also, Build configuration language is nowadays Kotlin DSL (build.gradle.kts) instead of Groovy DSL (build.gradle), the past default.

There are languages that are more like "script versions of java", lately including java itself - you can run simple .java stuff directly with a shebang line now - but things like Beanshell of yore and Groovy are far more java-like than javascript.

Install Groovy: To use Groovy, you'll need to first install it. You can find the installation instructions on the Groovy website (https://groovy-lang.org/)

On https://groovy-lang.org a lot of big companies are listed which use(d) Groovy. Is this still current? E.g. Netflix, ...

Groovylang

Hence, Groovy

If you want the power of JAVA but the feel of PYTHON, try Groovy (https://groovy-lang.org/) . Basically a scripting lang for JVM but can be dynamically/statically compiled and is 100% compatible with all JAVA libs but looks like Python

Doesn't Groovy (https://groovy-lang.org) achieve much of this? I remember being taught with it at university for some time before they introduced Java. With Groovy you don't need the class or main method, and can have a program which is just `println "Hello world!"`.

A ("shared") build service is kind of like a singleton, in that when you register one in any project, it's available in all projects as a single instance. (This unfortunately turns out not to be true, in some cases, when using composite builds, but can be worked around.) An actual singleton (global static instance) doesn't work at all, for the record—try it if you want to lose some sanity. Anyway, use a build service whenever you need global mutable state in your build.

When using build tools like Maven or Gradle, you can configure environment variables in the build scripts or configuration files.

For large projects, purpose-made build tools such as Gradle and Maven are preferred for managing the directory structure since they introduce additional semantics for managing test code and other programming languages (among lots of other things). Most IDEs can integrate with these build tools easily. If you're just starting out though, I wouldn't worry too much about these, you can visit them later.

Project Build and Management: Apache Maven 3 (3.9.5), Gradle 8 (8.3)

No wonder this had been raised previously, https://github.com/gradle/gradle/issues/15383

Ktor, a powerful web framework built with Kotlin, offers a lightweight and flexible solution for building web applications. In this article, we will guide you through the process of creating a Ktor project manually using Gradle and SDKMAN!. By following the steps below, you'll have a basic Ktor project up and running in no time.

The details regarding the code compiling would vary from one project to another. For that project, it seems that it uses Gradle (a helper tool) for compiling. Check Gradle's documentation for more information.

At the moment, Java 20 is the latest version, but Java 17 is the latest LTS release. It's usually best to use an LTS release, because the latest releases won't be widely supported. And that's true of Gradle too. You're using Gradle 8.0, but not even the latest version of Gradle (8.2) fully supports Java 20. You'll have to wait for Gradle 8.3 to use Java 20.