4 ms·

This question almost comes up daily nowadays. And I always reply the same "Use what you already know because unless you are at google scale, all languagues and

• fedebehrens 5y ago
  That's true - but decisions made on things like deployment/auth/hosting in the early days can give you a good base to build off of. For the first product we built it started off as a Laravel app but building in Javascript made more sense for us given the team we had access to.
  • codegeek 5y ago
    Not sure why you would need to switch from Laravel to JS other than the fact that your devs knew JS more ? Honestly, early days decisions are more about finding product market fit, customers and sales. If you cannot do those, you will be dead anyway and tech stack won't matter. If you are changing tech stack, the only reason to be directly helping do more revenue and almost always, tech stack is not the issue in acquiring customers and sustaining a business in the early days. There may be a handful (if any) of companies that failed due to tech stack selection. I highly doubt that though.
• criddell 5y ago
  > Build. Now. Great advice. Build now and hope that in a few years you need to change parts of the stack because you’ve outgrown them. That’s a great problem to have. There’s a good chance that the business that succeeds isn’t the one you are starting today. For example, IIRC Slack came out of game development.