Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
justamuslimguy348199dSure great idea. Why not.
If you have some special use case then look around at languages / frameworks you don't know. But for most sites, go with the tools you know
But I'm fairly sure (correct me if I'm willing) that you can't do multi threading with it.
N00bPancakes7682198dThere's lots to consider but generally there's no good answer.
RememberMe15417198dWhat you "should" be doing in generally a question of economics.
Can you afford to not care about raw performance and/or scale? Is it valuable to you to have a TS/JS codebase (eg. considering what the devs you work with know)? Does Node do something for you that eg. c# or go don't? Are you doing this for learning Node? Then sure, use Node.
Otherwise I'd recommend something speedier and more scalable, like dotnet core.
vomitmachine769198dAlong with the really good advice @RememberMe stated, I'd also ask about your team's infrastructure. Like is your team currently writing web apps in JS, c#, php, what have you. How experienced are you and your team with maintaining JS apps if you go that route. How long will your web app be in production. Try to estimate how many people will it serve.
My personal suggestion is that if your team is already writing stuff in one language and has a nice workflow for that language, meaning they use patterns in their code, make regular updates, can run daily builds, push to prod automatically, run unit tests automatically, then don't disrupt that by introducing a new stack. Instead experiment with that new stack outside of your work environment, come up with all the components on your own time and then slide them into prod on company time if you've deemed it worthwhile and your team is fine with it.
If you're doing this solo, fuck it. Build it and see if you like the stack.
JKyll6427198dDo it in whatever you feel comfortable or whatever you are willing to learn about.
HiFiWiFiSciFi4099198dPlease just use pure node with express until you figure how how to make a site/app “by hand”.
Then, and only then, look at using a front end framework like Vue or React or Bootstrap.
dontbeevil4489197dLess code in ts/nodejs compared to c# for instance? Sounds like you're doing sonething wrong