[spotman]

If you are relying only on a framework for things like CRSF protection and do not understand how to avoid these pitfalls on a fundamental level then you have bigger problems.

Having said that I think I would choose your solution based on your teams skills. If they are comfortable with golang there is no reason it could not be made to work.

But as long as you understand how the table is set and the trade offs I don't think it matters. Golang is going to have less batteries included but it has other advantages too. If it's worth it is really a question of speed of code execution vs speed of writing code.

[dlist]

Our previous startup was with Rails and we did hit performance bottlenecks, even without Payments being involved. Consumers are very sensitive to speed, so that plays a big role in the decision as well. Team skills are adjustable - the founders are technical and the team is being built up hereafter. The big question is does GoLang still have any inherent issues that may conflict with the expected reliability of a financial company - is the Braintree objection out of date?

[jtmarmon]

you'd have to explain more about what you're doing, but i'm sure go is fine. i'm also sure rails is fine.

i can't speak for the first two points, but those seem simple enough to avoid with tests, really. most issues are.

the third issue is something you have to decide on. i'm sure the tooling around go is much better than it was three years ago, but you're not going to have everything in a pretty package like you do rails.

honestly the choice is probably inconsequential, unless you have some actual reason why the language choice matters for your application (which it almost always doesn't).

also if you're in fintech and doing bitcoin, i've heard the node ecosystem has the most BTC support, so that's a consideration