JavaScript: It’s Not Just for Browsers Any More

Post by subbu » Mon, Mar 08, 2010, 11:00 AM UTC

blasdel wrote: post #90

subbu wrote: post #77

Earlier quoted context omitted.

* A shitton of people are already using it on the daily This is actually a problem. Majority of that shitton use js without knowing what they are doing. It's a copy-pasted code for some client-side validation. Even the so-called framework-users (jQuery and Prototype) depend blindly on plugins for their job.

You aren't wrong, and I find Protoype.js incredibly depressing (see my third point). But the point is that you're not going to get fired for choosing JS on the server. It has curly braces! Your boss isn't so worried about hiring.

Post by Periodic » Tue, Mar 09, 2010, 9:18 PM UTC

rictic wrote: post #49

Periodic wrote: post #25

Earlier quoted context omitted.

If A, B, C, and D truly are asynchronous then I believe you're going to need condition variables and (at a lower level) locks. I agree that such syntax should be baked in and handled at a lower level. If you can guarantee that a given variable can only be modified by one process at a time, it is easy to do something to take care of this for individual processes, and wouldn't be hard to generalize. (note, I was last u…

Nope, no locks needed in Node. This is one of the little joys of javascript: no threading at all. None. With Web Workers you can have processes, but there isn't shared state; everything is done through message passing. All parallelism is cooperative in javascript, meaning that you don't have to worry about control flow switching out from under you at arbitrary points, just when you explicitly yield it by returning fr…