Shawn McCool

Event Sourcery, the video course that I built as an introduction to domain modeling, cqrs, and event sourcing, is now publicly available on YouTube. youtube.com/channel/UCa_BK… I wrote and recorded the series over the course of a year and I hope that people will find it helpful.

@mteinum I appreciated the video =D

@ShawnMcCool Elixir was really nice for implementing a MCP server! github.com/mteinum/tictac…

Especially in an era of agentic coding.. it no longer makes any sense to me to continue using languages like PHP which offer zero novel value. I don't stand to gain anything from saying this, but now is the time to start with Elixir. Have faith and rip off that band-aid.

We just shipped Distributed Python on top of the Erlang distribution, with full Elixir and Livebook integration: dashbit.co/blog/distribut… And much more: intellisense, zero-copy Apache Arrow, and more. Read the article for all the details. A huge thank you to NLnet Foundation for sponsoring our work. They are always looking for new ideas and you have until April 1st to join the next batch: nlnet.nl

Chat-like interfaces replacing traditional UI are gradually exposing that *events* are the fundamental source of truth for state management

More #Elixir for #PHP devs fun! 🍷 — One of my favorite things about Elixir, don't sleep on multi-clause functions 😎 (link in replies) 👇

@unnamed1tw @rr_cook

@rr_cook @ShawnMcCool PHP is for web app, mobile apps, desktop apps, CLI,…

@rr_cook @unnamed1tw Its mid-90's intentions aside, even with modern advancements it handles concurrency poorly; to the point of almost completely ignoring it. It makes concurrency another layer's problem. It performs one action and dies. PHP is particularly poorly suited for server software.

@ShawnMcCool @unnamed1tw I spent 30 minutes reading a PHP book once but I thought it was made to build server software? What are the issues?

@petyastehlik I would make myself available to you during your experimentation. Message me if you like.

@ShawnMcCool Alright, let me try, I'll let you know in a couple of months.

Saying "isolated processes for fault tolerance are not relevant because they were pushed to orchestration layer" is like saying "we don't need threads, because we will just run one pod per core anyway". The difference in reacting and responding to "my connection pool crashed" by restarting the pool locally vs restarting the whole pod is going to be massive, similar to the differences in latency when coordinating across threads vs across pods. Yes, other programming languages have threads, and they raise a signal when they fail, but that's missing the point. What matters it not the signal but the guarantees. If you have global mutable state and a thread crashes, can you guarantee it did not corrupt the global state? If you can't, the safest option is to restart the whole node anyway, because it is best to have a dead node than running a corrupted one. PS: somewhat related 6-years-old post: dashbit.co/blog/kubernete…

@mteinum Let me know if I can help at all. I think you may be pleasantly surprised with the ergonomics of Elixir + Phoenix.

@ShawnMcCool A have done adventofcode some years with both Erlang and elixir. Maybe it’s time to revisit these skills

@real_redp I don't know what you're saying.

@ShawnMcCool in next months misanthropic will learn their models on elixir - what you gonna do?

@amitgupta Ultimately, we can agree to disagree that ecosystem "size" is a relevant metric.

@amitgupta There's significant precedence for high-performance from the BEAM including but not limited to RabbitMQ.

@petyastehlik ...designing software components, systems, and more. I believe that it has a reasonable chance of transforming your views on software and systems design. At the very least, I challenge you to put a couple of months into it and THEN evaluate. I believe you'll be happy you did.

@petyastehlik I would encourage you to change your mental model about the usefulness. I have been experimenting for some time with agents and I think it's going to work out differently than you may expect. Further, I believe that learning Elixir will feed back into how you think about...

@igorhansachat These tools also have weaknesses that are already overcome with the BEAM (the runtime that Elixir uses). It's not about WHAT php can do. Engineers have shown great capability in using inadequate tooling to solve anything. It's about how it could be done better.

@ShawnMcCool do you want to say that you want to use redis because it doesn't stay in memory? It does if you use e.g. FrankenPHP or Roadrunner instead of php-fpm that was previously common. This means you don't need extra layer like redis.

@igorhansachat Here are a few resources that go deeper into this topic, but there's more thaT I can share if you're interested. - youtube.com/watch?v=dKaZ89… - youtube.com/watch?v=_5B_B_… - ash-hq.org

@igorhansachat Further, Elixir supports tooling like Ash Framework that genuinely results in faster dev with a dramatic improvement in abstraction which PHP could not support. The ecosystem is smaller in Elixir, but the avg developer is much more experience and the tooling reflects that.