Pinned Tweet
BuckleScript is Rebranding: reasonml.org/blog/bucklescri…
Reason retweeted
Hello world! rescript-lang.org/blog/new-r…
Reason retweeted
I'm planning to start a video blog to critique iOS apps's UI/UX. It'll be hopefully funny, insightful and packed with trivias. If you'd like to see your app getting r̶o̶a̶s̶t̶e̶d̶ critiqued, gimme a ping or DM!
(No charge, but also no promise)
Reason retweeted
The formatter for the new syntax is available for testing. You can also use it as a way of learning the new syntax, see more details in the post reasonml.chat/t/the-formatte…
Reason retweeted
A Note on BuckleScript's New Syntax and Its Future Support Commitments:
reasonml.org/blog/a-note-on-…
Reason retweeted
Haven't tried it yet but the better error messages alone will help SO MUCH.
Also love that they make a lot of JS interop much easier by putting less syntax around it.
No semicolons are also awesome, seen this trip up so many JS devs.
🏆🤗
Reason retweeted
BuckleScript 8.1 comes with a new syntax option! Please read about it here: reasonml.org/blog/bucklescri…
Reason retweeted
The forthcoming BuckleScript version 8 will be the largest release since the initial open source! The initial goal that make the fastest JS target compiler generate the fastest JS code — an ambitious goal & bold claim will become true.
Reason retweeted
New ReasonReact version released today! Lots of features/fixes, GH issues managed, integration with concurrent @reactjs (createRoot, Suspense, SuspenseList, useTransition).
reasonml.github.io/reason-re…
Work of @rickyvetter + many contributors helping with PRs, issues, docs!
One of the last few unreadable BuckleScript output, the `match` JS variables generated from pattern matching, has now been optimized to be much more pleasant! github.com/BuckleScript/buck…
It's a good time to help people find new opportunities, so the ReasonML Discord server now has a #job-openings channel. Share any Reason job openings that you discover!
discord.gg/P8x4pFw
Here’s an example.
Before: github.com/BuckleScript/buck…
After: gist.github.com/chenglou/b6c…
If you ever use promises for ReasonReact, do it only for interoperability with existing JS code. Don’t use it in new code!
Also, using promise is almost always wrong in your React/ReasonReact component! Since you’ve encouraged not thinking about cancelling them when a component unmounts.
Ever had a mysterious warning where you “set state on an unmounted component”? Now you know where that comes from!
This tweet is unavailable
