Building Cortex on Jido: a signal‑driven coding agent workstation on Elixir/Phoenix. Architecture first—CloudEvents‑style signal bus, minimal tool core, self‑evolving
skills. Inspired by Pi Mono https://t.co/nPMudx4stc #elixir#jido#openclaw
I believe in the EEF! @TheErlef
I'm on the board so I get to see first-hand the amount of work and toil that goes into making the #ElixirLang, #Erlang & greater #BEAM ecosystem better.
What I also get to see, though, is how much we need your help. Relative to the revenue generated by companies that use Elixir, the EEF has a pittance.
Most of us know what's happening the OSS world and security right now. What you probably don't see is the massive amount of coordination and scrambling going on at every level to secure the open source ecosystem. While this may have been operating at a sustainable pace before, the advent of AI has fundamentally changed the game.
The EEF maintains a CNA, and actively coordinates and advises across the board on security issues. They are helping to make our languages more secure, and even https://t.co/VVBtFqrccb!
But the bad news here is that this is no longer sustainable. We need people who are generating revenue on the BEAM ecosystem to pitch in. We need a bigger team of people solving these problems because what we have is barely enough as is.
The real problem, however is that this is progressively getting worse by multiple orders of magnitude. CVEs coming in left front and center.
This is a tragedy of the commons. People are not helping foot the bill for our open source ecosystem. Before that used to mean "inconvenience", as you had to fork packages or version mismatches. But now? Now it means getting pwned.
Join me in becoming a member of the EEF, and please, if you run a company built on a BEAM language: DONATE.