You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am in the process of updating my old ruby documentation over the last 20 years right now.
One entry is "irb.md", so I will update that file locally.
I split this in two things:
core/
add_ons_for_ruby/
So, for instance, in core I have string.md which will explain how to use strings in ruby. I also
store lots of examples in that .md file eventually.
In add_ons_for_ruby/ I store things such as puma.md or sequel.md and so forth - external
gems.
So, my use case is to want to know which ruby gems are part of core ruby and which ones
are not. I may have to add a third directory ... but anyway.
When I encounter irb, I wonder if irb is core of ruby or not. If it is an external gem then perhaps
it is both an add-on and core, but I believe it belongs more to core. So I would put it into
core/irb.md.
This now brings me to the website.
I found it recently and you keep track of versions, e. g. which ruby version came with which
release. This is super-useful.
Would it be possible to also show WHEN a particular core-gem became an external gem
too? For instance, "irb became a gem in 2018" or so? Year may suffice, but year + month
may be even better to know. Ideally this could also be shown in that table layout you
use on the website.
This probably takes some time, so perhaps entries "(not known)" can be the default,
and the information when a gem became external (to ruby core) be added at a later
time.
This may be useful for people to know too. At any rate, this is a not so important
suggestion, so please feel free to proceed as you wish in this regard. Thank you for
reading this issue request. Grüße nach Berlin.
The text was updated successfully, but these errors were encountered:
Hello Jan,
I am in the process of updating my old ruby documentation over the last 20 years right now.
One entry is "irb.md", so I will update that file locally.
I split this in two things:
So, for instance, in core I have string.md which will explain how to use strings in ruby. I also
store lots of examples in that .md file eventually.
In add_ons_for_ruby/ I store things such as puma.md or sequel.md and so forth - external
gems.
So, my use case is to want to know which ruby gems are part of core ruby and which ones
are not. I may have to add a third directory ... but anyway.
When I encounter irb, I wonder if irb is core of ruby or not. If it is an external gem then perhaps
it is both an add-on and core, but I believe it belongs more to core. So I would put it into
core/irb.md.
This now brings me to the website.
I found it recently and you keep track of versions, e. g. which ruby version came with which
release. This is super-useful.
Would it be possible to also show WHEN a particular core-gem became an external gem
too? For instance, "irb became a gem in 2018" or so? Year may suffice, but year + month
may be even better to know. Ideally this could also be shown in that table layout you
use on the website.
This probably takes some time, so perhaps entries "(not known)" can be the default,
and the information when a gem became external (to ruby core) be added at a later
time.
This may be useful for people to know too. At any rate, this is a not so important
suggestion, so please feel free to proceed as you wish in this regard. Thank you for
reading this issue request. Grüße nach Berlin.
The text was updated successfully, but these errors were encountered: