@iyalei right?! Actually I think it's just comforts and the false promises of being able to hack something together quickly that infect all of the imperative programming world. You have to remember a lot of JavaScript folks learned C or Java first, or were trained by others who did.
I wish we could bring #FlowType back too but Facebook gave up on it to build #ReasonML and since there are #Rust UI frameworks now we might as well fall forward to coding in a proper ML with real type safety 😂
@oriSomething Slow compilation is extremely difficult for good web development. The incremental compilation speed in OCaml is very very very very good. Anyway it just tickles my interest, I've been very distant from #reasonml ever since I touched Rust but I have a warm place for it in my heart 😁
@wfaler #ReasonML looked interesting - then kinda forked to #ReScript (https://rescript-lang.org - which is just the buckle script layer) and it’s direction got confusing from the outside.
Maybe I should just start looking at #FSharp and .NET
I think that #TypeScript is going to herald a great new era of different languages targeting JavaScript as a transpile target. I loved #ReasonML, but the rift into #ReScript seems to have basically killed it. But perhaps more than anything, I am hoping that the normalization of the transpile process will accelerate acceptance and growth of #WebAssembly. We're already not writing real JavaScript.
#typescript #reasonml #rescript #webassembly
I think that #TypeScript is going to herald a great new era of different languages targeting JavaScript as a transpile target. I loved #ReasonML, but the rift into #ReScript seems to have basically killed it. But perhaps more than anything, I am hoping that the normalization of the transpile process will accelerate acceptance and growth of #WebAssembly. We're already not writing real JavaScript.
#typescript #reasonml #rescript #webassembly
@sbr #ocaml have a lot of use cases, it have great support to build compilers (it was used to build #rust). It's used by #mirageos and multiple other cool projects. It can be used to do frontend application with #reasonml or ocaml_of_js. OCaml can build rest APIs and much more... http://ocamlverse.net/content/ecosystem.html
#ocaml #rust #mirageos #reasonml
@sbr I once had this idea to build an app to record and host podcasts from the web itself using WebRTC.
Managed to get a WebRTC client with recording working and all done with #ReasonML and #ReasonReact and it was all probably in the same year.
@nflamel yes! I was playing around with it in 2019. I even wrote a few blog posts on dev.to about it and held a meetup talk. Very helpful and friendly community.
But I didn't have any real use-case for #ReasonML and the split between ReasonML and #Rescript was confusing. I think the community lost momentum with wider adoption due to the split, although I understand that it wasn't an easy decision.
@sbr I was once really, really, really hyped with #ReasonML https://reasonml.github.io/ but never ended up using it for real... although I know it has some real users, like https://v2.onivim.io/ for example.
And there's also https://reasonml.github.io/reason-react/, which is cool.
And it is all based in #OCaml
What I like about #Svelte is that it works with #RxJS out of the box. It's no fluff and easy to get started with.
What I like about #SolidJS is that it's reactivity that makes sense.
What I like about #Angular is that it works great with teams and has a rock-solid architecture, forces me to use #TypeScript, plus #RxJs .
btw:
I'm still sad about #ReasonML - I liked that a lot (#OCaml for #Frontend - way better than TS!). But the ecosystem was too small, plus the switch to #ReScript hurt.
#svelte #RxJS #solidjs #angular #typescript #reasonml #ocaml #frontend #ReScript
@rauschma I remember when I added #reasonml to our web project, at first our devops thought it was failing to bundle anything, because it finished in less than a second.
I had to give them a demo that my build system actually outputs and processes input reason files. And not just silently fails and proceeds to next step.
That's what I call blazing fast :)
I just encountered an issue in #revery while working on my “create a text editor in #reasonml “ project where horizontal scroll in ScrollViews is broken [0].
*sigh* Does this mean I have to create my own? That sort of goes against my goals for the project since that would increase the complexity significantly.
I guess I’ll try to fix the problem and submit a PR? Not confident I can actually fix the problem, but it’d definitely reduce complexity for me 😬
I did a thing.
Kakoune (-ish) mode for VSCode. It's just the very basics right now, but I'll keep adding to it while there are things I miss from actual Kakoune.
https://marketplace.visualstudio.com/items?itemName=reykjalin.vscode-kakoune
I've been getting really into #reason lately and I'm quickly falling in love.
Right now I'm following Pailey Quilts' tutorial on writing a text editor [0], but using Reason and #revery instead of C.
I thought this might be of interest to others so I'm writing a tutorial of my own following the shape of Pailey's original guide.
I'm also hoping writing about this will help me actually /finish/ a project this time 😬
Check it out!
https://www.thorlaksson.com/build-your-own-text-editor-with-reason-getting-started/
We’ve been talking about switching to a typed code base for our #react apps at work, and I got the go ahead to reimplement some of the code in #reasonml !
I don’t think we’ll end up choosing Reason over #typescript due to incomplete testing libraries for Reason, but I’m really happy to work in a place where we’re willing to experiment with new technologies 😌
I really hope Reason takes off as a mainstream, typed replacement for JS. The language has great potential.