gleam-lang
Cheatsheets / Guides for users from other languages
- [ ] C
- [ ] C#
- [ ] C++
- [ ] Clojure
- [ ] Dart
- [x] Elixir - https://gleam.run/cheatsheets/gleam-for-elixir-users
- [x] Elm - https://gleam.run/cheatsheets/gleam-for-elm-users
- [x] Erlang - https://gleam.run/cheatsheets/gleam-for-erlang-users
- [ ] F#
- [ ] Go - https://github.com/gleam-lang/website/pull/321
- [ ] Haskell
- [ ] Java
- [ ] JavaScript - https://github.com/gleam-lang/website/pull/274
- [ ] Kotlin
- [ ] Lua
- [ ] OCaml
- [x] PHP - https://gleam.run/cheatsheets/gleam-for-php-users
- [x] Python - https://gleam.run/cheatsheets/gleam-for-python-users
- [ ] Racket
- [ ] Ruby
- [x] Rust - https://gleam.run/cheatsheets/gleam-for-rust-users
- [ ] Scala - https://github.com/gleam-lang/website/pull/348
- [ ] Swift
- [ ] TypeScript - https://github.com/gleam-lang/website/pull/355
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?
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?
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?
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.
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.