jordwalke

10 ms·

31.
by jordwalke 8y ago
One recent project which builds a usable layer on top: https://github.com/ostera/httpkit
32.
by jordwalke 8y ago
Let's be a little more specific. "Reason Syntax" is merely a new syntax on OCaml, but ReasonML in general has a much larger scope - which includes every part of the toolchain/workflow up to and including package manageme
33.
Revery: Native ReasonML cross platform UI(github.com)
5 points by jordwalke 8y ago|1 comments
34.
Language Debt(medium.com)
3 points by jordwalke 8y ago|1 comments
35.
by jordwalke 8y ago
Hi, I work on Reason full time and have been managing the reason-cli releases, and I'm happy to say that we're pretty close to not needing reason-cli anymore because the much better alternative is to _avoid_ global installs and in
36.
by jordwalke 8y ago
I asked this question just yesterday. The challenge (the one I was interested in) was if this can be done in a general purpose way for arbitrary programming languages so long as they used libc to go through the file system. I actually think
37.
by jordwalke 8y ago
This is already such a useful part of the Reason/OCaml ecosystem in its current state, and has even more potential longer term. Great work!
38.
by jordwalke 9y ago
The main advantage of building on the OCaml language is that it is possible to totally encapsulate an FFI binding in a way that doesn’t virally infect the code path that calls into it. In pure languages this may not be the case. OCaml is no
39.
by jordwalke 9y ago
I don’t mean to ignore your observation - it is valid. Bsb is a build system that works with a specific form of packages. What you suggest could work too. The only (small?) challenge is that people have bsb JS projects, and they aren’t conf
40.
by jordwalke 9y ago
Thanks for the tip. Also, we are working on making it easier to isolate opam packages and npm packages side by side in one development environment so that problems like this are avoided. This allows you to build a project that depends on op
41.
by jordwalke 9y ago
Reason is supported on every major version of the native OCaml compiler (currently versions 4.02.3 up to 4.06).
42.
by jordwalke 9y ago
Hi, I work on Reason: To add to other comments: One thing that ReasonML can do that TypeScript cannot do, is take advantage of the world-class OCaml compiler to generate very fast native executables. If you learn Reason, then you are also a
43.
Learning ReasonML(lucasmreis.github.io)
2 points by jordwalke 9y ago|0 comments
44.
by jordwalke 9y ago
With RC, you might be able to predict when a final reference count goes to zero (though in practice in large apps that might be difficult - I don’t have enough experience) but it doesn’t seem to help you predict the size of the memory graph
45.
by jordwalke 9y ago
I think by “determinism” you mean “predictable” because OCaml’s GC is also deterministic (see Core_Bench benchmarking blog post which shows how you actually need to account for this determinism when benchmarking). You could make the claim t
46.
Does reference counting GC really use less memory than tracing GC(flyingfrogblog.blogspot.com)
9 points by jordwalke 9y ago|4 comments
47.
Apple's CVDisplayLink Doesn't Link to Your Display(thume.ca)
110 points by jordwalke 9y ago|36 comments
48.
by jordwalke 9y ago
This is some solid feedback, thanks for taking the time to write it up. I work on ReasonML, so a lot of this feedback describes problems we’d like to help the OCaml community solve. We are making progress on the popularity front by leveragi
49.
by jordwalke 9y ago
We provide tools to automate the upgrade between any two reason versions. It’s actually pretty trivial to keep up with changes due to refmt.
50.
by jordwalke 9y ago
> “The biggest example I can think of is that OCaml uses let..in, which reminds you that every function is a statement. By contrast, the `;` in Reason hides that fact.” ... Except in OCaml modules/files where you don’t use “in”. OCa
51.
by jordwalke 9y ago
Currently: lexer, and parser, and AST printer (bidirectional parser you could say), with a few lightweight ppx macros included for UI development.
52.
by jordwalke 9y ago
Noted and thank you for the constructive feedback. Various people in the OCaml community are working on some of these and we might contribute to some of these missing pieces as well.
53.
by jordwalke 9y ago
Hi, I’m the original inventor of React and I really like SML, however SML just didn’t have a few of the escape hatches or advanced features that were needed to implement a very usable, extensible, and type safe React interface or implementa
54.
by jordwalke 9y ago
You already have that option. Reason's syntax is for the vast majority of developers that do not prefer OCaml's syntax, the majority of them not being OCaml programmers.
55.
by jordwalke 10y ago
Thanks for the reminder.
56.
by jordwalke 10y ago
We are compatible with 4.03 and 4.04 via opam!
57.
by jordwalke 10y ago
Also note that there are some language features which are surprisingly syntactic - which are well within the scope of Reason : For example, some basic facilities for export/import as well as async transformations. These are all being d
58.
by jordwalke 10y ago
And another interesting thing to note about the approach taken here, is that I did several surveys and interviews that explored why developers choose the languages they do, and there were many cases where people could have (arguably should
59.
by jordwalke 10y ago
I believe so, but IIRC, it's not possible to use it on Real World OCaml. Also, for something as core as a book, it's worth being able to custom tailor some things including the code generation, and some extensions to the book that
60.
by jordwalke 10y ago
Just so we don't miss the opportunity to learn - would you mind stating what you would find valuable in a toolchain for building a server side native system? What kind of things about project management/install appeal to you?

More ›