News for hackers. Stuff that matters.
Re:A deep dive into Multicore OCaml garbage collector by mookid11 on Sunday July 16, 2017 @05:19AM (#14781244)
> Haskell has some nice things going for it. Its syntax is cleaner than OCaml's, for example.

While I find the ocaml syntax very far from perfect, the whitespace sensitivity of Haskell makes it immediately worse. What a silly design.

Re:A deep dive into Multicore OCaml garbage collector by mercurial on Sunday July 16, 2017 @08:04AM (#14781647)
IMHO, it's not so much that as the ASCII operator galore. $, <*>, the horrible lambda syntax... Sometimes it looks an opinionated Perl.
Re:A deep dive into Multicore OCaml garbage collector by ice109 on Sunday July 16, 2017 @09:35AM (#14781915)
I don't know if you've worked with a production Haskell code base but it cannot be over stated what a poor decision operator overloading is. if they got rid of that it would immediately make Haskell an order of magnitude more practical
Re:A deep dive into Multicore OCaml garbage collector by the_why_of_y on Sunday July 16, 2017 @01:55PM (#14783246)
Haskell doesn't really have the problems that are commonly associated with operator overloading.

Haskell does have type classes, which do allow overloading, even of operators, but the type class uniquely determines the type of the operator - and there can be only one definition of any operator in scope.

Also, you can just define as many new operators as you like.

For these reasons, you can't have the madness of operator<< in C++, or whatever it is that Perl does with the same operator doing 5 completely different things depending on context.

Re:A deep dive into Multicore OCaml garbage collector by tom_mellior on Sunday July 16, 2017 @02:51PM (#14783535)
> Haskell doesn't really have the problems that are commonly associated with operator overloading.

Nobody said it did. People said that it has its own brand of problems with operators looking something like >>+@*<>> peppering your code.

Re:A deep dive into Multicore OCaml garbage collector by ice109 on Sunday July 16, 2017 @06:28PM (#14784439)
lol i wonder if you work on my team
Re:A deep dive into Multicore OCaml garbage collector by ice109 on Sunday July 16, 2017 @06:28PM (#14784435)
>Also, you can just define as many new operators as you like.

this is exactly the problem

Re:A deep dive into Multicore OCaml garbage collector by mercurial on Sunday July 16, 2017 @10:14AM (#14782022)
Haskell for hobby programming coupled with professional Perl experience gave me enough idea of what creative programmers could come up with in terms of ASCII art.
Re:A deep dive into Multicore OCaml garbage collector by tome on Tuesday July 18, 2017 @06:30AM (#14795508)
Haskell doesn't have overloading at all, either of operators nor of non-operator identifiers, so I guess you mean something else.

Do you mean user-defined operators, or do you mean operators whose type has a typeclass context?

Re:A deep dive into Multicore OCaml garbage collector by tome on Tuesday July 18, 2017 @06:32AM (#14795519)
If find these kind of comments really interesting, because for me Haskell's witespace-sensitivity immediately makes it a much better language! (I feel the same about Python).

It's interesting because (presumably) reasonable people really disagree on these issues.

Re:A deep dive into Multicore OCaml garbage collector by LukaD on Sunday July 16, 2017 @09:28AM (#14781894)
How does the whitespace sensitivity make it immediately worse?
Re:A deep dive into Multicore OCaml garbage collector by mookid11 on Sunday July 16, 2017 @12:27PM (#14782690)
Unless experienced, you have no clue how a piece of code will be parsed. With ocaml, where is very little ambiguity; and indentation tools can take care of proper formatting, you only need to break lines.

And it can be pretty bad with haskell, which has complex semantics compared to, say, python.

With whitespace sensitive syntax, I feel like in the dark age of manual indentation.

Re:A deep dive into Multicore OCaml garbage collector by tome on Tuesday July 18, 2017 @06:28AM (#14795493)
By no means. Haskell's semantics are extremely simple. Python's are complicated.
Re:A deep dive into Multicore OCaml garbage collector by beeforpork on Sunday July 16, 2017 @05:32AM (#14781269)
Youmeanwhitespaceisbad?C64basicrules!