Reason Conf 2018

Keynote

• Sat, Jan 1, 10:00 - 10:45

The talk introduces ReasonReact and the way it operates on the state of React components. This is illustrated by introducing the notion of local state presented via a series of examples. State is changed by means of reducers, that can operate directly on the current component, or on distant components via remote actions. Further examples illustrate how certain animations can be considered instances of local state that can be easily composed.

• Sat, Jan 1, 11:15 - 12:00

Tech has a diversity problem: marginalised people are being pushed out of the industry; their voices and experiences are erased. Open Source is particularly bad, with too few contributors who aren’t white, male, cisgender and able-bodied. What if things were different? What if we could create spaces that are welcoming, where we show empathy and compassion? What if those qualities could reflect in our work, ultimately helping us create better software? In this talk, you will hear stories of first-time contributions, successful examples in supporting...

• Sat, Jan 1, 12:00 - 12:45

In this talk we go beyond syntax and look at an experimental webassembly backend for OCaml / ReasonML.

• Sat, Jan 1, 14:15 - 15:00

We will review the current state of the IDE tooling for Reason:

• Sat, Jan 1, 15:00 - 15:15

Bringing new technologies to large-scale enterprises is a challenge in which we are involved quite often. In this talk we will reflect on our current experience with Reason based on a real implementation.

• Sat, Jan 1, 15:15 - 15:30

F# has been a powerful language based on OCaml without mainstream adoption. Let’s discuss their differences.

• Sat, Jan 1, 15:30 - 15:45

Today every major language has some kind of library that helps a developer formatting his or her code. Tools like Prettier, Gofmt and Refmt are setting new standards and have a deep impact on our day to day programming. But what does it actually mean to format code? Does it mean pressing a magical button to align your code? Is it more than the automatic insertion of trailing commas your colleague always seems to forget? Why are we even doing it? How is it going to impact us as programmers to get better? “Code formatting” is an opaque ocean, we’ve done a really poor job at explaining what code formatting actually...

• Sat, Jan 1, 15:45 - 16:00

Traditionally, soundly typed-language are warm and cozy in their own world, but as soon as they have to deal with the outside world (say, talking to a REST API), the pain quickly sets in: trying to keep a type definition in sync with a moving external service, manual conversion back and forth, and lots of boilerplate. Well no more! Proper GraphQL support in ReasonML libraries means that we can have full-stack safety, knowing that if our programs compile, the server can satisfy our requirements! And on top of that, we get all the other...

• Sat, Jan 1, 16:30 - 17:15

Reason community is growing rapidly, and a lot of people are interested in leveraging it on their servers. One way to achieve this is to use native OCaml compiler. It produces exceptionally performant binaries, but the native ecosystem is scarce, and you will struggle with finding solutions for very common tasks. Another option is to use BuckleScript and compile everything to JavaScript. You would regain access to the vast Node.js ecosystem but would have to sacrifice performance. It seems that you have to choose either ecosystem or...

• Sat, Jan 1, 17:15 - 18:00

Even though Reason looks like JavaScript with a few additional functional features and semantics, it’s sometimes easy to forget that it’s a completely different language, with different problems. This talk looks at life on the bleeding edge, as experienced by a not-so-functional programmer.

• Sat, Jan 1, 18:30 - 19:15

Would you rather have a community like npm, where there are hundreds of thousands of packages, but very few feel stable, or one like opam, with only a few thousand packages and a much more rigorous vetting system? How do language and community decisions affect the pull between security and freedom, safety and agility? Can we design a system that gives us both? Come learn about how tools, language features, and community structures all impact the “feel” of a developer community, and what tricks Reason could borrow from other communities to ensure that we can have freedom to publish without fearing change.

• Sat, Jan 1, 19:15 - 20:00