[sergiotapia]

I recently tried Nextjs and Remix to explore other stacks since I've been using Elixir and Phoenix since 2016.

You won't find the dev UX you take for granted in Elixir and Phoenix.

Endless routing options, background jobs? Just install Squirrel and yadabadabadoo or just use AWS SQS(https://old.reddit.com/r/nextjs/comments/qspw4v/how_to_do_ba...). What about solid backend processes? Can I call those in some kind of repl? In Elixir I can just go `iex -S mix phx.server` and `MyModule.foobar("test")` and bada bing I'm all set. What about logging? Wait I need to decide and configure a logger? I also need to decide and configure what to output to? What about a nice ORM? Prisma looks good, set that whole thing up from scratch, I need to await, but special considerations need to be thought of when iterating through a collection? Promise.all vs for..of? I iterated an array and want to save it to the DB but it's running out of connections (https://github.com/prisma/prisma/discussions/16884)? Why do I even need to think about this?

Really curious to hear your counterpoints to this because granted I am quite new to backend typescript.

[melony]

The counter argument is that you don't have to babysit any of those services. AWS/some other PaaS will handle everything for pennies. Unless you are working in a low cost of labor country, developer time is going to be more expensive than anything else. It will take very large scale/growth for infrastructure fees to exceed the total compensation of a decent US staff engineer or a site reliability engineering team.

[fomine3]

A problem is that "penny" isn't actually penny for hobby or very small internal in-corp project.