Please note that it may be hard to make a
print out of a wikibook. You might want to
use Docbook/XML or Latex in a darcs repo-
sitory instead.
On Mon, Dec 11, 2006 at 03:23:13PM -0500, Matt Revelle wrote:
Sorry, wasn't sure I had clearly expressed that it's possible to have
an open book end up
Paul Hudak wrote:
Maybe some of you can do better, but it's really tough to show someone how an
/advanced/ Haskell programmer would solve /advanced /problems that arise in the
real world. As a simple example, I love this recent quote by Garrett Morris:
I'm personally fond of framing most
Paul Hudak wrote:
Hi Sebastian. As a writer of one of those academic Haskell textbooks,
I've been following this thread with some interest.
BTW, I found your textbook very helpful. The first time I tried to
learn Haskell, I got the Bird and Wadler textbook, and got bogged down
about halfway
Hello everyone,
On 12/12/06, Ketil Malde [EMAIL PROTECTED] wrote:
snip
Some things took a bit of effort to wrap my head
around, but it generally wasn't too hard to get to a level where I could
write useful programs.
snip
* I'm already productive with what I know, so I don't have the direct
On 12/11/06, Andrew Wagner [EMAIL PROTECTED] wrote:
I think there are some great ideas here, and it would be a fantastic
project to do as a community, via a wikibook.
..
On 12/11/06, Kirsten Chevalier [EMAIL PROTECTED] wrote:
there's not really a way to get a publisher to
In my opinion it would be important to increase the
understanding about semantics and processes. And
it would be good to introduce the concepts in a
similar way as Profokiev introduces the sound of
classical music in Peter and the Wolf. If my
suspicion is correct, functional programming would be
On 12/11/06, Patrick Mulder [EMAIL PROTECTED] wrote:
In my opinion it would be important to increase the
understanding about semantics and processes. And
it would be good to introduce the concepts in a
similar way as Profokiev introduces the sound of
classical music in Peter and the Wolf. If my
The way to write the book, I think, would be to take something
referred to as real world problems - problems a large proportion of
programmers deals with and gets paid for, and then show how to solve
these problems in Haskell (preferrably quicker and easier than with
conventional solutions).
I
(to Kirsten, Akhmechet, cc: Haskell-Cafe)
I would divide the book into two parts. The first
part would introduce
Haskell via traditional small examples. Quick sort,
towers of Hanoi,
etc. The second part would have two or three large
examples -
something that people would relate to. I'd take
Kirsten Chevalier wrote:
There's also excellent Haskell documentation available on the web
already, but people like to buy books and they like to have an
artifact that they can hold in their hands without getting laser
printer toner all over themselves.
It also helps to collect and edit.
[...] I think the concept of computer is better to
see as sort of telescope or translator. Computers
allow to look at processes (and complexity) which
would otherwise not conceivable to our limited minds.
The idea of computers as telescopes is from Daniel
Dennett though.
Computer Science is
I think there are some great ideas here, and it would be a fantastic
project to do as a community, via a wikibook. I, for one, have been
studying haskell for several months, and am just starting to see a
little bit of light when it comes to monads. I think it would be
beneficial to work through a
On Mon, 11 Dec 2006, Andrew Wagner wrote:
I think there are some great ideas here, and it would be a fantastic
project to do as a community, via a wikibook. I, for one, have been
studying haskell for several months, and am just starting to see a
little bit of light when it comes to monads. I
On 12/11/06, Andrew Wagner [EMAIL PROTECTED] wrote:
I think there are some great ideas here, and it would be a fantastic
project to do as a community, via a wikibook. I, for one, have been
studying haskell for several months, and am just starting to see a
little bit of light when it comes to
A quick search turned up Lulu (http://www.lulu.com/).
From the Lulu site:
Publish and sell easily within minutes.
No set-up fees. No minimum order.
Keep control of the rights.
Set your own price.
Each product is printed as it is ordered.
No excess inventory.
Looks like they offer hardcover
On 12/11/06, Matt Revelle [EMAIL PROTECTED] wrote:
A quick search turned up Lulu (http://www.lulu.com/).
From the Lulu site:
Publish and sell easily within minutes.
No set-up fees. No minimum order.
Keep control of the rights.
Set your own price.
Each product is printed as it is ordered.
No
Well, perhaps if nothing else, we could use a wikibook to
collaboratively work on the structure of such a book, and then from
that you could publish a real book. I don't really know the legal
issues, though. I am thinking of several books though which have been
written and released both as full
On 12/11/06, Andrew Wagner [EMAIL PROTECTED] wrote:
Well, perhaps if nothing else, we could use a wikibook to
collaboratively work on the structure of such a book, and then from
that you could publish a real book. I don't really know the legal
issues, though. I am thinking of several books
What do you mean by real publisher? As long as the quality of the
final product is good, does it really matter what publishing company
has their name stamped on it?
I'm not sure about Lulu and distribution, but there's also BookSurge
(http://www.booksurge.com) which is owned by Amazon. From
On 12/11/06, Matt Revelle [EMAIL PROTECTED] wrote:
What do you mean by real publisher? As long as the quality of the
final product is good, does it really matter what publishing company
has their name stamped on it?
It matters to me; if I'm going to put work into this, then that's what
I
Well, I'm not opposed at all to a written final form. I guess I just
don't see that and using a wikibook to assist in our collaboration as
mutually exclusive. Anyway, I'd love to help in any such project. By
the way, I seem to be messing up the threads. What is considered the
correct way to reply
On 12/11/06, Andrew Wagner [EMAIL PROTECTED] wrote:
Well, I'm not opposed at all to a written final form. I guess I just
don't see that and using a wikibook to assist in our collaboration as
mutually exclusive.
I think the confusion is my fault. I assumed that you (if it was you
who originally
I have taken the liberty to read into the definition of practical
Haskell; if I'm off target let me know so I can tweak my claims to
fit whatever it is I thought I was discussing ;).
Two cents:
1) This wouldn't be the first book introducing functional programming
to imperative programmers. It
On 11 Dec 2006, at 19:35, Kirsten Chevalier wrote:
On 12/11/06, Andrew Wagner [EMAIL PROTECTED] wrote:
Well, perhaps if nothing else, we could use a wikibook to
collaboratively work on the structure of such a book, and then from
that you could publish a real book. I don't really know the
Since people keep saying the word wikibook, I will make the obligatory
mention of http://en.wikibooks.org/wiki/Haskell
It might not yet have the style/voice/sense of direction that we're
discussing here, but maybe people might be interested in shaping that
book into something really interesting?
Sorry, wasn't sure I had clearly expressed that it's possible to have
an open book end up as a dead-tree book.
Either way, I'm interested in helping.
On 12/11/06, Kirsten Chevalier [EMAIL PROTECTED] wrote:
It matters to me; if I'm going to put work into this, then that's what
I want the
Ok, well I think we can all agree that such a book is a good idea. I
suggest we take the discussion to some kind of collaboration tool.
It's pretty hard to do just on this mailing list. There are a lot of
options, such as finding a forum somewhere, creating a wiki book
somewhere and having a
On Mon, 2006-12-11 at 13:42 -0600, Nicolas Frisby wrote:
Two cents:
Two (Croatian) lipas, much less than two cents :-(
3) This would be the first book introducing the nuances of large
systems development in Haskell to Haskell programmers. Explaining well
various monads (e.g. how to use
On 12/11/06, Kirsten Chevalier [EMAIL PROTECTED] wrote:
It's not as if this is the first time that this has been suggested,
but some people have suggested that a practical book about Haskell
would be a good idea. I agree. Some people have also suggested that
the right moment for this hasn't
On 12/11/06, Andrew Wagner [EMAIL PROTECTED] wrote:
Ok, well I think we can all agree that such a book is a good idea. I
suggest we take the discussion to some kind of collaboration tool.
It's pretty hard to do just on this mailing list. There are a lot of
options, such as finding a forum
Hi Sebastian. As a writer of one of those "academic" Haskell
textbooks, I've been following this thread with some interest. In
fact, I agree with pretty much everything that's been said. But I must
point out that, even though Chapter 18 in SOE is titled "Higher Order
Types", and that's where I
I think this might be a good time to step back and make some general
comments of my own.
I learned Haskell in the summer of 2000. I see that that's exactly
when SOE was published. I didn't have a copy. (I did acquire a copy of
SOE about two years later, when I didn't need it anymore :-) I did
On 12/11/06, Paul Hudak [EMAIL PROTECTED] wrote:
Hi Sebastian. As a writer of one of those academic Haskell textbooks,
I've been following this thread with some interest. In fact, I agree with
pretty much everything that's been said. But I must point out that, even
though Chapter 18 in SOE
G'day all.
Quoting Kirsten Chevalier [EMAIL PROTECTED]:
I suppose I should have clarified that I meant a dead-trees book with
a real publisher, [...]
Something more like this, then:
http://phptr.com/perens
Maybe we should come up with an outline and a sample chapter or two, then
talk to
On 12/11/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
G'day all.
Quoting Kirsten Chevalier [EMAIL PROTECTED]:
I suppose I should have clarified that I meant a dead-trees book with
a real publisher, [...]
Something more like this, then:
http://phptr.com/perens
Maybe we should come up
Hi,
I wonder if a similar theme is apropriate for proposed book.
Graphics and sounds give a very direct feedback to the programmer, and
I expect that helps with the motivation.
Perhaps a single largish application could be the end product of the
book. Like a game or something. You'd start off
36 matches
Mail list logo
