If you're not a tech founder then you probably shouldn't ask to use a particular stack/approach. Let that conversation at least be started by someone who knows what they're talking about. What do you say? You say that you want to convert a desktop app into a web app, and take it from there. The app itself may start to dictate the approach anyway, which we can't speak to without any details.
Davelnewton, appreciate your response. My experience is that if I ask 2 or more developers, I get the food fight that Anold and Maxx are having below. So if I pick a developer out of the internet and he/she recommends "Atom" I know I need to avoid him/her. On the otherhand, if he/she says "React", I know at least 2 others have mentioned it. You suggest that I just talk to a developer and put myself in their hands. Th…
You'll always be putting your trust in someone if you're not doing it yourself. There's no way to absolutely guarantee what's being done is an effective path, but you can always have development plans vetted by a third party, and it may be worth it.
In the JS world there's always a "flavor of the week". There are several standouts, e.g., React, AngJS, EmberJS, whatever. The back-end isn't as relevant if all it's doing is shipping data to the client (browser), but infrastructure costs and maintenance always matter. It also depends on what the back-end actually needs to do (batch jobs, timed jobs, etc.) but you have a lot of flexibility in this regard.
Feel free to reach out if you have additional questions; I'm reasonably easy to get ahold of.