update status of JDK 8 #2351
update status of JDK 8 #2351
Conversation
also change AdoptOpenJDK->Temurin also move some GraalVM text to a more appropriate location
|
As you may not yet be aware, I spent a few hours with Since there is no longer any "and such", but only Also some of your periods could be exclamation marks, as in "New! and improved!" It seems to me that you say "reasonable" when a more precise word might be "passable." I'm reading Pickwick Papers, so soon I will be speaking only as Mr Pickwick does, or rather, as only he can. |
| If you compile on JDK 11+ but have users on an older JDK version, additional care is needed to avoid using APIs and features that don't exist in 8. Therefore, *compiling* on 8 may be the safest choice in this scenario. (Some Scala developers use JDK 11 or 17 for their daily work, but do release builds on JDK 8.) | ||
|
|
||
| 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. | ||
| JDK 8 remains in use at many shops (as of early 2022), but usage is declining and some projects are dropping support. If you compile on JDK 11+ but want to allow your users to stay on 8, additional care is needed to avoid using APIs and features that don't exist in 8. (For this reason, some Scala developers use JDK 11 or 17 for their daily work but do release builds on JDK 8.) |
There was a problem hiding this comment.
I understand that we intentionally avoided mentioning --release, but I think this wording is nearly misleading as it makes it sound like one has to do this manually.
There was a problem hiding this comment.
I see what you mean. Would you like to PR a suggested wording change?
note that I chose not to add coverage of
-releaseand-targetand such. I feel like it would be out of scope for this page to go into detail about that. (a separate PR that added a brief reference and link of some kind to information on that would be welcome.)