Lispers here, cackling with their S-expressions, listening to other languages complain about being unsure where a statement/expression ends.
As a non-lisper, it always kind of amused me that vi had brace-detection in the % command. I mean, what self-respecting C coder doesn't know where the other bracket is.. oh wait. ok. That's useful for me.
Then you wind up in emacs, editing a .emacsrc file, marvelling at the .. depth of germanic (((( ... things) which need to be said)) by this person) nesting.. wondering what you do...
Yeah I understand why F# has whitespace indentation now - it resolves these ambiguities in OCaml without adding a bunch of new keywords.
> Interesting to read about semicolons improving comprehension -it felt like it had been decades since somebody had the courage to say so. (That said I write python un functionally and so am 4space tabbed to the max)
I think it has a lot to do with the writer not using blocks. It would solve both of their issues (with match and with if and semi-colons which is actually an issue of precedence) Some people seem to have a lot of trouble with the BCPL/Pascal syntax using begin and end.
The author apparently doesn't know about "|>" either which would solve their sequencing issues.
At least this post was written in good faith. I think this highlights that there is a dearth of recent material promoting best practices when it comes to Ocaml.
Interesting to read about semicolons improving comprehension -it felt like it had been decades since somebody had the courage to say so. (That said I write python un functionally and so am 4space tabbed to the max)
It's also the first time I've seen "currying is bad" which seems to run against the flow of salmon.