Skip to content
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

Time / Date information for std-ified gems? #19

Open
rubyFeedback opened this issue Mar 10, 2023 · 0 comments
Open

Time / Date information for std-ified gems? #19

rubyFeedback opened this issue Mar 10, 2023 · 0 comments

Comments

@rubyFeedback
Copy link

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:

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.

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

No branches or pull requests

1 participant