How to deal with the fear of using Javascript on the server?

Question

JavaScript

We choose with colleagues on what to write the next REST APIs service.
Previously, we almost always used WCF.
I suggested considering alternative solutions, especially Node.js.
But unfortunately, colleagues with more experience in C#\Java development do not perceive Node.js as a mature solution for commercial development.
I would like to clarify for myself what this feeling of colleagues is largely due to: fear of using new technology or do they still see real pitfalls?

Answer 1

I think the fear is very simple - because of the lack of feeling of support. Big Brother like MS or Oracle is not behind Node.js. Of course, I don’t want to say that no one cares about him and no one will offer support - another thing is how popular these firms are.
A related issue is the availability of things that are important for commercial development. If you've used WCF before, it's no surprise that after a gimmick that supports a huge amount of standards for old-school XML web services (with security, addressing, etc.) and even REST services out of the box, many will want to go to the node. and re-assemble the necessary tools and libraries there, even if they exist (which, of course, must first be checked).
And, finally, the main subjective factor is the desire to use the acquired skills. WCF has a pretty decent entry threshold, and it takes a really long time to figure it out before you can put something into practice with an understanding of what is happening. It’s like people have been indignant with WPF lately - everyone spent N months studying (one XAML is worth something), and over the past 6 years there haven’t really been any innovations or updates from Microsoft, everyone is looking at ASP.NET rewritten from scratch (which is now all platform leads in the right direction), and envy. So you come all dressed in white and say - don't worry about your corporate dotnet baggage, we're all going to the node.

Answer 2

Show them its advantages over other solutions.
But there is a suspicion that colleagues are simply stuck on one technology and do not want to consider something new.

Answer 3

Fighting fear is useless, so the whole life will go to the fight.
If they are afraid or do not want to, then there is nothing to help them, except for their own example.
Only personal experience and example will convince you.

Answer 4

Have you tried asking your colleagues? :-)
I will speak for myself. I'm spinning in a "bloody enterprise" in Java. I deal with JavaScript only on the client. The word debug in relation to JavaScript gives me phantom pains. You can write code, but how do you debug it? Debugging in a way that feels good? Maybe someone will answer and dispel my fear?

Answer 5

node.js is when front-end developers try to take care of the back-end, and drag what they know there?

Answer 6

I would say that a lot depends on the task, I have been using a rest node for the last couple of years - but this is convenient when you live in a world of "floating" code - if there is a clear TOR and a development plan for a couple of years that will not change - perhaps there are other solutions, maybe I would choose a java stack - just due to the maturity of the platform and libraries, but if we host on Windows and connect only from Windows applications - I would question the rest and use C # (a wonderful and flexible language).
Any solution has pros and cons, and it is necessary to look at the task itself, ideally, having experience of using the platform in production.