Live data from Hacker News

Phoenix.new – Remote AI Runtime for Phoenix

fly.io

171–180 of 283 posts

Re: Phoenix.new – Remote AI Runtime for Phoenix

#172
post #68
post #56

Phoenix.new looks powerful, and I'll definitely play with it. I've been daydreaming of an agentic framework that maximally exploits BEAM. This isn't that, but maybe jido[0] is what I'm looking for. 0. https://github.com/agentjido/jido

TIL; That is a very interesting library

This thread on Elixir Forum is a good read if you are considering building agents with Elixir. Jido's author weighs in also.

https://elixirforum.com/t/is-anyone-working-on-ai-agents-in-...

Re: Phoenix.new – Remote AI Runtime for Phoenix

#174
it's wild to me all this progress with AI, but at the same time, on my brand new mac, going through the readme to try out phoenix, it can't even get past the first step without an error (says it can't find postgres), yet the docs say I don't need postgres and it will default to sqllite if postgres and mysql can't be found.

hard to put confidence in AI vibe hacks when the basic stuff just doesn't work.

* (Mix) The database for Myapp.Repo couldn't be created: killed

Re: Phoenix.new – Remote AI Runtime for Phoenix

#175

Earlier quoted context omitted.

Amazing work. Just a clarifying question since I'm confused by the branding use of "Phoenix.new" (since I associate "Phoenix" as a web framework for Elixir apps but this seems to be a lot more than that). - Is "Phoenix.new" an IDE? - Is "Phoenix.new" ... AI to help you create an app using the Phoenix web framework for Elixir? - Does "Phoenix.new" require the app to be hosted/deployed on Fly.io? If that's the case, ma…

Yes all 3. It has been weird trying to position/brand this as we started out just going for full-stack Elixir/Phoenix and it became very clear this is already much bigger than a single stack. That said, we wanted to nail a single stack super well to start and the agent is tailored for vibe'd apps atm. I want to introduce a pair mode next for more leveled assistance without having to nag it. You could absolutely treat…

> For me, something like this is the future of programming. Agents fiddling away and we pop in to see what's going on or work on things they aren't well suited for.

Honestly, this is depressing. Pop in from what? Our factory jobs?

Re: Phoenix.new – Remote AI Runtime for Phoenix

#176
post #82

Why wouldn't LLMs work as well with Elixir as python or JS? LLMs don't parse an AST.

Because of the amount of Python and JS in the wild is much more than the amount of Elixir code, so the LLMs have much more data to base their answers on.

Thanks

Re: Phoenix.new – Remote AI Runtime for Phoenix

#178

Earlier quoted context omitted.

Yes all 3. It has been weird trying to position/brand this as we started out just going for full-stack Elixir/Phoenix and it became very clear this is already much bigger than a single stack. That said, we wanted to nail a single stack super well to start and the agent is tailored for vibe'd apps atm. I want to introduce a pair mode next for more leveled assistance without having to nag it. You could absolutely treat…

> For me, something like this is the future of programming. Agents fiddling away and we pop in to see what's going on or work on things they aren't well suited for. Honestly, this is depressing. Pop in from what? Our factory jobs?

Hopefully, from sitting by the pool drinking margaritas ... but I doubt we will get to keep our new found freedom.

Re: Phoenix.new – Remote AI Runtime for Phoenix

#179

Earlier quoted context omitted.

You can push and pull code to and from local desktop already: hamburger menu => copy git clone/copy git push. You could also have it use GitHub and do PRs for a codex/devin style workflows. Running phoenix.new itself locally isn't something we're planning, but opening the runtime for SSH access is high on our list. Then you could do remote ssh access with local vscode or whatever.

> Running phoenix.new itself locally isn't something we're planning So no plans to open the source code?

Everyone has to eat.

Re: Phoenix.new – Remote AI Runtime for Phoenix

#180

Earlier quoted context omitted.

Yes all 3. It has been weird trying to position/brand this as we started out just going for full-stack Elixir/Phoenix and it became very clear this is already much bigger than a single stack. That said, we wanted to nail a single stack super well to start and the agent is tailored for vibe'd apps atm. I want to introduce a pair mode next for more leveled assistance without having to nag it. You could absolutely treat…

> For me, something like this is the future of programming. Agents fiddling away and we pop in to see what's going on or work on things they aren't well suited for. Honestly, this is depressing. Pop in from what? Our factory jobs?

> Pop in from what? Our factory jobs?

Oh, you sweet summer child. ;)

You will pop in from the other 9 projects you are currently popping in on, of course! While running 10 agents at once!

Post reply on HN