Here is where you can find an up to date version of the book: The Little Ecto Cookbook - Dashbit ebooks The one you linked is at least 3 years outdated (also please don’t link to the book directly).
Yes!! I remember there was some other thread where people were complaining that it’s difficult to get started with LV unless you started with it long ago and kept up to date with its development. But that video looks totally up to date with Phoenix 1.7…
Would be cool to see a similar video, but for basic CRUD type stuff, kind of highlighting how much easier it is to do “restful resources” in LV as opposed to normal controller/actions.
With the ecosystem growing as much as it has these past few years I think it could be really nice to now have a book that is a “A whirlwind tour around Elixir and the ecosystem” or “A beginners guide to Elixir and the ecosystem” which introduces readers to various areas of the Elixir world, such as Elixir itself, Erlang, Phoenix, LiveBook, Nx, Ash, Elixir Desktop and even newer things like Hologram etc. So by the end of the book you’ll have had a decent introduction to each topic and should be able to create a basic project with them.
Could be something like @redrapids’s “Seven … in Seven Weeks” series of books - wouldn’t surprise me if Bruce has already been thinking about doing something like it! If Bruce is not interested, it could be a nice book with multiple authors, those specialising or with knowledge of each topic… which they could then perhaps turn into a dedicated book for each topic if their chapters take off
How about something like The Rails Way - https://leanpub.com/therails7way reference book? I think in depth of Phoenix and its internals can be a good one - The Elixir/Phoenix Way
Good idea. As someone new to Elixir, I feel overwhelmed by the many tools available even for a simple website. Each of these tools requires some knowledge, so learning them sequentially can take a significant amount of time. Maybe that’s why I preferred using Gleam last time for a pet project, because there are fewer libraries for each problem with limited options