Make other implementations more visible to users #2020
Conversation
The list of other implementations is hidden in the About page, which few developers will hit. By showing developers this list in the Downloads page, developers can be better informed and aware that the Ruby language is rich and widely adopted to the point of having multiple implementations and engines to run Ruby code.
|
@jcserracampos hey Julio, any chance this can be considered? |
|
Hey @ismailarilik, @hsbt, @stomar -- any chance you can take a look at this? |
|
OK, this language was exactly taken from the existing about page. https://www.ruby-lang.org/en/about/ The download page isn't for this language. |
|
Let's forget about the text for a second, and discuss the main point: Ruby is a programming language specification that has multiple implementations. The proposal here is to surface these other implementations under the Download page because that is the page that almost every developer visits. I'd be curious to see a traffic analysis of the Download page versus the About page, but I'd confidently guess that the About page gets less than a 1/10 of the hits that the Download page gets. By raising awareness that Ruby has multiple implementations, developers can more confidently invest in Ruby for new projects. This of course assuming that ruby-lang.org is a website dedicated to the Ruby language more than to the Ruby runtime. |
|
But ruby-lang.org is for MRI. Why you put the info above of Compiling Ruby section? I agree indicating visitors about alternative runtimes would be better, but the proposed change is too long. I'd suggest adding a link to the existing section on "About" page for such runtimes. |
|
Got it, thanks for the feedback. I'll work on that proposed change sometime this week. |
The list of other implementations is hidden in the About page, which few developers will hit. By showing developers this list in the Downloads page, developers can be better informed and aware that the Ruby language is rich and widely adopted to the point of having multiple implementations and engines to run Ruby code.