# Improve Crystal's profile on Rosetta Code

**URL:** <https://forum.crystal-lang.org/t/improve-crystals-profile-on-rosetta-code/513>\
**Category:** Community\
**Created:** [March 4, 2019, 10:27pm UTC](https://forum.crystal-lang.org/t/improve-crystals-profile-on-rosetta-code/513 "2019-03-04T22:27:18Z")\
**Posts on this page:** 1\
**Showing post:** 62

<div class="post-metadata">

**Author:** ![jzakiya](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/jzakiya/32/278_2.png) [@jzakiya](https://forum.crystal-lang.org/u/jzakiya)\
**Post date:** [April 20, 2020, 4:19pm UTC](https://forum.crystal-lang.org/t/improve-crystals-profile-on-rosetta-code/513/62 "2020-04-20T16:19:14Z")

</div>

> [@jhass](#):
>
> There’s [Crystal for Rubyists · crystal-lang/crystal Wiki · GitHub](https://github.com/crystal-lang/crystal/wiki/Crystal-for-Rubyists), but I think nobody keeps that up-to-date.

You’re right. It hasn’t been updated for either Ruby or Crystal.

> [@jhass](#):
>
> In Ruby `lambda` is just a `Proc` that behaves a bit differently in some aspects. In Crystal we never had the need for those distinctions, so there’s just `Proc` . Also Ruby does actually provide a quite similar syntax to define a lambda proc, the “stabby lambda”: `->(x) { x + 1 }` .

I don’t want to change this thread to about documentation (keep it about Rosetta Code) so I’ll make a last comment here about Crystal documentation.

I spent almost 3 hrs before giving up because of deficiencies in website ref docs. Ruby’s std docs, in contrast, are more detailed, and more people write about its features/nuances.

> **[Class: Proc (Ruby 2.7.1)](https://ruby-doc.org/core-2.7.1/Proc.html)**
>
> Class : Proc - Ruby 2.7.1

> **[What is Difference between Ruby Blocks, Procs and Lambdas](https://medium.com/podiihq/ruby-blocks-procs-and-lambdas-bb6233f68843)**
>
> Having a problem understanding the difference between ruby blocks, procs and lamdas. What are blocks? What is the difference between procs…

> **[Closures in Ruby: Blocks, Procs and Lambdas
 | AppSignal Blog](https://blog.appsignal.com/2018/09/04/ruby-magic-closures-in-ruby-blocks-procs-and-lambdas.html)**
>
> In Ruby Magic we love to dive into the magic behind the things we use every day to understand how they work. In this edition, we’ll explore the differences between blocks, procs and lambdas.

I’ve been encouraging the devs to **TAKE THE TIME** to at least write regular blog entries on the website on small issues like this, to document these things in at least one location for users.

For example, I’m really impressed with the quality and breadth of the `Sidef` language and documentation, which I hadn’t even heard of until Rosetta Code exposure.

> **[GitHub - trizen/sidef: A modern object-oriented programming language...](https://github.com/trizen/sidef)**
>
> A modern object-oriented programming language implemented in Perl. - GitHub - trizen/sidef: A modern object-oriented programming language implemented in Perl.

> **[Introduction | The Sidef programming language](https://trizen.gitbooks.io/sidef-lang/content/)**
>
> This book is a full description of the Sidef programming language.
> Github: https://github.com/trizen/sidef

Again, I don’t want to hijack this thread away from Rosetta Code. If there’s an existing one dedicated to documentation I can contribute these point there, but good documentation is essential to enable users to come up to speed fast. Lastly, here are some helpful resources.

> **[Documentation](https://opensource.com/tags/documentation)**
>
> Good documentation—including installation guides, user guides, white papers, FAQs, and more—provides users a roadmap to using software and hardware. Our articles focus on giving open source project creators ways to improve the quality and usefulness...

> **[How to write effective documentation for your open source project](https://opensource.com/article/20/3/documentation)**
>
> Unfortunately, good code won't speak for itself.

---

_[View the full topic](https://forum.crystal-lang.org/t/improve-crystals-profile-on-rosetta-code/513)._
