[jksmith]

This.... This is about business, getting to market, making money. It's not about programmers' pet interests - those days are long gone. That's why it's important to pick a toolchain that's 1) easy to code, 2) easy to test, and 3) easy to hire for with a reliable expectation of skill level. Unless you're plugged into a small team of very advanced programmers, and this small team is all you'll ever need, you won't be using something like Haskell. Likewise, if you choose a MSFT toolchain, and are hiring blind, you're likely to do a lot of interviewing, because the market is flooded with programmers with this background who claim to be seniors but really aren't, and you can end up with a messy project with lots of tech debt very quickly if you're not careful. One toolchain I've used that does meet those three criteria I mentioned above, therefore letting you get shit done that is closer to being on time, in budget, and correct, is of course golang.

One more point: It's important to understand what parts of your app are capitalizable, and which parts are aren't. The really capitalizable parts are the ones you think bring real competitive value to the market you want to attack - the code that addresses your valuable SME and original ideas. So something to ponder: if you want to also develop a presentation layer, how valuable is it really to develop that layer internally when in the long run that work is not much of an asset, and is a time hole for development? No matter how skilled your team is with the latest js framework I can guarantee you that there's some team of kids out there who are much better with the same framework and can develop your UI at half the price. So create your mockups, define your inputs and outputs, and farm that shit out. Unload the UI headache while in startup mode.