georgecalm

Kei, I've just installed the node_sample "Hello World!" project on the free plan, and noticed it was running a bit slow. Apache bench shows an avg of 1471ms/req over 100 requests (from NJ). Do you provide faster response-times on the other plans? Where are the data-centers located?

Looks great! It's very simple and useful.

One comment: on both (interviewee & interviewer) page I'd recommend having a box in the right rail with the following:

"Give this pin: * to the interview[er|ee]. If you already have a pin, enter it here:

[ INPUT BOX ]"

I've just printed a copy for my wall, and it's beautiful! If you had a poster, I'd buy it :)

One request: please switch from W3Schools to the official W3C spec for the "more-info" link.

The fact that it's all std-based, and back/front-end rendered is beautiful, but what seriously bothers me is how much weld.js is tied to jQuery.

The README states "Use with whatever library you want, jQuery for example". Let's analyze that for a second.

Weld.js uses the following jQuery methods: - Sizzle selector ($) - first() - is() - val() - attr() - text() - map() - extend() - clone() - data() - remove()

These methods are used throughout the 249 lines of code.

This makes weld.js completely dependent on jQuery. Thus, you can't just use whatever library you want. And that would be allright, if the README would say that; but it didn't, and so it isn't.