mousetraps

fixed!

Thanks for the response. <- no exclamation point, just for you

My manager always jokes that I have caffeine running through my veins, so you're not too far off the mark ;-)

awesome, thx for the pointers!

Thanks, we'll keep that in mind for the next survey. That's something we went back and forth on - those are always some of the most interesting fields, and we didn't want people to consider the field as unimportant and skip it because they were optional. On the other hand, I can see that it would be annoying for it not to tell you you're missing fields until you submit. Maybe we can try editing it tomorrow to do a quick a/b test and see if it has an effect on % (good) responses for those questions...

That's a fun question :-). Technically it's not, but we're interested in supporting the entire node.js dev experience. One of the advantages of node.js is the ability to move between client side and server side code without switching contexts, so we want to ensure we properly support people working on both.

I also personally get the sense that the lines are being blurred between node and JavaScript (especially now that Npm brands itself as the JavaScript package manager). Curious if anyone else feels that way?

And yeah... You're right... Id be pretty surprised if anyone used node without Npm... Well at least it might serve as an indicator that someone read the question and wasn't just checking random boxes :-)

node.js too https://nodejstools.codeplex.com/

Seattle actually has a similar sign-based system in place. I rarely have trouble finding a spot, but I moved here recently so unsure how it compares to previous system. http://www.seattle.gov/transportation/parking/signs_icons.ht...

You can't really compare them. MonoCross is a crossplat MVC framework that you use on top of Xamarin's Monotouch/droid/etc. to increase your shared code. Xamarin allows you to write about the same code for multiple platforms, but it doesn't make it easier to share the same exact code. E.g http://components.xamarin.com/view/xamarin.mobile

The code looks similar across platforms, but it's not exactly, the same - you can't make one change and have it carry across to all platforms. Monocross brings you closer to a write-once for all platforms experience.

A better comparison is Monocross v.s. MvvmCross

I intuitively agree about the reduced scannability, but do you happen to have a link to the study? I tried searching for it to no avail.

You can also use the Office Web Apps to edit your documents online, whereas in Dropbox/Google Drive, you'd have to have Office installed.

They had skeletal tracking, but it wasn't reliable enough for consumer applications:

- OpenNI requires a calibration pose, while the technique Microsoft uses allows players to walk in and out of the frame. Kinect would not have succeeded if people had to calibrate it all the time.

- Microsoft does predictive analysis so it's much better in non-optimal environments (e.g. a living room) or in cases where it loses track of a body part because it's behind something.

- Also. To train it. Microsoft generated and processed millions of depth images from mocap data taken of people of all sorts of different shapes in sizes in all sorts of environments. It's insane. And of course they needed new algorithms to manage that...

- Lastly - no audio/speech or 3D facial expression tracking in NITE

PrimeSense provided a low cost chip, but Microsoft:

- did the product design and put it into a friendly package (take apart a Kinect some day, they did some neat stuff in there)

- developed the body tracking algorithm (http://research.microsoft.com/pubs/145347/BodyPartRecognitio...).

- developed the microphone array, speech recognition algorithms

- provided developers the resources they needed to take advantage of the device

- applied it well to gaming and quickly brought it to market

- put the technology in the hands of millions, triggering even more innovation