Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

A simple experiment to show to you can have shared code between frontend and backend without going nuts.

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 public
Octocat-spinner-32 spec
Octocat-spinner-32 views
Octocat-spinner-32 .gitignore
Octocat-spinner-32 Procfile
Octocat-spinner-32 README.md
Octocat-spinner-32 package.json
Octocat-spinner-32 server.js
README.md

NODE.JS WILL EAT YOUR CHILDREN!

The live site can be found here: http://node-js-will-eat-your-children.herokuapp.com/

During Euruko 2011 the guys from kopfmaschine delivered a talk in which they showed how they used the rubyracer gem to embed the V8 within a Ruby app to share code between frontend and backend.

During the questions somebody asked why they did not use node.js and the answer was that they did not know node.js but they knew Ruby.

As they were finishing the talk I was finishing a simple express-based node.js app which used shared code in the frontend and the backend.

The idea - to show how easy it is to set up. It's far from being perfect, but it shows that if you want shared js code on both sides, node.js is your friend!

And as Heroku launched node.js support I could not think of a better way to celebrate than to put it on Heroku so here it is!

So if you're afraid of node.js, don't be - it will not eat your children.

Something went wrong with that request. Please try again.