Re:Fixing the callback spaghetti in node.js
by justatdotin on Thursday September 29, 2011 @04:44AM
(#3051643)
Reduce complexity: sure.
But if we have requirements that can be well defined within an async FP paradigm, then maybe an async FP environment isn't such a 'problem'... and many of us "average programmers" already know lisp.
If nodejs doesn't suit everyone, probably not everyone should use nodejs. But if we're going to have a go at it, let's not immediately dismiss node's natural style as "an absolute mess"
Re:Fixing the callback spaghetti in node.js
by artsrc on Thursday September 29, 2011 @04:56PM
(#3054260)
Handling concurrency should be an accepted part of the skill set of GUI development.
Writing a user interface that can respond to user input, whilst also being able to handle and respond to a long running data access or computational requests is a concurrent problem.
Having a single threaded model with callbacks, like the JavaScript browser model is one of the less complex ways to handle this.
I agree that a less complex model is appropriate for some developers/applications. But to call yourself a "skilled-professional GUI-developer", you need to get awesomely brilliant enough to handle this.
Remember that not everyone is as awesomely brilliant as you are.