The latest episode of the Pingback Podcast with @joelga is out!
We had a special guest this week! @samruby has more years of programming under his belt than I have lived!
His recent project Roundhouse is having a good momentum. Go and give a listen!
https://t.co/NdRXmkA9SS
Did not expect a question that starts out 'Do you think before you speak?' to go so well. A+ question from Charlotte Harpur A++ response from Eileen Gu.
@hopsoft Spinel + Roundhouse is incredibly exciting. It's absurdly ambitious in just the right way and very open to open source contribution. Join the party. I'm committed to getting BitterClip to compile, which 3 million lines Rails!
@mikehostetler@thorstenball https://t.co/TTSGuBJpjO any feedback on this, I’m trying to basically have one prompt per language+framework that represents how an expert in the framework would guide the agent to build conduit ( the spec app being compared )
I am publishing archives of agents one shotting a spec app at https://t.co/8zblh6el25 and I would be super honored if you could make a PR for the elixir prompt. Basically I’m just trying to have an even playing field where there’s a expert level prompt for each language to make it as terse and idiomatic as possible, and a shared spec they need to hit.
Do you have the prompts or threads publicly available?
The agent clearly chose to follow Rails compatibilty more closely in the Elixir version. So a few of Rails limitations got ported to the Elixir one. Here is an example from the README itself:
> Elixir retains Redis and Resque-compatible jobs, while Rust uses integrated queues and a different frontend/server implementation.
The agent knows, it just chose to prioritize something else, which will always happen if you are not steering.
I am certain coding agents can spot those issues and bring the numbers up for both Elixir and Go with no troubles whatsoever (although I don't expect them to beat Rust).
I’ve got a project that’s similar but attempts to be more rigorous by defining a spec. They must all share so the app has the same requirements across the different languages https://t.co/8zblh6el25 I’m seeing similar performance on the compiled with Spinel Ruby as the Rust version
Initial explorations with Spinel are very promising! Seeing around 6x+ perf And request throughput on the canonical https://t.co/e7GRzL0xO1 app! It wasn't easy, but it works! 2 PR's landed upstream, lots more incoming.