Live data from Hacker News

Reason: A new interface to OCaml

facebook.github.io

291–294 of 294 posts

Re: Reason: A new interface to OCaml

#291

Earlier quoted context omitted.

This is not correct. You can still auto format just fine. It won't change indentation obviously, since that would change the meaning of the program. What problems do you have in mind? I'm also very skeptical that they make sharing code difficult. Any indentation issues will be readily apparent in a compiled language.[1] Plus I doubt this is a serious issue in the first place. And certainly it doesn't outweigh the mas…

You're right about auto-formatting being possible with significant whitespaces... but: When you copy-paste a block of code in another block of code, with significant whitespace you have to correctly reindenting everything very carefully, while with explicit blocks you can let an automatic formatter do the work. When you copy-paste a block of code in chat/email/comment, it is sometimes difficult to preserve significan…

> When you copy-paste a block of code in another block of code, with significant whitespace you have to correctly reindenting everything very carefully, while with explicit blocks you can let an automatic formatter do the work.

I've heard this argument a lot, but how often does it happen to copy paste extensive parts from web sites? Some short bits, yes, but longer parts with blocks? Almost never, since I always have to rewrite them to fit my variable names etc, so might as well make sure the formatting is right.

Re: Reason: A new interface to OCaml

#292
post #284

Earlier quoted context omitted.

Yes and no, depending on which aspect of the language you consider: - Type system -> OCaml is more modern (despite being designed before Go) - Concurrency, parallelism, garbage collector, tooling -> Go is more modern (Reason is improving the tooling with refmt for example; work is ongoing on parallelism)

Interesting. What's fancy about the Go garbage collector?

As far as I know, there is nothing fancy about it, except for the fact that a lot of work has been put into Go's garbage collector, especially in versions 1.5 and 1.6, with people working full-time on it.

Go easily achieves GC latencies well below 10 ms, even for programs using a large heap, without having to manually "tune" the GC.

https://blog.golang.org/go15gc

https://talks.golang.org/2015/go-gc.pdf

Go 1.5 concurrent garbage collector pacing, https://docs.google.com/document/d/1wmjrocXIWTr1JxU-3EQBI6BK...

Post reply on HN