I have just stared learning Erlang after more or less leaving Java, and the heavy weight world of J2EE. I was surprised how easy I have found learning Erlang maybe it just seemed to make sense, or it feels like the right way of doing things. I would be really interested in the book.
Tell HN: I'm writing an Erlang recipes book, are you interested?
11–20 of 42 posts
Re: Tell HN: I'm writing an Erlang recipes book, are you interested?
#12Hey, I see you're gaging potential reader interest by asking what they might pay. You might consider using StoryFunded (http://www.storyfunded.com) for this.
Our site lets authors raise funds for promising book projects. Like Kickstarter it's all-or-nothing where contributors only pay once the goal is met. If the goal is met authors receive the raised funds, minus 5% and processing fees. We've just went live, and our biggest challenge now is finding book projects people would be interested in funding. This may be such a project :)
(sorry! :) )
Re: Tell HN: I'm writing an Erlang recipes book, are you interested?
#13Yes please!
Re: Tell HN: I'm writing an Erlang recipes book, are you interested?
#14[deleted]
Re: Tell HN: I'm writing an Erlang recipes book, are you interested?
#15Yes! Especially if you can cover mutual supervision - that sort of arrangement seems to get glossed over in the "tree of supervisors" world.
Re: Tell HN: I'm writing an Erlang recipes book, are you interested?
#16Very needed book. In particular I am interested in limiting message queues in Erlang. I still don't get it - How one should deal with situations where messages are produced constantly in higher rate than consumed.. There is no protection in Erlang for this common scenario (I think)
Re: Tell HN: I'm writing an Erlang recipes book, are you interested?
#17Nope, never used Erlang and probably will never do so. Good luck though.
Re: Tell HN: I'm writing an Erlang recipes book, are you interested?
#18excuse me for not answering your question, but I have a different suggestion (goes in a similar direction though):
"Erlang in the Real World"
From the top of my head:
- portraits of companies and products who are using erlang
- what does erlang do for them, that is not available in mainstream stacks
- discussing their infrastructure and design desiscions as detailed as possible
- what did they learn
- how are they involved in opensource projects
- numbers and figures of their running systems
This could be a win-win situation. Companies can show their cool stuff. We can learn in what cases Erlang is a good solution.
Anyway - Good luck with your book.
Re: Tell HN: I'm writing an Erlang recipes book, are you interested?
#19excuse me for not answering your question, but I have a different suggestion (goes in a similar direction though): "Erlang in the Real World" From the top of my head: - portraits of companies and products who are using erlang - what does erlang do for them, that is not available in mainstream stacks - discussing their infrastructure and design desiscions as detailed as possible - what did they learn - how are they in…
I think this kind of things is well covered in presentations given at any Erlang Factory. Slides and videos are available at erlang-factory.com
I know for a fact there were some really good talks on development & deployment experiences.
Hope this helps.
Re: Tell HN: I'm writing an Erlang recipes book, are you interested?
#20Erlang recipes, not that much. Make that Erlang/OTP recipes with a strong emphasis on the OTP side of it, and a million times yes !
Or to say it slightly differently : I'm not that much interested in recipes about the Erlang language itself, but I'm very very interested in recipes/examples of architectures of actual Erlang/OTP softwares.
I'm doing mostly Python these days, but I worked on a couple of side projects in Erlang in the past (a large one ~3 years ago, and a small one ~6 months ago). And for me the hardest was (and still is) to figure out how to use the OTP behaviors in an optimal way. How to make a nice, working supervision tree.
I managed to pull working stuff out of the ground, but somehow it never fell OTPish. I couldn't tell if I did it right or wrong.