jordwalke

17 ms·

1. 91.▲
   by jordwalke 10y ago

   Yeah, if you peak inside the source code, you'll see we've implemented a `Reason` binding to the `Atom` JS plugin API.
2. 92.▲
   by jordwalke 10y ago

   Jordan here (I work on Reason) I've mentioned elsewhere that the primary goal for now was to get the tooling automated as much as possible, so that when we receive common feedback, we can adapt to that feedback and trivially migrate pe
3. 93.▲
   by jordwalke 10y ago

   Thanks evincarofautumn! I'll take a look.
4. 94.▲
   by jordwalke 10y ago

   For now: - Teaching new programmers how to use ML, and OCaml in particular. - Keeping consistent formatting rules among a large team or project and automating that within your editor. - Benefiting from the comprehensive pattern matching che
5. 95.▲
   by jordwalke 10y ago

   What cheng said, but we could also make sure that the syntax for modular implicits plays very nicely with the rest of the grammar. With Reason we can rethink the grammar holistically instead of having to find room in it for new features. Th
6. 96.▲
   by jordwalke 10y ago

   Fixed, thank you @konschubert.
7. 97.▲
   by jordwalke 10y ago

   Interop with OCaml is perfect and should remain so. ppx should work (modulo issues that we're not aware of). You can even upgrade your existing OCaml source code to be in the Reason style by using the versatile `refmt` program that is
8. 98.▲
   by jordwalke 10y ago

   The Atom Reason plugin uses Nuclide's system for error rendering (in the diagnostics bar), and type hints. But the actual logic for integrating with Merlin has been completely rewritten in Reason itself, and compiled from Reason into J
9. 99.▲
   by jordwalke 10y ago

   Facebook has many projects that are already written in OCaml, and Reason provides a path forward for seamlessly, and incrementally moving projects over to the new syntax/style. Feel free to take a look at some Reason in the wild, used
10. 100.▲
    by jordwalke 10y ago

    Please take a look at the FAQ which describes the best way to move forward with evolving the syntax. It helps to know your personal technical background and where you're coming from, as well. I do like your idea, but you can currently
11. 101.▲
    by jordwalke 10y ago

    Cheng Lou fixed the firefox issue. Refresh and it should be fixed. Thanks again for reporting.
12. 102.▲
    by jordwalke 10y ago

    We just discovered the same by disabling the media query which handles the shadow. Thank you very much for investigating.
13. 103.▲
    by jordwalke 10y ago

    See the FAQ, as this is a fairly anticipated question. There's some benefits to having some token to separate let bindings and statements, so that the grammar is unambiguous, and it doesn't matter too much which token is used (m
14. 104.▲
    by jordwalke 10y ago

    Thanks for the thoughts. I would definitely not call Reason a new language, but rather a new interface to an existing language that is already great. Not all languages make it easy to provide such an interface, but OCaml did, and the timing
15. 105.▲
    by jordwalke 10y ago

    Thanks, we're looking into how to fix the perf in FF. Meanwhile, it works on my tiny mobile cell phone.
16. 106.▲
    by jordwalke 10y ago

    For now, that's somewhat accurate. If you check out the JS comparison page, you might say it looks like JS with OCaml's influence. The point of the syntax toolchain is actually not to get it right on the first try but to make some
17. 107.▲
    by jordwalke 10y ago

    Thanks there's some strange font rendering issues. Will fix! edit: now fixed.
18. 108.▲
    by jordwalke 10y ago

    Sounds like FF can't handle gifs, but Chrome/Safari do a good job. I've disabled the gif on the main page just to be friendly to FF while I figure out a better approach. Thanks for the report.
19. 109.▲
    by jordwalke 10y ago

    Chrome and Safari both worked for me. Common reports about Firefox, so I disabled the gif. Can you let me know if it works now?
20. 110.▲
    by jordwalke 10y ago

    Pretty sure it was the gif. I've disabled it. Could you try again?
21. 111.▲
    by jordwalke 10y ago

    Note that multicore includes two separate "features": the algebraic effects abstractions, and the multi-core runtime (domain heaps). From what I understand, OCaml's multi-core effort will include both of these as well as some
22. 112.▲
    by jordwalke 11y ago

    It's not incredibly advanced: It mostly just consists of measuring where exactly the current text box is in the scroll view, how high the text box is, and then having the scroll view scroll to that location, followed by fading in a doc
23. 113.▲
    by jordwalke 11y ago

    I've implemented one solution to this in FB's Groups App. Try that experience out and let me know what you think. Also, Nick Lockwood should comment here.
24. 114.▲
    by jordwalke 11y ago

    Here are some things that make ML (and OCaml in particular) a desirable language for mobile development. 1. Sound, static typing prevents entire classes of errors. This becomes even more important when you are shipping an irrevocable binary
25. 115.▲
    by jordwalke 11y ago

    The article divides programming languages into two groups: Those that require you to manage memory manually and those that rely on language level managed memory. However, the examples of the managed memory languages also rely on language le
26. 116.▲
    by jordwalke 11y ago

    This article conflates two separate issues: Automatic memory management, and Virtual Machine runtimes. People often make the mistake of thinking that some sort of garbage collection strategy (such as reference counting[1] collection (ARC) o
27. 117.▲
    by jordwalke 11y ago

    Question for hongboz and Drup about F-lambda: OCamlScript does some cross-module optimization it seems. That's really cool, and js_of_ocaml does several optimizations as well, but for both approaches, it seems we'll not be able to
28. 118.▲
    by jordwalke 11y ago

    It would be great to see a list of known/anticipated compatibility issues. For example, I notice that when compiling `String.set` with OCamlScript, the generated JS ends up trying to set/mutate a character in the JS string, which
29. 119.▲
    by jordwalke 11y ago

    Before that, I'd ask if the implementation of OCaml's map is at all similar to the implementation of Immutable.js's Map. Different internal data structures/algorithms are probably the most likely explanation for any diff
30. 120.▲
    by jordwalke 11y ago

    Drup: Also, if it wasn't abundantly clear (to you or others) - I believe js_of_ocaml to be perhaps the best systems language compile-to-js toolchain that I've ever discovered (and I've looked extensively for others) - so I ho