English Original:Why does Google despise Node.js? Answer Request
Some people ask questions on Quora, why Google does not like Node.js, Google's UX engineers and developers from the Node.js team answered their views on the issue, for the programming language, each language has Its own advantage, it is important how to use it to solve the problem.
Google UX engineer Sean Grogg:
For any language, Google has a neutral attitude, only the so-called Big Three (Java, Python and Go) exceptions, these languages have their own special advantages in the use of the project they do not need additional instructions.
As a business, Google has no prejudice against Node.js. I wrote a lot of React code, they are dependent on Node, some of which code is still even in Google's megarepo.
Of course, there may be some individuals or teams who do not like Node.js. There are some people who do not like it, but there are a lot of people who can see the value of Node.js, especially the Cloud team.
Node.js is the only language currently supported by Cloud Functions
It is also part of the App Engine flexible environment
It is also a lot of products client library (Compute Engine, Cloud Storage and Datastore, etc.)
Node.js Team Andreas Madsen:
Google's V8 team has a close collaboration with the Node.js team. In the recent Node.js 8, we guarantee ABI compatibility for subsequent V8. If there is no close cooperation between the two teams, we can not do that.
Node.js is also working with the V8 team to develop the PromiseHook API, which allows developers to use C ++ to detect all promise. It allows us to add support for promise to the domain module, and it is also a major component of the new async_hooks API.
This shows that Google hate Node.js is completely nonsense.
Topseptools.tech SEO Manager Muhammad Saeed:
In the use of Node.js, you can not deal with multiple cores at a time, than the need for multiple instances of the spin. Worse still, its cluster API is still just an experimental feature.
I do not like Node.js because it's smart to use a core when running tests with headless browsers. Unless you can learn how to allocate the tested load, running the test in the real browser will be faster.
Debugging is also a problem, if you are using the cluster library, it will not work properly. I very much hope that Node.js can solve this problem.
Compiled: Lu Xingyun