[Suggestion/Proposal] Cheatsheet for Ruby? Happy to Contribute!

[robertDurst]

Hey folks. Rubyist here who's knee deep in my first gleam project. Having a fantastic time so far!

Anyway, I noticed that there isn't a Ruby cheatsheet yet.

A few questions:

1. Is this interesting?
2. Is anyone working on this yet?
3. Happy to take the lead! (would love to find a way to contribute and this seems like a good place) Anyone want to collaborate on this?
4. Where would this cheatsheet content live?

Cheers!

[ankddev]

Hey, answering your last question, tutorials live in website repo, mostly in this file. You can use existing cheatsheets as example.

[robertDurst]

Thanks for the pointer!

[GearsDatapacks]

Hello! Thank you for your interest in contributing. Unfortunately, the cheatsheets are in a bit of a sorry state at the moment. They are outdated and incomplete. We would like to improve them and bring them up-to-date before adding new ones, because new ones would also be outdated leading to more work updating them when the time comes.

[robertDurst]

Certainly - makes sense.

Ruby is freshest in my mind (it's what I write during the day) but of the existing cheat sheets, I do have experience in Rust + Python.

Furthermore, as someone interested in getting involved, is this the best place to start? Imagine as an open source community, there's always more to do than people to contribute, so curious where best to spend my time here. For some context, I have past open source experience, am a PL enthusiast, etc.

Cheers and thanks for all you do here!

[lpil]

More work on the cheatsheets would be amazing!

If you're interested in a bit more of a project it'd be good to look past the existing ones and work out what a better cheatsheet page would be like. Some flaws they have at the moment:

• They are incomplete.
• The visual design hasn't been considered, so they're quite hard to read.
• They spend too much time teaching the other language, when the reader doesn't need that information at all.
• Little thought has been put into what content to show in the cheatsheet.
  • Is it the same for every language?
  • Is it trying to cover all the main Gleam features? Or does it instead cover the very basics of the other language and then show how to translate that into Gleam?
  • Is it just syntax, or does it include micro-patterns (e.g. recursive loop helper functions), or common library code (e.g. the list module)?
• They don't link to any resources to learn more about each topic.

I think @graphiteisaac might have some improved visual designs?

If this is something that would interest you then I'd love to work with you on this.

[robertDurst]

Little thought has been put into what content to show in the cheatsheet.

Ahh, yes. My first though is some sort of consistency, checklist, etc. such that for new releases it'd be more systematic to update, maybe baked in to the release process? (forgive me, I am new to this community so learning the ins and outs of how y'all function).

They don't link to any resources to learn more about each topic.

yes - great point here

include micro-patterns (e.g. recursive loop helper functions), or common library code (e.g. the list module)

👀 would be interested in this too (ofc an opinion to work through in whatever forum a "standard" for this is discussed). Learning language idioms is challenging as it's easy to just bring your biases from wherever you came from and force them to work. I.E. spent a good amount of time working with a Haskell-er in a Ruby codebase who loved to chat type driven development philosophies 😆. Sure we all have seen this play out at some point.

If this is something that would interest you then I'd love to work with you on this.

Please count me in!

Let me know what you think first steps are to get started. My initial thought is to work through some sort of source of truth to answer Is it trying to cover all the main Gleam features?. In an open source world, where would such an artifact live? I'd propose Github somewhere, but again, I'm new and learning ways of working here 😁 so don't know enough to have a reasonable opinion.

Thanks again for your response here and look forward to contributing!

[robertDurst]

@lpil Dm'd on discord.

Opened a question there as well to solicit collaborators.