-
Notifications
You must be signed in to change notification settings - Fork 330
Updates to the homepage - add new tagline, why scala? and use cases #1518
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! I only have minor comments.
This snippet is a bit conflicting. Node.js and serverless are not frontend web technologies. Actually, the point is that you can use Scala.js very effectively on the server-side, where its fast and lightweight runtime can be advantageous over the JVM for some services. Further reading. |
Thanks, I can see that it makes sense what you say - I think I can keep all mention of node.js to the server-side section |
@armanbilge This is a good point! Slightly related to that, the last point of the “Command Line” section mentions compilation to native binaries. I wonder if we should capture the multi-platform aspect of Scala in a separate section (outside the “Frontend Web” and “Command Line” sections)… Or maybe we could just move the sentence about Node.js into the “Server Side” section and keep the “Command Line” section as it is? |
(I'll review next week.) |
Yeah, it's very difficult to present this aspect of Scala :) rather than present platforms as independent features, I think it's helpful to present them under the use cases where they are most relevant. Actually, all platforms could technically be used in most/all domains (except frontend, that's effectively JS-only), it's just there are certain use-cases some platforms can excel at. servers: Scala JVM |
@armanbilge I changed the frontend section to avoid mentioning node.js |
d8bd375
to
46c7d4a
Compare
46c7d4a
to
2b9391e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great :)
@SethTisue did you get a chance to look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is fantastic. Well done!
This is the next step in modernising the Scala homepage.
We simplify the large opening paragraph, splitting it into three new paragraphs that better communicate the same message, and add more detail.
We also add a new "use cases" section, which is based upon what was reported in the Scala Developers Survey 2022. This section could potentially be continuously evolved as developments unfold.
The "Scala in a nutshell" section is removed - we felt that the examples were outdated, and now we have the carousel of code snippets to better showcase the "flavor" of Scala.
Thanks to everyone at the Scala Center and LAMP who assisted in validating the design and suggesting content.
overview:

server-side:

data processing:

command-line:

frontend web:
