I recommend nvm on your dev machines.

    $ nvm install 6.6.0
    Downloading https://nodejs.org/dist/v6.6.0/node-v6.6.0-darwin-x64.tar.xz...
    ######################################################################## 100.0%
    Now using node v6.6.0 (npm v3.10.3)
    $ node -v
    v6.6.0

DRW is hiring SOFTWARE ENGINEERS in CHICAGO for ONSITE employment. (DRW also has offices in other cities, including London, Montreal, New York, and Singapore. Other roles are also available.)

https://drw.com/careers/listings

I work in software engineering in Chicago, so that is what I know about. We are looking for people who care deeply about programming. We write systems that last for years so we strive for good design, extensibility, and maintainability.

DRW is a proprietary trading company with no outside investors or customers.

The interview process for SEs is thorough. It will include a phone screen, a take-home exercise, and a multi-hour on-site including pair programming.

Not surprising. Lots of kids are holding out hoping that someone will get elected and wave a wand to magically erase the money they borrowed.

I have read so many articles which incentivize switching from Node.js to Go and every single one of them (this one included) blabber on about the Node.js event loop becoming congested - This is completely misguided - It only shows that the engineer didn't understand the problem.

A single Node.js instance runs its business logic in a single process. A single Go instance can run its business logic in multiple processes. Of course if you're comparing a single instance of Go running on 4 CPU cores, it's going to be faster than a single instance of Node.js running on 1 CPU core.

But the thing the author fails to mention is that there are a lot of Node.js modules which help you easily scale across multiple CPU cores. E.g. PM2 https://www.npmjs.com/package/pm2

Had the author of the article actually understood the real cause of the problem, he would have saved himself and his company a lot of time.

Nodejs is still outpacing Golang according to Google Trends and yet I have never seen a single article about switching from X language to Node.js. My guess is that the Go community probably wouldn't exist if it wasn't for this constant form of aggressive propaganda/marketing. Node.js on the other hand doesn't need any marketing/propaganda; it just sells itself.

If you have a scalability problem with Node.js (or any language for that matter) and you can't find a simple solution that doesn't require rewriting your whole app, you're probably not qualified to manage this project at scale - Because scaling across multiple CPU cores is kids' play compared to scaling across multiple machines. Heck, my grandma could scale this thing across multiple CPU cores.

Personally I think Node.js is great because it encourages you to think about these problems sooner rather than later.

Take a look at Susy for layout, bit more flexible than Bootstrap:

https://github.com/oddbird/susy

Also for static site generators take a look at:

https://middlemanapp.com/ (Ruby) http://gohugo.io/ (Go) https://github.com/getpelican/pelican (Python)

When you need to go beyond static sites and take a look at the web frameworks - Ruby on Rails is the obvious one, but I reckon that Meteor (https://www.meteor.com/) could be a good bet now that it has matured. Might save you a lot of time when compared to RoR for certain tasks.

From the hardware FAQ on /r/oculus:

"Can I use a weaker PC for basic content?

With weaker hardware, it may be possible to run very graphically simplistic content like virtual desktop, virtual cinema (for watching movies), and 360 videos, however you will be totally on your own without support if you choose to do this, and it is unlikely that there will be many (or any) games that support lower specs.

If you do wish to take this non-recommended path, your PC must at least meet the absolute minimum requirements:

    Video Card: GTX 650 / AMD 7750 desktop GPU or better and newer
    USB Ports: 2x USB 3.0 ports
    Video Output: free HDMI 1.3 output
    OS: Windows 7 SP1 64 bit or newer

Remember: The Rift will not run on your laptop, this rule does not change!" https://www.reddit.com/r/oculus/wiki/requirements

Personal or not, our entire company is devoted to making Trails the best damn backend framework for node. We don't distract ourselves with VC-funded side projects, and we don't have a automated bot that closes everyone's issues (see: SailsBot).

Our company lives off consulting around the open-source tools we build and support. That's it.

Clickables:

http://www.buildcampus.com/

https://quip.com/SerKA2wVqgQl