Skip to content

Guide ideas #1033

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

Open
fhammerschmidt opened this issue May 7, 2025 · 6 comments
Open

Guide ideas #1033

fhammerschmidt opened this issue May 7, 2025 · 6 comments

Comments

@fhammerschmidt
Copy link
Member

We need more guides for people to get an idea what one can do with the language.

Some examples:

  • Fullstack examples with API type-sharing thanks to JSON schema and Sury
    • Rust Actix Web
    • Java Spring
    • ...
  • A simple server with Deno
  • A vanilla JS project with the new experimental web bindings
  • Something with rescript-relay
  • Something with EdgeDB

Please add your ideas here!

@zth
Copy link
Collaborator

zth commented May 7, 2025

High and low here (we should probably consolidate these after we have a large pool):

  • Ecosystem
    • Using Postgres with ReScript
    • Building GraphQL servers
    • Using Bun
    • Using Node
    • Using DOM with webapi
    • Using Gel (EdgeDB)
    • ReScript and OpenAPI
    • JSON serialization/deserialization with Spice
  • Language
    • Decoding strings typesafely
    • JSON serialization/deserialization with raw ReScript
    • Abstract types
    • Error handling with polymorphic variants

@cknitt
Copy link
Member

cknitt commented May 7, 2025

React Native! 🙂

@nojaf
Copy link
Contributor

nojaf commented May 7, 2025

I believe that every example involving bindings should focus on creating minimal bindings from scratch. While this might discourage some users due to the absence of a large library like TypeScript, it serves as a helpful reality check. Utilizing bindings that aren't maintained by the core team feels risky, and I would not recommend it. Therefore, I suggest including the creation of bindings in the recipe whenever needed. We do have a short list of exceptions for well-maintained options.

@zth
Copy link
Collaborator

zth commented May 7, 2025

To me bindings is a separate thing that we should have guides for as well. But I think it's a bad idea to focus on it in every single guide that deals with the outside world. To me it'd be like recapping every language feature used in every guide as well - also doesn't make sense and just becomes repetitive. But, we can certainly do guides on bindings and then link to them wherever it makes sense.

Using community bindings is totally fine and I'd happily recommend it. I use a ton of them in production already. Not sure why it wouldn't be?

@nojaf
Copy link
Contributor

nojaf commented May 7, 2025

Using community bindings is totally fine and I'd happily recommend it.

That is not my experience at all. As a v12-only user, I've encountered issues with older bindings. If something is missing, you need to submit a PR, which can feel like shouting into the void. A guide or link to patching is essential. I wouldn't describe it as recapping; it feels more like a necessary step.

@zth
Copy link
Collaborator

zth commented May 7, 2025

V12 is in alpha still. That the community hasn't caught up is expected.

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

4 participants