<story><title>Elixir web development 101: collaborative todolist with realtime updates</title><url>https://blog.openbloc.fr/elixir-phoenix-web-development-101-todo-app/</url></story><parent_chain></parent_chain><comment><author>whalesalad</author><text>I&amp;#x27;m so excited about Elixir these days. I would love to see more cookbook examples of using Elixir but NOT as a Ruby&amp;#x2F;Rails replacement.&lt;p&gt;While the concept is not new to me, I have recently become totally infatuated with the concept of green threads, actor models, etc... for dealing with concurrent processing. This is literally what Erlang was designed to do, and Elixir makes it user friendly.&lt;p&gt;The real beauty of Elixir&amp;#x2F;Erlang is being able to run hundreds of thousands of concurrent &amp;quot;threads&amp;quot; (co-operative in userspace, not OS-level).&lt;p&gt;Anyway I do not mean to detract from the post here -- just feel like a todo list is not a shining-star example of Elixir and would love to see some more hackers post their concurrency work here.</text></comment>
<story><title>Elixir web development 101: collaborative todolist with realtime updates</title><url>https://blog.openbloc.fr/elixir-phoenix-web-development-101-todo-app/</url></story><parent_chain></parent_chain><comment><author>bsaul</author><text>Non-representative anecdote : i&amp;#x27;ve recently heard of two teams that started using elixir, they both came from a ruby background, and in both case they weren&amp;#x27;t using OTP.&lt;p&gt;They both justified using elixir because it was &amp;quot;closer to ruby&amp;quot; (???), and they both seemed to live a pretty difficult time with that language. Which makes me wonder : why would you ever want to use such a special language (purely functional isn&amp;#x27;t for everyone) if you don&amp;#x27;t have any scalability issue, and don&amp;#x27;t even use OTP ?</text></comment>