Skip to content

docs: Blog post about JDK support in the next Scala LTS #1736

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 9 commits into from
Jan 31, 2025

Conversation

tgodzik
Copy link
Contributor

@tgodzik tgodzik commented Jan 21, 2025

Copy link
Member

@SethTisue SethTisue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this round, I've tried to only give substantive feedback and not nitpick the grammar and such.

Before this is published, I would like to have a second opportunity to polish the prose and the flow.

@SethTisue SethTisue changed the title docs: Create blog about the next Scala LTS docs: Blog post about JDK support in the next Scala LTS Jan 21, 2025
@SethTisue
Copy link
Member

I suggest also having a second PR that also updates https://docs.scala-lang.org/overviews/jdk-compatibility/overview.html appropriately — basically by linking to this very blog post.

@SethTisue SethTisue marked this pull request as draft January 23, 2025 15:12
@SethTisue
Copy link
Member

someone already shared this on the Scala Reddit, though they withdrew it when I objected. I've marked the post as 'draft" in the hopes of discouraging wide sharing.

@tgodzik
Copy link
Contributor Author

tgodzik commented Jan 23, 2025

someone already shared this on the Scala Reddit, though they withdrew it when I objected. I've marked the post as 'draft" in the hopes of discouraging wide sharing.

It's not really a secret, but it's weird to share before being published.

@JD557
Copy link
Contributor

JD557 commented Jan 23, 2025

There's one thing that bugs me about Scala dropping Java 8: It is now going to be more troublesome to distribute Scala applications to desktop users.

For example, I believe that the traditional way would be to distribute the .jar and mention "This software requires Java installed".

This is an issue as, when a user searches for "Download Java" in Google, it gets pointed to https://java.com, which provides only Java 8 binaries.
As such, end users are much more likely to have Java 8 installed in their systems.

I know that this is a niche, but maybe the blog post could have a mention to where one should download the most recent JDK and/or JRE?

@tgodzik
Copy link
Contributor Author

tgodzik commented Jan 23, 2025

There's one thing that bugs me about Scala dropping Java 8: It is now going to be more troublesome to distribute Scala applications to desktop users.

It's a good point. Maybe Scala Native or JS would be useful for those cases, but let's discuss that once I create the contributors thread before publishing the blogpost.

@He-Pin
Copy link

He-Pin commented Jan 23, 2025

Hi, as actually everyone I know will just jump from Java 8 to Java 21, and our Java 17 Jvm is not well maintained too, Java 21 maybe considerable here too.

Copy link
Member

@sjrd sjrd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A bunch of suggestions for the English grammar and phrasing. Mostly cutting long sentences into several smaller, active voice sentences.

@tgodzik
Copy link
Contributor Author

tgodzik commented Jan 28, 2025

A bunch of suggestions for the English grammar and phrasing. Mostly cutting long sentences into several smaller, active voice sentences.

Thanks! That was very thorough!

@tgodzik tgodzik requested review from SethTisue and sjrd January 28, 2025 13:57
@SethTisue
Copy link
Member

SethTisue commented Jan 28, 2025

@tgodzik okay, I think we have enough Scala and Java projects in the projects lists. (I separated them into two lists.)

If the lists seem long, well.... I really think it's really good ammunition and worth having.

Copy link
Member

@SethTisue SethTisue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM otherwise

Copy link
Member

@lrytz lrytz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me!

@tgodzik tgodzik requested review from SethTisue and lrytz January 30, 2025 13:37
@tgodzik tgodzik marked this pull request as ready for review January 30, 2025 13:37
@tgodzik
Copy link
Contributor Author

tgodzik commented Jan 30, 2025

I will post on contributors, should I essentially copy over the contents, so that people get the full picture?

@SethTisue
Copy link
Member

SethTisue commented Jan 30, 2025

I don't see a need to copy-and-paste when you can just link to the blog post.

Copy link
Member

@SethTisue SethTisue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I pushed two commits with a number of small tweaks.

@tgodzik
Copy link
Contributor Author

tgodzik commented Jan 31, 2025

I pushed two commits with a number of small tweaks.

And I removed them by mistake 😅

I added back the changes, sorry! I will update the table in the next PR

@tgodzik tgodzik merged commit 741b646 into scala:main Jan 31, 2025
1 check passed
@tgodzik tgodzik deleted the next-lts branch January 31, 2025 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.