Skip to content

Update why-scala-3.md #2116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jul 12, 2021
Merged
Show file tree
Hide file tree
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions _overviews/jdk-compatibility/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Sometimes new JVM and JDK (Java Development Kit) versions require us to update S

Even when a version combination isn't listed as supported, most features may still work. (But Scala 2.12+ definitely doesn't work at all on JDK 6 or 7.)

In general, Scala works on JDK 11+, including [GraalVM](https://www.graalvm.org/docs/reference-manual/scala/), but it probably won't take special advantage of features that were added after JDK 8. See [below](#jdk-11-compatibility-notes).
In general, Scala works on JDK 11+, including GraalVM, but it probably won't take special advantage of features that were added after JDK 8. See [below](#jdk-11-compatibility-notes).

Lightbend offers [commercial support](https://www.lightbend.com/lightbend-platform-subscription) for Scala. The linked page includes contact information for inquiring about supported and recommended versions.

Expand All @@ -32,7 +32,7 @@ We generally recommend JDK 8 or 11 for *compiling* Scala code. Since the JVM ten

If you compile on JDK 11+ but have users on JDK 8, additional care is needed to avoid using APIs and features that don't exist in 8. Therefore, compiling on 8 may be the safer choice. Some Scala developers use JDK 11+ for their daily work but do release builds on JDK 8.

Additionally, you can also run your scala application on [GraalVM](https://www.graalvm.org/docs/reference-manual/scala/) which is a JVM. GraalVM performs well on the Scala benchmarks, and it benefits from GraalVM runtime and runs faster too.
Additionally, you can also run your scala application on GraalVM which is a JVM. GraalVM performs well on the Scala benchmarks, and it benefits from GraalVM runtime and runs faster too.

## Long Term Support (LTS) versions

Expand All @@ -50,7 +50,7 @@ In almost every case, you're free to use the JDK and JVM of your choice.

JDK 8 users typically use the Oracle JDK or some flavor of OpenJDK.

Most JDK 11+ users are using either OpenJDK or [GraalVM](https://www.graalvm.org/docs/reference-manual/scala/) which runs in the context of OpenJDK.
Most JDK 11+ users are using either OpenJDK or GraalVM which runs in the context of OpenJDK.

OpenJDK comes in various flavors, offered by different providers. We build and test Scala using [AdoptOpenJDK](https://adoptopenjdk.net) in particular, but the differences are unlikely to matter to most users.

Expand Down
2 changes: 1 addition & 1 deletion _overviews/scala3-book/why-scala-3.md
Original file line number Diff line number Diff line change
Expand Up @@ -252,7 +252,7 @@ a.tail // List(20, 30, 40, 10)
a.take(3) // List(10, 20, 30)
a.takeRight(2) // List(40, 10)
a.takeWhile(_ < 30) // List(10, 20)
a.filter(_ < 30).map(_ * 10) // List(100, 200)
a.filter(_ < 30).map(_ * 10) // List(100, 200, 100)

val fruits = List("apple", "pear")
fruits.map(_.toUpperCase) // List(APPLE, PEAR)
Expand Down