madebymany.com/blog/replacing-rails-part-2-amazing-tooling

I come from a compiled language background (C, Objective-C) and I've been thinking for some time now that Rails isn't always the best tool for the job. Memory usage, performance, deployment and too much "magic" are an example of some of Rails' weak points, points I find to be of great importance in the larger scale apps I've had to write or maintain.I remember reading the initial release of Go and being excited! A statically typed language with garbage collection, a compiled language where concurrency is a first class citizen and a standard library which has everything you could ever need, 90% of what you need is already there. Here's the workflow and tooling I've been using recently with Go.


Comments (0)

Sign in to post comments.