Thread replies: 10
Thread images: 2
Thread images: 2
File: download.png (2KB, 204x204px) Image search:
[Google]
2KB, 204x204px
I know I'm going to be cursed by even touching the topic of node, but I'm really in hope that someone in /g/ can help me out.
My tech lead had the brilliant idea to go with nodeJS for the backend of a webapplication that we need to deliver production ready. It gives me the chills by putting node and production ready in the same sentence. I know that Java is not perfect but if something goes wrong I'm sure I can go down to it and do the dirty work, with node? I'm afraid it will all go into flames. Mostly because there is really no one in my team that really understands it.
I hate the community around nodeJS. It's all shinny and pretty small examples, it's all so simple and fun to use. It kindda sounds like intellectual vomit, repeated across different dev blogs. Self promotion material, portfolios to complement your CV with.
It's hard to find resources where you just sense that the author really understands the topic, has the experience and you can proceed to read more from him. Most of the posts don't go beyond the basics.
But really, I have never really gave node a shot to surprise me. I sincerely hope it does.
Can someone please recommend me some good resources on nodeJS?
How it works, structure, error handling, good practices. Intelligent worth resources
Thanks
>>
https://developer.ibm.com/node/sdk/
>>
I feel you anon things like the node js event loop for concurrently handling many requests at a time by non blocking confused me. Basically you have to understand JavaScript well because node leverages weird aspects of the lang . Try this
http://eventdrivenpgm.sourceforge.net/
https://developer.mozilla.org/en-US/docs/Web/JavaScript/A_re-introduction_to_JavaScript
>>
>>61933004
The node official docs are everything you need.
You are right when you say that most people don't understand node and they should. The event loop as a LOT of quirks, for example.
The biggest advantage of node is that it's easy and fast to use and deploy.
The biggest disadvantage is that it's hard as FUCK to test and check for correctness.
>>
>>61933004
Fuck off
>>
>>61933004
quit your job sir.
>>
>>61933017
Nice.
>>61933004
This is a good, real source for Nodejs:
https://www.joyent.com/node-js/production
>>
>>61933004
The whole trick is to NOT build complex stuff with node.
Build microservices instead.
Which is a much better idea anyways.
>>
>>61933004
Non-blocking io isn't unique to node. See, java nio. You should learn how it works anyway.
>>
>>61933004
Careful with the habit of node hipsters of shoving every framework directly in the core of the application. In node world there is a big bunch that seem to have forgotten words like "loose coupling" or "DI" and it's a major fucking ass to switch when one of them stops updating, working or gets funny.
And that "stops updating" part is rather common in nodeland where everyone switches framework every 2 years.
Thread posts: 10
Thread images: 2
Thread images: 2