jakerella86

Hi! My name is Jordan and I'm a USDSer at the DoD. I'll be sharing my experiences trying to open source software within the DoD at the upcoming Mid-Atlantic Developer Conference in Baltimore (Aug 1-2). As Robbie mentioned, some of us also participate in many of the user groups around town, including DCJS and Women Who Code DC.

Really meaningful work, and some of the most dedicated people I've ever worked with.

Seems like these tools are still evolving, wondering how long it will take for these to really be adopted in enterprise orgs (thus fueling more growth).

I'd agree that Node.js is pretty dang nice for RESTful APIs. The fully asynchronous nature means really great throughput on the server, especially when most of your processing time is spent in DB or file I/O (as is often the case in APIs). As for disadvantages... I dunno. I guess if you don't really know JS very well it could be difficult to get into, and good developers are harder to find than in some other languages. But as a platform for APIs it's pretty solid.

As for a guide... There's a guide for LoopBack specifically here: http://docs.strongloop.com/display/LB/Getting+started+with+L... That framework was written specifically for writing REST APIs.

Curious to know if anyone is using RethinkDB for an IoT project (more interested in home use)...

And if you follow them on Twitter there are some good conversations back and forth. ;)

Or just require devs to use --harmony. I think there are a couple modules that do so... like koa. :)

Of course, since that's basically "experimental" I guess people would think your module is also "experimental". But I think let and const are pretty darn stable.

Also note that even in io.js you need to enable "strict mode;" in all scripts!

It's in Node.js v0.12.0, but only with the --harmony flag (and I think you also have to specify --use-strict).

Rand (the main docs guy right now) has been doing a ton of work on this, and still more to come!

Only if you're not already the "in crowd", right? I mean... if you have commit rights, it's the same...

Not sure if I agree that everyone wants a single Node (Isaac's first point), but I agree with most of the points. That said, I don't know that we will get to reunification. :/

The license is one benefit, yes... but the StrongLoop PM also has support for deployment across multiple machines and integration with nginx for load balancing. And everything can be monitored (including across machines) from a single GUI: StrongLoop Arc.

pm2 is great, but this is not an "added features" play, StrongLoop wrote this process manager from scratch based on experience with very large enterprise clients. In other words, this is a new beast entirely!

Heh... I think that's why the announcement hasn't been made on Twitter and such just yet. Waiting to see if they need to immediately release 0.12.1