4 ms·
Wow ... I just saw type-safe macros / quasi-quoting. It seems that Haskell is the language I've been searching for all my life :-) ... unfortunately code writt
by bad_user 16y ago
Wow ... I just saw type-safe macros / quasi-quoting.
It seems that Haskell is the language I've been searching for all my life :-) ... unfortunately code written in it looks really scary.
I mean ... when I look at good Python / Ruby code, I just get what's going on ... that's partly because I know these languages, but on the other hand they encourage programmers to do literary story-telling.
Maybe someday Haskell will get reinvented into some form meant for mere mortals :)
- eru 16y agoI really like the syntax of Haskell. You can get used to it fairly quickly. > [...] but on the other hand they encourage programmers to do literary story-telling. Try literate Haskell. (I say this only partially tongue-in-cheek.) Really, I think that Haskell is very geared towards being read by humans. This is mostly because it's so good at gluing, that you can break your problem apart in smaller pieces in the first place. E.g. let's look at a program that computes sqrt(2). With Haskell you can talk first about how to produce infinite list of ever better approximations: next x = (2 / x + x) / 2 approximations = iterate next 1 and then talk about when to stop and finally give an answer later on. goodEnough x = abs (2-x*x) <= 0.0001 sqrtTwo = find goodEnough approximations In a strict language, you usually intermingle producing new values with watching out for the ending condition: guess = 1 while abs(2 - guess*guess) >= 0.0001: guess = (2/guess + guess) / 2 Python's generators help, but they are more restricted. (Which is intended, Python wants to stay simple.)
- JadeNB 16y agoJust out of curiosity, what's the advantage of `(2/x + x)/2` over `x/2 + 1/x` (which, to me, is more readable)?
- eru 16y agoIt is more readable. But I wanted to stick close to the general formula [1], so that you see what's going on. It would probably have been better to write it as: y = 2 average x1 x2 = (x1 + x2) / 2 next x = average (y/x + x) It's just a co-incidence that I chose y as 2. [1] Heron's Method (http://en.wikipedia.org/wiki/Herons_method#Babylonian_method http://en.wikipedia.org/wiki/Herons_method#Babylonian_method)
- danieldk 16y agoI'd say: just try it. After reading haskell-cafe for a day, I felt utterly incapable of ever learning Haskell. I started picking up the language using Real World Haskell (quite an acceptable book). I can read most programs now and crafted some short programs. I still find predicting memory/time use under a lazy-evaluation regime difficult. But it is certainly a nice experience ;)
- eru 16y agoThe guys on Haskell Cafe delight in complex problems (and solutions). There's a list for beginners, too. You will enjoy the Haskell Cafe later. By the way, one small exercise (from a paper by Chris Okasaki): Write a function with the type Tree a -> Tree Int where data Tree a = Node a (Tree a) (Tree a) | Empty your function should all nodes in a tree with their position in level order traversal (also called breadth first search). E.g. (lot == lever order traversal) lot Empty = Empty lot (Node 'a' (Node 'b' Empty (Node 'c' Empty Empty)) (Node 'd' Empty Empty)) = (Node '0' (Node '1' Empty (Node '3' Empty Empty)) (Node '2' Empty Empty))
- gaius 16y agoThe thing with RWH I found was, chapters 1-4 great, a nice introduction to the language, and I did all the exercises without too much head-scratching. Then chapter 5 is utterly incomprehensible. I didn't get any further. OCaml, that's a nice language, with much better introductary materials.
- gtani 16y agoDont' give up: http://www.amazon.com/Programming-Haskell-Graham-Hutton/dp/0521692695/ http://www.amazon.com/Programming-Haskell-Graham-Hutton/dp/0... http://stackoverflow.com/questions/1012573/how-to-learn-haskell http://stackoverflow.com/questions/1012573/how-to-learn-hask... http://learnyouahaskell.com/ http://learnyouahaskell.com/
- anonymousDan 16y agoWhat did you find so hard about chapter 5 ("Writing a library: working with JSON data")? Doesn't seem too be such a big step up to me in comparison to other chapters in the book?
- loup-vaillant 16y ago> on the other hand they encourage programmers to do literary story-telling. That is the part you must avoid. In Haskell, you don't tell a story. You depict a landscape. (There is a story, in the IO monad, but it is minimized and segregated.)
- stonemetal 16y agoMy background is almost all C, C++, and some python. I have been fooling around with Haskell for a few months now. I can honestly say I haven't used anything on the list beyond the first two. Haskell falls very close to python in readability if you want it to. You can "go deep" and produce stuff that only an experienced, hard core functional programmer can understand as this guy does, but I tend to use it as a statically typed, fast python. Flip through the first few chapters of Real World Haskell online and see that it is fairly readable.