Cheatsheets / Guides for users from other languages

[inoas]

• C
• C#
• C++
• Clojure
• Dart
• Elixir - https://gleam.run/cheatsheets/gleam-for-elixir-users
• Elm - https://gleam.run/cheatsheets/gleam-for-elm-users
• Erlang - https://gleam.run/cheatsheets/gleam-for-erlang-users
• F#
• Go - Create gleam-for-go-users guide #321
• Haskell
• Java
• JavaScript - Add JavaScript cheatsheet #274
• Kotlin
• Lua
• OCaml
• PHP - https://gleam.run/cheatsheets/gleam-for-php-users
• Python - https://gleam.run/cheatsheets/gleam-for-python-users
• Racket
• Ruby
• Rust - https://gleam.run/cheatsheets/gleam-for-rust-users
• Scala - first pass at cheatsheet for scala #348
• Swift
• TypeScript - Add TypeScript cheatsheet #355

[inoas]

I have compiled the above list from a mix of most frequently used languages: https://www.statista.com/statistics/793628/worldwide-developer-survey-most-used-languages/ and languages from the functional programming realm.

• Which one would be missing?
• Which one would you not add (or remove from above list) even if there was a contributor creating them?

[lpil]

It would be good to make some more structured way of making these, to ensure they all cover the same topics. How could we do that?

[inoas]

Write a small gleam app and maintain the topics in that app via git and let users contribute via a web interface? If it is file based we can merge back the changes to upstream?

[inoas]

One note:

to ensure they all cover the same topics

I am also doubtful that exactly the same topics is always good idea.

I think there should be a shared core but then there are topics where it is worth to explain specific differences between A and gleam but not between B and gleam.

[lpil]

Editing via GitHub is fine, the authors will be programmers. More I want them all to cover the same basic topics as a minimum, and I want it to be easy to see what topics are unfinished.

[inoas]

Maybe a small gleam application?