2 ms·

There is a large base of competent Rails practitioners. It has good documentation. The code base is stable. There are mature libraries. It is practical to l

There is a large base of competent Rails practitioners. It has good documentation. The code base is stable. There are mature libraries. It is practical to learn Rails. Sure there are very good reasons not to choose Rails, but the current year is not one of them. And the work of building any new business...let alone a startup is approximately the same no matter which technologies you choose (modulo your expertise). Time spent researching web frameworks postpones building the potentially money printing mechanism. When your research is done, you still won't have built anything. If you are lucky enough to grow, you will be constantly rebuilding your systems. Unless you are Telegram. They used Erlang. It has the same features as Rails except for a large pool of practitioners. Good luck.

dondraper36 2y ago
I just opened the official starting guide from the official RoR website and am very excited, to be honest. I mean, the Go way of as few dependencies as possible and no opinionated frameworks is cool, but getting so much done for you is such a nice thing when you want to build fast. Also, switching to a purely REST API with just render json: <blah> is unbelievably fast. Writing the same in Go would include a lot of boilerplate. Anyway, thanks for your response. I am really happy for Ruby, RoR, and the community.
- brudgers 2y ago
  Congratulations on starting! the Go way of as few dependencies as possible and no opinionated frameworks That is highly opinionated and the opinion is based on Google’s business model, resources, operational strategies and engineering wherewithal. No startup has anything like any of them.
- nivertech 2y ago
  > Writing the same in Go would include a lot of boilerplate. Yes, it would be very hard for LLM to write this boilerplate. It’s so long it would not fit in its limited context brain ;)
  - apetrov 2y ago
    still you have to maintain the pile of boilerplate code and whoever does it, has a very narrow context window (aka human)

dondraper36 2y ago

I just opened the official starting guide from the official RoR website and am very excited, to be honest. I mean, the Go way of as few dependencies as possible and no opinionated frameworks is cool, but getting so much done for you is such a nice thing when you want to build fast. Also, switching to a purely REST API with just render json: <blah> is unbelievably fast. Writing the same in Go would include a lot of boilerplate. Anyway, thanks for your response. I am really happy for Ruby, RoR, and the community.

brudgers 2y ago
Congratulations on starting! the Go way of as few dependencies as possible and no opinionated frameworks That is highly opinionated and the opinion is based on Google’s business model, resources, operational strategies and engineering wherewithal. No startup has anything like any of them.
nivertech 2y ago
> Writing the same in Go would include a lot of boilerplate. Yes, it would be very hard for LLM to write this boilerplate. It’s so long it would not fit in its limited context brain ;)
- apetrov 2y ago
  still you have to maintain the pile of boilerplate code and whoever does it, has a very narrow context window (aka human)