jam
This was an interesting post by Jose. Curious to hear what others think. Evolving programming languages in the AI era - Dashbit Blog
Generally I think what’s good for humans will be good for LLMs. I think it would be unfortunate to optimize for LLMs forsaking human involvement / code readability etc.
I think there are several excellent points particularly the observability one. I’m not sure explicit static types are that beneficial. Mainly seems like more noise for little to no gain.
Program databases over LSPs
Isn’t this Dexter? Anyone tried it out?
Trending in Discussions
Hey there,
It’s been more than a year since we started using LiveView as our main UI library and building a whole library of UI componen...
New
Hey folks,
I wanted to share with you a project I’ve been working on for a while: It’s an Open Source (AGPLv3) newsletter tool. Think Ma...
New
Hi everyone :waving_hand:
I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
In my third year of college, around 2010, I found Erlang. A few years later, I found Elixir. I liked the ideas at once: many small proces...
New
Hi everyone,
I have 8 years of production experience with Erlang/OTP and I’m just starting to get to know Elixir. What would you learn f...
New
I’ve been tinkering with Lynx (by José) via hold_ledger. I used AI to write the code, a separate specification, the tests, and the Lean p...
New
A remark @Garrison made…
..has already inspired a thread for the technical side of reclaiming our internet, but there is of course anot...
New
Other Trending Topics
Hey there,
I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first.
...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #elixirconf-us
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #security
- #elixirconf-eu
- #api
- #forms
- #performance










Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
josevalim
Most LSPs, including Expert and Dexter, have a database inside but, as far as I know, none of them expose it via a query language.
rhcarvalho
And a challenge with such database is that it is constantly needing to reconcile with the data on disk.
Reminds me how both SQLite3 and DuckDB are able to query over data stored elsewhere.
schwarz
Not necessarily. Sometimes what would be best for both humans and agents is actually too tedious to stick to for humans in practice. See Elm or even DHH’s Rails World 2026 keynote about moving to Rust.
A great of example of targeting LLM capabilities and agents is the MoonBit language. The team is doing a fantastic job building tooling and tweaking the language itself to optimize for agentic outcomes. And we’re seeing more and more of these ideas in the Elixir world already, because it does help.
On the topic of types: As a human I love having types right there in the code, documenting without the risk of being stale.
webofbits
it looks like someone already built something similar months ago: elixir-ontologies/guides/users/getting-started.md at main · pcharbon70/elixir-ontologies · GitHub (query an RDF knowlege graph)
sodapopcan
Oh hey, a José jump scare

EDIT within the timeframe before it even shows I made an edit: Looking at your activity I now realize you’ve been pretty active relative to the recent activity on this forum so, uh, my joke sucks
caleb-bb
The bit on “stronger guarantees” gave me pause.
Stronger guarantees is why I think that Rust is going to be enormously important as we move into agentic coding. You can’t really trust an agent to write memory-safe C++, for example, but in Rust you don’t have that problem because it’s memory safe if it compiles (barring the use of Dark Arts…).
I guess that the capability to develop memory-safe code in older languages might arise with guardrails, but that’s going to require scaffolding and eat up context that could be used for other things. Which leads me to my next point: one big design consideration will be asking ourselves what we can offload to static analysis. Rust, in particular, allows us to offload memory safety almost entirely, so it has a huge advantage.
This is also why my RAG framework focuses so heavily on static analysis, especially the kinds of static analysis that catch agentic errors. For example, property testing, which enforces invariants thus defeating overfitting.
josevalim
If “stronger guarantees” is your main goal, then I don’t think the conclusion necessarily lands on Rust. Any language with a garbage collector provides the same memory-safe guarantees as Rust. BEAM languages provide stronger concurrency mechanisms than Rust. Lean and any other dependently typed language provides stronger typing guarantees than Rust. And so forth. There are multiple venues into stronger guarnatees and I wouldn’t park my horse on memory safety.
Schultzer
I think Elixir has a strong position when it comes to AI native programming languages, and the community is already pushing a lot of projects that I think will benefit. AI is good at generating code, but Turing complete languages comes with a cost to AI agents as it introduces combinatorial explosion. But given Elixir is extendable then we can easily constrain them with implementing and writing protocols, which humans have a harder time with as they are strict and you have to remember the spec, thats why we love general programming languages since there is so many ways to derive a program.
caleb-bb
Garbage collected languages also tend to be prohibitively slow for certain kinds of work. Anyone who’s writing in a systems language to begin with probably has speed as a primary consideration so I don’t see why you’d default to garbage collection here. It would be a step backwards.
I know a guy in PL doing his PhD on finding safe ways to convert C++ to Rust. There’s a reason he’s not converting C++ to Java!
Schultzer
This is absolutely wrong, you can write code in any language that is slow. Just because its native doesn’t mean you get a free lunch you still need to respect the laws of nature.