V
V
Vlad Timofeev2014-12-09 16:42:28
Node.js
Vlad Timofeev, 2014-12-09 16:42:28

What is impossible / problematic to implement on node.js?

How many bad people have already heard from people about the node ....
Actually, the whole point of the question is in the question :)
If anything, I do not ask you to do a dissertation if it is not difficult for you .. point at least by example ..
I will be very grateful.

Answer the question

In order to leave comments, you need to log in

3 answer(s)
S
Sergey, 2014-12-09
Protko @Fesor

Real-time computing is problematic. Nothing else comes to mind. Well, yes, writing desktop software (not CLI) on a node is a perversion.
You just understand, you can do almost everything on brainfuck. The question is efficiency. Everyone is also talking bad about PHP, even those who only shit code in controllers on their favorite js / ruby. So what? Be above it.
ps In fact, everything is shit except bees. This is a harsh reality. There is nothing universal and suitable for all ranges of tasks. There are also subjective factors.

E
Elizaveta Borisova, 2014-12-10
@Elizaveta

I think there are objective factors besides philosophical ones.
1. It's really hard to write and maintain very large projects.
2. Reliability factor. Because of it, it is worth referring projects on Node more to solid prototypes.
3. Instability of infrastructure for developers, the need to fork modules to fix their bugs. And a split into 2 branches now.
Due to indirect factors, it is easier for large/highload projects in the kernel to use other technologies.

S
smanioso, 2014-12-11
@smanioso

https://www.npmjs.com - instead of a thousand words

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question