The problem is feedback being a bottleneck when code and prototyping became cheaper.
The solution Mostra suggests is that you add our OSS overlay script to your site, generate a link that embeds mostra project in query param, and share it with people whose feedback you care about.
These folks join the link and just talk while reviewing your feature or the whole site. Once they're done - their feedback is converted to comments that are pinned to the element they were talking about.
After the feedback is submitted, you can point your agent via MCP to fetch and act on it.
Please let me know what you think! I'd appreciate any feedback!
I've been building with Elixir for the last 5 years, and comparing to Python or NodeJS - it's a breath of fresh air. Such decent developer experience, so easy to understand how your system works because of actors and well-defined primitives. If you haven't - you definitely should give it a try!
In an AI era I feel like the tiny amount of Elixir code in comparison with other languages, but all that code having higher signal to noise ration vastly contributed to how good LLM-written Elixir code is. Especially in a well-maintainted codebase that relies on a decent db schema and Oban.
It judging by many microbenchmarks and my prior experience with RabbitMQ and a few Erlang systems, performance has often been a bottleneck. I’m happy that it’s got some typing. I’ll take it to ChatGPT about that. But I’m wondering about real world experience. Could you share more? I don’t have any meaningful experience with Erlang hands on and have never used Elixir. But I’d be fancy to try.
In real world, we currently serve 20M+ visitors and 500M+ requests with Elixir. Previously the client was on PHP, let's just say they have the lowest cost compared to any of the competitors in the region just by switching to Elixir.
All that gloating aside, a lot of it depends on the architecture itself, which Elixir allows you to do eloquently. Just the fact that there are no object oriented concepts alone should be reason enough to use Elixir.
Appreciate that. What’s the infrastructure that it runs on? Is it about delegating the workloads to BEAM as opposed to something like Node.js scaled on AWS Lambdas or a single large JDK container or VM instance for a Spring project where the JVM would serve the requests?
The problem is feedback being a bottleneck when code and prototyping became cheaper.
The solution Mostra suggests is that you add our OSS overlay script to your site, generate a link that embeds mostra project in query param, and share it with people whose feedback you care about.
These folks join the link and just talk while reviewing your feature or the whole site. Once they're done - their feedback is converted to comments that are pinned to the element they were talking about.
After the feedback is submitted, you can point your agent via MCP to fetch and act on it.
Please let me know what you think! I'd appreciate any feedback!
reply