Yes, it describes human nature better than psychology. We can’t fight even knowing about it.

How do you ensure security? Does it have a proper container? Otherwise, it's impossible to prevent leaking prod secrets.

By using Signals and Plugins, all data between agents can be encrypted. I've seen a Jido implementation doing this already.

It's use-case specific though - security is a much bigger topic then just "agents in containers"

The point of Jido isn't to solve this directly - it's to give you the tools to solve it for your needs.

It’s crazy how pretty much every tool people post to support AI systems is already in Erlang/OTP or in elixir standard libraries.

Yep, everyone seems to reinventing the actor model from first principles right now.

We're taking a different approach of building the best actor primitive for mainstream languages and letting people build a thin AI layer on top. We did not set out out build for AI when we started it, it was a happy accident.

How do you intend to conquer the preemptive scheduler? System-wide fairness and preventing starvation are essencial steps for this to work well.

Elixir + Postgres is the microservices killer...last time I saw VP try to convince a company with this stack to go microservices he was out in less than 6mo

This is the killer combo. Working on something now that uses pgmq + Elixir for DAG workflows: https://github.com/agoodway/pgflow

I prefer bit more type-safety. JVM/Kotlin/Jdbi + PG for me.

You read my mind sir! Also, great work by OP, I really needed this since a long time!

Beautiful! :clap:

Rectangle+Apptivate made me stop looking for an i3 alternative, after years. The first for moving windows, the second for switching between them with super+number, just like i3.

I fight against this by using it mostly on trivial tasks, which require no comprehension at all, also fixing docs and extending tests. It helps me to focus on what I love, and let the boring stuff automated.

For complex tasks, I use it just to help me plan or build a draft (and hacky) pull request, to explore options. Then I rewrite it myself, again leaving the best part to myself.

LLMs made writing code even more fun than it was before, to me. I guess the outcomes only depends on the user. At this point, it's clear that all my peers that can't have fun with it are using it as they use ChatGPT, just throwing a prompt, hoping for the best, and then getting frustrated.

I do almost the same, with a simple bash script, and no JS junk: https://github.com/alexandremcosta/alexandremcosta.github.io...

If it's not intended to be done, then you are using the wrong name. Don't call it `TODO`.

Sometimes "TODO" means something you would do if you had infinite time, refactor the code completely or something that will likely need to be revisited in the future but currently adds no value to implement.

TODO is a pretty clear name. If it's not to be done, then it should be just a regular comment, no need to tag as TODO.