Your ideas for Elixir book authors and content creators

elixir & elm, something like in programming phoenix book. I don’t think it needs to be book per se, what’s wrong with online course on udemy or lynda?

I would like to see one project from start to finish that handles bunch of requests (and can monitor whenever he wants, get notifications for certain conditions). Maybe gaming server. Players connect to server to look for available players, chat with them, create games and play with other players. This is one example where this technology would do much good. https://www.faforever.com/
my 2 cents

I think there’s more than enough material for beginners. I’d like to see a distributed systems book that uses Elixir as its language. It’d have implementations of algorithms like Raft or solutions to say, Byzantine Generals.

In general, material that goes beyond making web apps would be nice.

Not again a chat application.

“This could cause a prejudice I have seen: that elixir/phoenix is good for making (for them) trivial chat-applications and not much more. While the easy to add real-time possibilities can be a big plus for administrative applications. Showing this plus would be good for marketing.”

https://forum.elixirforum.com/t/what-can-we-do-to-accelerate-the-adoption-of-elixir/2398/47

Personally I’m not interested in gaming either. An administrative one showing everything that makes elixir/phoenix special please.

I think a book about how to use Elixir in embedded contexts (such as a book about Nerves) would be a very good idea.

Here’s an Elixir and Elm sample game, in case it helps:

It’s explained in this talk.

100% this. The low hanging fruit has been thoroughly picked by now and while I think a very decent way of learning is to make a tutorial on something, a lot of the time the videos/posts are actually full of guesswork that ends up being wrong, or they do a lot of handwaving about stuff that ends up being either misinformation or very unhelpful for the people who need the content.

Right on.

What we need are more real world books. Don’t get me wrong. I love the inspirational “Elixir is great…Elixir rocks…Elixir does x easier” books and articles, but what really really matters is how do we do REAL WORLD things in Elixir.

We need a book that talks about the hard stuff: Deployments, networks, distribution, scaling, testing, logging, metrics, and real failure. It’s nice that all the books we have tell us that we CAN do all those things, but how are companies like Bleacher Report handling these topics.

I’ve talked to Steven Proctor in the past about him and I setting up a conference here in Dallas, TX to interview real Erlang/Elixir developers that have successfully dealt with these real world issues. It would be awesome to see a book that really dove into those subjects.

Now, that being said, I’m only halfway finished with Designing for Scalability with Erlang/OTP. That book may have everything I said above, but I’ve got a feeling it still isn’t in depth as we SHOULD get.

It’s one thing to read some examples, and it’s another thing having someone experienced tell you, “It’s not all Rainbows and Sunshine, but don’t worry because I’m going to show you the hard things you’re going to run into and how to overcome them”.

I would really like an introductory book to Ecto. The guides are fine but a book is more structured and can walk you step by step through the features.

Also books that cover real life projects would be great.

Maybe this is what you want: http://pages.plataformatec.com.br/ebook-whats-new-in-ecto-2-0

PS: I am the author.

I have read that book. And I plan to re-read it again this weekend. To be honest I don’t remember much of it’s content because when I read it the first time it was all new to me. I do remember though that the book states that it is not an introductory book and one should refer to documentation.

Right now I am reading again programming phoenix and I saw “custom types”. This got me thinking how many features like this does Ecto have and I am not aware of them. I know I will discover them as needed but it would be nice to have them somewhere concentrated for reference. You don’t know what you don’t know.