Published on May 3, 2019

This is sort of a continuation from yesterday, but I think it's separate...

I've seen a lot of talk about what stack people use lately. I think people get caught up with this too much. Obviously, the Rails stack is the one to rule them all - I jest, stack does not matter.

That being said, I love the Rails stack. As DHH said in his Rails Conf keynote, Ruby was designed by Matz for developer happiness, what a wonderful thing. Rails is a beautiful language. I've tried other stacks, including PHP, Java, C - nothing compares for me. I sometimes wish I was more of a polyglot, but then I remember one key principle.

Stack does not matter.

Whatever you choose, the goal is service. A user doesn't care about your stack. When you're starting out, you don't need to worry about scaling to a million users - you might never get a single one.

My problem with trying a new stack is that I always think I can do this better with my old stack. Then there is more overhead when it comes to DevOps, deploying and maintenance. I might have already solves these problems in my existing stack, what would I gain from using a new stack and learning this all again?

Is that short sighted?