Go learn functional programming if you haven't, it will force you to look at problem with a new set of eyes!
The Future of Standard ML (2013) [pdf]
21–30 of 82 posts
Re: The Future of Standard ML (2013) [pdf]
#22Earlier quoted context omitted.
No. I mean, I know Tiobe isn't great, but the only ML-derivative I see on the top 50 is F#. ML and OCaml crack the top 100.
F# is an OCaml derivative. I'd reckon that OP's feelings about F# would be rather similar to their feelings about OCaml.
Re: The Future of Standard ML (2013) [pdf]
#23Earlier quoted context omitted.
F# is an OCaml derivative. I'd reckon that OP's feelings about F# would be rather similar to their feelings about OCaml.
The only objection to OCaml is "the crufty syntax," which I think F# has taken steps to improve upon.
Re: The Future of Standard ML (2013) [pdf]
#24Cutting to the chase: use Haskell or Scala or F# if you need to do some scripting or build a web application that requires lots of different tasks (being a web server, rendering templates, connecting to a database, etc.). Haskell and Scala have great libraries and polymorphism that allows you to express things succinctly. Dunno much about F# except .NET. Use OCaml if you want easily native binaries, predictable perfo…
Re: The Future of Standard ML (2013) [pdf]
#25Re: The Future of Standard ML (2013) [pdf]
#26Earlier quoted context omitted.
F# is an OCaml derivative. I'd reckon that OP's feelings about F# would be rather similar to their feelings about OCaml.
The only objection to OCaml is "the crufty syntax," which I think F# has taken steps to improve upon.
Re: The Future of Standard ML (2013) [pdf]
#27I was taught functional programming through SML in university two years ago. I have never had my brain twisted with so many interesting and clever concepts - it was one of the most valuable semesters I had, and my favourite class. Go learn functional programming if you haven't, it will force you to look at problem with a new set of eyes!
Re: The Future of Standard ML (2013) [pdf]
#28Earlier quoted context omitted.
> operators (not named functions) are to programming > languages as icon-only buttons are to web pages; > they are completely unusable. I see ( ) ; . you are using already. Latin letters are gibberish to people who don't use it.
I wrote some Scala just today: val list = a +: l :+ b And I knew I had to put in a comment because that stuff always makes my eyes cross over when I come back to it.
a ? b : c
construct which maybe was equally puzzling when it was introduced by CPL in 1963.Re: The Future of Standard ML (2013) [pdf]
#29Re: The Future of Standard ML (2013) [pdf]
#30Cutting to the chase: use Haskell or Scala or F# if you need to do some scripting or build a web application that requires lots of different tasks (being a web server, rendering templates, connecting to a database, etc.). Haskell and Scala have great libraries and polymorphism that allows you to express things succinctly. Dunno much about F# except .NET. Use OCaml if you want easily native binaries, predictable perfo…
Learning SML isn't going to help as much with Haskell as you might think. The others, yes.
[0] http://www.cse.unsw.edu.au/~chak/papers/modules-classes.pdf