Join the conversation

Sign in to join this conversation, and others like it, in the communities you care about.

Reason

Reason lets you write simple, fast and quality type safe code while leveraging both the JavaScript & OCaml ecosystems.

Reason / General

What are you using Reason for?

What are you using Reason for?

Reason / General · November 16, 2017 at 7:08pm
Curious what y'all are building with ReasonML. Mobile apps? Web apps? Show off your creations!

November 16, 2017 at 7:11pm

Stating what you already know, Max 😉, but to get this conversation going, I’m working on a CSS (-in-JS) parser that takes interpolations into account, and outputs an optimised & flat format called ISTF for projects like styled-components and others https://github.com/cssinjs/istf-spec

like-fill
3
  • reply
  • like

And languages with a sound & type system and pattern matching are perfect for that job ✨

like-fill
1
  • reply
  • like

So far I have one non critical google cloud function written in Reason. I’m hoping to get some Reason into our main React site at openlearning.com soon, and spreading out from there

like-fill
2
  • reply
  • like

I recently rewrote the word import cleanup process of our TinyMCE powerpaste plugin in reason. We're hoping to expand reason to open source areas of the editor soon :D

https://store.ephox.com/products/powerpaste/

like-fill
2
  • reply
  • like

November 18, 2017 at 11:05pm

@spyder@spyder Just out of curiosity, since it's all javascript in the end, doesn't every site that uses that plugin have to ship some form of the source, anyways? A compiled version, perhaps, but some source regardless. It's an interesting business model selling plugins like that. I've been selling support for fully open source projects and it has been working out pretty well for me. I'm intending to write new projects in reason with react.

  • reply
  • like

Not sure why that is showing the name twice.

  • reply
  • like

November 27, 2017 at 12:13am

@zploskey I leave most of those concerns to marketing ;)

Yes technically with JS even when compiled the source is available, but minification makes it mostly unreadable and commercial entities aren't going to risk using unlicensed software.

  • reply
  • like

December 8, 2017 at 4:36pm

I'm working on an Expo app and I'm slowly adding Reason to it so I can get to know the language and its tooling better

like-fill
2
  • reply
  • like

@fiber-god how'd you make that work?!

like-fill
1
  • reply
  • like

@mxstbr If I'm thinking of this correctly one could just run bsb's watch task alongside the normal packager and create an index file pointing to the compiled Reason js files :) but actually there's also this: https://github.com/react-community/reason-react-native-scripts

like-fill
1
  • reply
  • like

Ohhh noice, that makes

  • reply
  • like

I wrote a little blessed terminal for displaying the concurrent bsb and exp watches, and in the bucklescript config i'm targeting my js source folders directly so i can use reason along my JS more easily

like-fill
1
  • reply
  • like
/* Importing a js based styled-component into my Reason React Native component */
module Label = {
[@bs.module "./styled/Label"] external label : ReasonReact.reactClass = "default";
let make = (children) =>
ReasonReact.wrapJsForReason(~reactClass=label, ~props=Js.Obj.empty(), children);
};
  • reply
  • like
like-fill
1
  • reply
  • like

December 14, 2017 at 10:53pm

Writing a compiler for Flow libdefs to BuckleScript bindings in native Reason 😄

like-fill
3
  • reply
  • like

@rrdelaney I've been waiting eagerly for sth like this :O

  • reply
  • like

July 6, 2018 at 4:20am

@rrdelaney any chance for reasonml types to flow types as we start replacing some of our application with reason and want some type safety with it as we use our reason generated code in other js files

  • reply
  • like
Your message here...

*bold*_italic_`code````codeblock```