5 ms·
Using Go is a constant temptation and for small APIs it's probably a good choice. Ruby (esp. Rails), for me, is worth the performance trade-off - even though t
by mtkd 13y ago
Using Go is a constant temptation and for small APIs it's probably a good choice.
Ruby (esp. Rails), for me, is worth the performance trade-off - even though that stings me coming from a C/assembler background originally.
With Rails you can build complex/deep APIs with very efficient syntax and clear tests - the conventions enforced mean that everything is in the same place/style no matter who coded it - so the finished app is more maintainable than in any other language/framework I've ever known.
- astrodust 13y agoPlus you can prototype in Ruby and optimize by replacing it with something else and running the same Ruby-based tests against your optimized version.
- IanChiles 13y agoA small note on Go and enforced conventions. Gofmt enforces a standardized syntax for all code - there's no debating or arguing over code style. Now for the rest of it (file structure and the like) Rails blows Go away. If Go had a framework like Rails, but designed to play to Go's strengths, it could decimate Rails in every facet except the amount of existing code written.