-
Notifications
You must be signed in to change notification settings - Fork 323
Page which spells out exactly which level of support people can expect from which platform #67
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
Comments
Hi @soc. Cool to see that you've joined up! To be honest, we don't ignore that work. The issue is a lack of people organizing and communicating. If it's important to you, make a proposal and step up– tell us the path you'd like the page to have (better on docs.scala-lang?) and what you'd have on it, and so long as it doesn't run the risk of quickly falling outdated, I'd be happy to put it up. |
Hi @heathermiller, I'll look into it the next week (after my next exam) and think about what's the best way to integrate it into the site.
Getting those answers as fast and easy as possible to potential users might help improve conversation rate a lot. |
#506 addresses this slightly, but we should still do more. but I do think it should be done in a way that doesn't simply present the platforms as equal:
|
#606 does something towards this |
new ticket on Scala Native specifically: #860 |
I think this ticket is too broad to leave open indefinitely. Some pieces have happened, like Scala.js getting much higher billing than it used to have. I invite people to open more specific tickets like #860 on changes in this area they would like to see — or better yet, pull requests! |
It is mentioned a bit in the "Scala runs on the JVM [...]", but we should make it more clear, which versions (5 deprecated, 6 and up supported) are supported and which implementations are tested and verified that they work (OpenJDK/Hotspot ... anything else?).
Additionally, it would be nice to stop ignoring all the work people have done to get Scala running on Android and mention that too (and link to the appropriate resources/mailing lists).
Mentioning the JavaScript backend and Avian support, marked as "experimental" would make sense imho, too.
The text was updated successfully, but these errors were encountered: