New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Take it from someone who has done multiple node.js projects and is not going to touch nodejs again, its not worth learning. Down the line you will start having issues with the concurrency model (long running tasks), sphagetti code and a lot more and once the codebase grows, its gets harder and harder to manage. If you do decide to stick with it, here are some good learning resources :
http://nodecasts.net/
http://www.nodebeginner.org/
https://github.com/tj/masteringnode
What language did you end up deviating to?
Right now I am primarily using Golang and also some Java and PHP on side.
Async.js/Promises solve both problems and they're far worse in other languages/frameworks, so I don't see why this should be a dealbreaker...
Interesting, I'll need to check that out.
Well people only abandon something when they simply did not understand something.
That's it. This is the only reason. Why did you hate to go to specific classes as school? Exactly. Who the fakk know what the teacher was talking about?
Same happened me back way back in years with Ruby on Rails. I was a PHP spaghetti code maker.
So when I met with RoR and after just creating a simple model (almost just a file) and it was able to read the database and it's all fields. I was too shocked, I did not understand that, it was so off, I couldn't figure it out. Why is it working?! What is these views? I do not get, so after 3 hours I left. Then realized the principle that I mentioned, so I bought a book, and now I can code it. However since clients usually needs something "easier" so their system administrator can handle the installing I switched back to PHP (Laravel). 
But back to the topic, first: Why do you want to learn it? What do you want to code? Is it the hype?
You see, you can join the fanboys, but it is not the One Ring situation, to rule them all. :P
I still use node. Twice I did a whole App in it, but now instead I use it for it's characteristic. So whenever I need some realtime or non-blocking stuff in my App I use it also.
Well of course I had to ask my current client's system administrator if he can handle node, he said no problem. 
So I could skip this part: doing some AJAX or any other method that calls a route on my Laravel and checks every 3-5 seconds if there is any notification... which would be a bit longer then 30 lines, and would required to code the server side too. 
My current project is Laravel 5 + mySQL + redis + node. What I'm using node for? For Realtime Notification, socket.js. With 30 lines of code my realtime notification works very well.
You see, you can join the fanboys, but it is not the One Ring situation, to rule them all. :P
I'm building a couple of real-time web apps and after doing some research saw that a tech stack with Node.js could work very well. Also wanted to get more immersed with JS too.
I would definitely not use it for all projects.
I suggest you starting with CoffeeScript. It gives you a better overview of the code.
>
You'll do well with NodeJS. I've built about four small real-time apps (WS) and they perform good. You have plenty of libraries that will fulfill your typical needs and there are ways to avoid spaghetti code easily. Perhaps you want to start getting familiar with io.js (https://iojs.org/en/index.html) if you need to use the latest ES6 features for example.
Cool have you enjoyed using the language overall?
I'm more of a Python person but I can still enjoy it