231 reputation
36
bio website heliosstudio.ca
location Penticton, Canada
age 35
visits member for 3 years, 3 months
seen Sep 29 at 22:05
I'm a web developer who loves database design and hates Internet Explorer.

Aug
27
comment Is there a good reason to avoid node.js for non-realtime web apps?
so you think there's not really much against using Node in place of more traditional app stacks; the issues are more to do with real-world concerns?
Aug
27
comment Is there a good reason to avoid node.js for non-realtime web apps?
+1 ease-of-use in setting up multiple hosts is definitely worth consideration.
Nov
4
comment Is there a good reason to avoid node.js for non-realtime web apps?
I know that I do have to load up an interpreter some time, but I see a benefit to having one instance of the interpreter running all the time (for low-CPU apps, of course) as in Node.js rather than having interpreters spin up and terminate with every request, as in PHP.
Nov
2
comment Is there a good reason to avoid node.js for non-realtime web apps?
@default.kramer thanks for the reminder; I tend to take people's opinions as gospel. His major valid criticism seems to be that you shouldn't use Node.js for CPU-intensive tasks. I'm confused about his criticism of worker processes; is there any big problem with creating separate workers for specific tasks?
Nov
2
comment Is there a good reason to avoid node.js for non-realtime web apps?
heh, thanks for the caveat. I do remember your comments on the node.js chat about using other people's model libraries (Backbone.js, etc) and realising that I was spending too much time learning Backbone.js and not enough time just taking advantage of (and learning) JavaScript's prototypical inheritance mechanism. Good advice; I feel much more relaxed now.
Nov
2
comment Is there a good reason to avoid node.js for non-realtime web apps?
Point taken about HTTP being stateless and realtime-ish; however, I'm more interested in the pragmatic concerns about the typical definition of realtime: high volumes of low-weight requests. It seems a bit overkill to spin up a new PHP instance just to spew out three or four lines of JSON sometimes. Am I correct, or am I just suffering from parrot syndrome?
Nov
2
comment Is there a good reason to avoid node.js for non-realtime web apps?
So you think that pragmatic principles like familiarity, availability of libraries, etc, are strong arguments for a certain platform, eh? Those are good thoughts, and they're definitely things I'm considering. (I'm surprised you're advocating for out-of-the-box solutions; I thought you were a roll-your-own kinda guy!)
Nov
2
comment Is there a good reason to avoid node.js for non-realtime web apps?
His hatred of JavaScript seems to be an important issue too, which I fear might be partly responsible for the energy behind his argument.
Nov
2
comment Is there a good reason to avoid node.js for non-realtime web apps?
wow! Rather opinionated chap, eh? In the follow-up article, he seems to be saying that, for high-I/O and low-CPU applications, evented and threaded systems are roughly on par, and that the problem lies with novice programmers who don't know when to give up on events and spawn a new thread. But the ignorance of the programmer doesn't mean the tool is bad, does it? I do agree that using an environment whose forté is event loops for CPU-intensive tasks is a bit weird, but is it evil?