spyder81

6 ms·

1.
by spyder81 6y ago
It was never official, and the people behind it folded into the new ReScript team.
2.
by spyder81 6y ago
"readable output" isn't really about being human-readable, except in unrealistic example cases. The bigger benefit is shared data types; this helps immensely with JS interop. https://rescript-lang.org/docs&#x2
3.
by spyder81 6y ago
ReasonML is, as it has always been, a 100% syntax map to OCaml. It will always be that, but moving forward it will be nothing more than that. Compiling future ReasonML versions to JS will require js_of_ocaml. The success of BuckleScript mea
4.
by spyder81 6y ago
It's still on 4.06, I think in 2021 they're targeting an upgrade (they haven't said how far forward they will upgrade to)
5.
by spyder81 6y ago
Quite the opposite, Reason v4 looks to be taking inspiration from the changes ReScript has made.
6.
by spyder81 6y ago
ReasonML isn't dead, but the way I heard the story it has always been a spare time project not a properly funded FB team. There was just enough spare time early on to get the community excited. From the same source, I heard ReScript do
7.
by spyder81 6y ago
The TinyMCE team is building a big new feature with it https://www.tiny.cloud/blog/tinymce-reasonml/ We aren't sure when we will be able to open source the new model, and we are still using Reason syntax with
8.
by spyder81 6y ago
IMO this isn't about whether ReScript wants to upstream their changes, it's a combination of things: - Reason+BuckleScript was confusing at best, having two websites and different release schedules. - Reason's goal is to be a
9.
by spyder81 6y ago
You might have been able to use the same syntax before, but writing code for Reason native was already very different to writing Reason+BuckleScript for the browser. This just formalises the split. To write the same code for both front and
10.
TinyMCE Is Using ReasonML(tiny.cloud)
12 points by spyder81 6y ago|0 comments
11.
by spyder81 6y ago
The standard compiler can do a cold compile of a single file in milliseconds. When the compiler is that fast you _can_ just wrap it up and it'll still be faster than TypeScript. But to answer your actual question: The current standard
12.
by spyder81 7y ago
This is the second post in a series, discussion from the first post: https://news.ycombinator.com/item?id=22039950
13.
Real-Time collaboration in TinyMCE with Slate.js(tiny.cloud)
10 points by spyder81 7y ago|1 comments
14.
by spyder81 7y ago
It's hard to offer more detail than that in a blog post. I'm not going to repeat the research papers or write one of my own. The post is already so long and complex, covering so many surface details, I couldn't reasonably pus
15.
by spyder81 7y ago
User experience is definitely why we didn't go for an existing CRDT solution. The model we've chosen is fairly agnostic to whether OT or CRDT is used to collaborate, as I'll expand on in the second post, so if we see an oppor
16.
by spyder81 7y ago
atomic elements doesn't really extend to arbitrary HTML, which is fine for the simpler editing solutions but not TinyMCE. To do something like that in arbitrary HTML you wind up locking at the top-level-block boundaries. Locking sounds
17.
by spyder81 7y ago
It is, as I'll cover in the second post ;)
18.
by spyder81 7y ago
I haven't! This is what our server team is looking at as an option for encrypting our RTC traffic. https://tweetnacl.js.org/ https://github.com/dchest/tweetnacl-js/wiki/Examples
19.
by spyder81 7y ago
It's not impossible, particularly in cases where the model is fairly flat. In complex models it is symptomatic of a larger issue with complexity in CRDTs; the post was already quite long and I didn't want to repeat any more of the
20.
by spyder81 7y ago
I wasn't really trying to say OT is better than CRDT. Nor was I intending to provide a complete detailed explanation (there's enough research already). I was driving at CRDT not being capable enough for arbitrary HTML structures,
21.
by spyder81 7y ago
I'm a big fan of Automerge, I look forward to where the research takes it!
22.
by spyder81 7y ago
I've been given advice that ShareDB is "pretty antiquated and not well supported". I'm told it is not difficult to rewrite in modern NodeJS, replacing things like callbacks and event emitters with async/await produc
23.
by spyder81 7y ago
I'll cover this in the second post but we will be using ShareDB for our initial launch (although probably building our own once we hit production release).
24.
by spyder81 7y ago
I definitely read a few of your posts during my research, thanks for your hard work :) The best CRDTs do treat each character separately (as I think I mentioned at one point?). But not all of them - the video and my example is an example of
25.
by spyder81 7y ago
That's included in my research links, yes :D
26.
by spyder81 7y ago
The second post will cover which editor model we chose, and talk a little bit about the OT implementation details ;)
27.
by spyder81 7y ago
We're using property-based testing where we can, which I hope to cover in a future post
28.
by spyder81 9y ago
"Then I remembered reading something long ago" is when experienced programmers are worth their weight in gold.
29.
by spyder81 12y ago
In the presence of laziness, it can be very difficult to reason about what code executes when. When you don't know when your unsafe IO happens, things can get out of order or have other unforeseen side effects.
30.
by spyder81 12y ago
That's exactly why most FP articles and tutorials around the net didn't help me, but Dan Grossman's "programming languages" coursera course did. If (when) I ever learn enough to talk about why OCaml is better in det

More ›