a0

5 ms·

1.
Docker pull implemented with multicore OCaml(twitter.com)
3 points by a0 3y ago|0 comments
2.
On OCaml and the JavaScript Platform(anmonteiro.com)
11 points by a0 6y ago|0 comments
3.
by a0 7y ago
I think I don't mind lack types as much in immutable languages. Clojure and Erlang are like that. But they're also both simple languages with simple semantics. One issue I have with Clojure is when I have to work with nested datat
4.
by a0 7y ago
> Common reaction from them I receive very often "We never knew that JS/TS can do that" Maybe it's about what you cannot do in ReasonML, and not about what you can do in TypeScript? :)
5.
by a0 7y ago
One problem with people selling ReasonML's type inference is that it's not depicting the actual developer experience. The first thing to note is that you do interact with types to build a mental model! The editor will show them to
6.
by a0 7y ago
ClojureScript is beautiful! If only it had types :)
7.
by a0 7y ago
Being a Vim/Merlin user I normally just type `<Leader>t` to see the type of the value under the cursor (this maps to `:MerlinTypeOf` if I recall correctly). What I do use type annotations for is debugging. If the compiler finds a
8.
by a0 7y ago
There was a workshop at the last ReasonLDN meetup. Here are the slides that were used, they include quickstart instructions: https://docs.google.com/presentation/d/1wuAveSHslRfKShD6SiVd... If I recall correctly, e
9.
by a0 7y ago
One place where clean build times do matter is in the CI. Having very fast builds and tests is great for speedy deployments.
10.
by a0 7y ago
This kind of comments make me really sad. Most ReasonML developers are actually "JavaScript developers". ReasonML was specifically designed for JavaScript developers. Being JavaScript-friendly is in it's DNA really. I even se
11.
by a0 7y ago
Many interesting points! :) > Why do people care about this? Writing type annotations is not that much work (...) I personally care about this when I'm prototyping something. Not having to write types means that I can simply write w
12.
by a0 7y ago
It's ok. There's pretty good support for linting and code completion. The plugins are fast and have a rich feature set. Take a look at this: https://marketplace.visualstudio.com/items?itemName=jaredly.... The only
13.
by a0 7y ago
Many modern languages support type inference to some degree. The special thing about ReasonML is that the type inference is much more robust and complete. In practice you don't need to provide any types annotations at all at any point
14.
by a0 8y ago
WASM currently does not have a GC but that's precisely why one is needed. Languages that target WASM need to implement their own GC but there's already a proposal to integrate a GC implementation into WASM[1]. [1]: https:/&#
15.
by a0 8y ago
In principle it seems like a significant limitation but in practice it is rarely an issue. ReasonML does support parametric polymorphism so it is still possible to write generic code. Some language features conveniently help to avoid boiler
16.
by a0 8y ago
I used OCaml in production for a 2 years and it was a very pleasant experience. Recently I started using ReasonML at my team to implement a Kubernetes configuration tool. It’s surprisingly easy to use ReasonML for backend development with d
17.
by a0 8y ago
Great seeing more apps being built in Reason! How was your experience with it?
18.
by a0 8y ago
I think implementing a Go backend for Reason would be a better approach. Existing libraries, could be reused and it would be easier for people familiar with Reason/OCaml to learn the language.
19.
by a0 8y ago
There’s also a desicated list for ReasonML now: https://github.com/vramana/awesome-reasonml
20.
by a0 8y ago
This is a brilliant tool that fully shows the potential that Reason/OCaml provide as a platform. Good job!
21.
by a0 8y ago
For everyone interested in learning OCaml, there's a very active Discord community where you can ask questions: https://discord.gg/ZBgYuvR Join and say "hi"! :)
22.
by a0 8y ago
If you want something closer to Rust, consider looking into Reason. It’s essentially OCaml with braces and semicolons.
23.
by a0 8y ago
Single-process concurrency is great in OCaml. It’s flexible and composable with libraries like Lwt and Async. On the other hand true multicore backend is where the most work is moment. For the latest update on that see: https://
24.
by a0 8y ago
This is such a great book. OCaml’s type system feels like a superpower specially in the context of Unix development which is traditionally done in C.
25.
by a0 8y ago
The most unique feature is the type system which allows you to both model domain problems effectively and guarantee consistency. This reduces a huge number of bugs in compile-time.
26.
by a0 8y ago
Syntax errors are suboptimal. They are usually reported at correct location and it's relatively easy to spot them. On the other hand type error messages are simply awesome.
27.
by a0 8y ago
It's really great seeing this contributions from JaneStreet. If you're interested in learning more about recent progress in the OCaml's ecosystem, I recommend watching this talk: https://www.infoq.com/presenta
28.
OCaml for the impatient(adambard.com)
21 points by a0 9y ago|0 comments
29.
by a0 9y ago
There’s a beginner’s guide to OCaml’s beginner’s guides: http://blog.nullspace.io/beginners-guide-to-ocaml-beginners-...
30.
Stream Processing with Coroutines (from C to OCaml)(pusher.com)
7 points by a0 9y ago|0 comments

More ›