I'd suggest no. If Rails is the right tool for the job, there is no reason to not use Rails. If Rails is not the right tool for the job, reimplementing Rails o

I'd suggest no. If Rails is the right tool for the job, there is no reason to not use Rails. If Rails is not the right tool for the job, reimplementing Rails on top of Go isn't going to make it the right tool. It is possible that some future "killer app" will emerge out of the Go ecosystem like Rails did with Ruby, but the effort to build something like Rails to duplicate Rails is not a particularly good use of someone's time.