Ask HN: Choosing an entrepreneur's stack in late 2018?

Hi HN. I'm a CIO by day, entrepreneur by night. I used to write a lot of code, but the last few years have been dealing with coordination of many projects post-acquisition and haven't kept my hands as dirty as before.

I have a few ideas I'd like to build MVPs for. I'm trying to decide what the best components are to include in my stack. My requirements are a web backend (including PostgreSQL support), a web client, and mobile clients for iOS and Android. I should be able to develop this from Linux as much as possible, but I have a Mac I can jump to as necessary.

I'd like to avoid as much complexity as possible in the stack so I can focus on the business idea instead of spending hours worrying about tooling, etc. Dart (with flutter) seemed appealing at first for this, but comments like this (https://news.ycombinator.com/item?id=17708671) as recent as four months ago don't really bolster confidence there.

If you were building a MVP from scratch and didn't care about using what you know (were willing to learn new tech for a better experience) what would you choose and why?

Server, web, and 2x mobile is a very tough requirement to meet. If it's just CRUD stuff I'd settle on ReactNative for mobile and use either clojure or js (both have the same reach in this case, but arguably clojure gives you a more unified experience).

But if you're pushing the envelope on mobile I don't think you're gonna pull this off to be honest. Consider reducing scope if possible.

Take a look at the recently announced phoenix framework live view

It depends on your exact requirements. If it's something crud based go with an established framework like Django or Rails. Both of these have mature communities, ample tooling, and aren't going anywhere soon.

If you're looking to simplify as much as possible from your own perspective, consider using something like Next.js so you only have to learn one language. But you'll have to make other choices, so it's a trade off.

I wouldn't go 2 native clients on mobile, but perhaps ionic framework instead.

I have to admit...I'm not the biggest fan of javascript (largely based on old history) and the node.js craze has passed me by...but I'm open minded. I'll definitely take a look. Thanks for your response.