1. Clear and readable code. Emphasis on pure data being passed around.
2. More minimalist. JavaScript stacks like T3 app (Next.js, TypeScript, tRPC, Prisma) feel like they're solving endless problems caused by other "solutions" in the stack. With Phoenix, you mostly write Elixir, some Ecto macros, sometimes JavaScript for edge cases.
3. Phoenix LiveView is amazingly intuitive
4. Way faster to prototype in, more time in "flow"
Cons:
1. Fewer UI components to pull from if you want to do something complex with the frontend
2. Not a big fan of Ecto macros
3. Have to figure things out yourself (usually read from docs or source code). Difficult for newcomers because of the lack of guides, but good for experienced devs
> 3. Have to figure things out yourself (usually read from docs or source code)
If you're all alone, there are still tons of guides, books, blog posts, et al. Documentation is a first class citizen in Elixir, and theresIf you're on a good team, they'll get you resources. If you're on a bad team? {shrug}
> JavaScript stacks like T3 app (Next.js, TypeScript, tRPC, Prisma) feel like they're solving endless problems caused by other "solutions" in the stack.
I don't agree at all... tRPC/Prisma have been a joy to work with. We still use a traditional SPA app.
1. Clear and readable code. Emphasis on pure data being passed around.
2. More minimalist. JavaScript stacks like T3 app (Next.js, TypeScript, tRPC, Prisma) feel like they're solving endless problems caused by other "solutions" in the stack. With Phoenix, you mostly write Elixir, some Ecto macros, sometimes JavaScript for edge cases.
3. Phoenix LiveView is amazingly intuitive
4. Way faster to prototype in, more time in "flow"
Cons:
1. Fewer UI components to pull from if you want to do something complex with the frontend
2. Not a big fan of Ecto macros
3. Have to figure things out yourself (usually read from docs or source code). Difficult for newcomers because of the lack of guides, but good for experienced devs