←back to thread

638 points wut42 | 2 comments | | HN request time: 0.443s | source
Show context
chrismccord ◴[] No.44328933[source]
Phoenix creator here. I'm happy to answer any questions about this! Also worth noting that phoenix.new is a global Elixir cluster that spans the planet. If you sign up in Australia, you get an IDE and agent placed in Sydney.
replies(21): >>44329010 #>>44329145 #>>44329199 #>>44329447 #>>44329669 #>>44329679 #>>44329692 #>>44329699 #>>44329766 #>>44330059 #>>44330099 #>>44330127 #>>44330670 #>>44331525 #>>44331688 #>>44334922 #>>44335271 #>>44336137 #>>44336958 #>>44337485 #>>44344757 #
tiffanyh ◴[] No.44329145[source]
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, maybe a naming like "phoenix.flyio.new" would be better and extensible for any type of service Fly.io helps in deployment - Phoenix/Elixir being one)

- Is it all 3 above?

And how does this compare to Tidewave.ai (created as presumably you know, by Elixir creator)

Apologies if I'm possibility conflating topics here.

replies(1): >>44329739 #
chrismccord ◴[] No.44329739[source]
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 phoenix.new as your full dev IDE environment, but I think about it less an IDE, and more a remote runtime where agents get work done that you pop into as needed. Or another way to think about it, the agent doesn't care or need the vscode IDE or xterm. They are purely conveniences for us meaty humans.

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.

Tidewave is focused on improving your local dev experience while we sit on the infra/remote agent/codex/devin/jules side of the fence. Tidewave also has a MCP server which Phoenix.new could integrate with that runs inside your app itself.

replies(1): >>44333742 #
tills13 ◴[] No.44333742[source]
> 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?

replies(4): >>44333964 #>>44334000 #>>44334128 #>>44334652 #
pmarreck ◴[] No.44334000[source]
> 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!

replies(1): >>44338802 #
1. tills13 ◴[] No.44338802[source]
And from which exactly am I earning an income to feed myself? Who's buying what I'm making? Where are they getting their money?

We're building a serfdom again.

replies(1): >>44343329 #
2. pmarreck ◴[] No.44343329[source]
LOL, what? Take on 10 projects at once, and start making way more money... if you're not an external-locus-of-control moron at least

You've literally been given an excavator when you currently have a shovel, and you're worried that other excavators will dig you out of a job. That is a literal analogy to your POV, here