3 ms·
Yes, very similar but nowjs includes a lot more specialized functions and namespacing conventions. However, with any library that you simply require in your no
by rgbrgb 14y ago
Yes, very similar but nowjs includes a lot more specialized functions and namespacing conventions.
However, with any library that you simply require in your node.js app, there is a certain amount of boilerplate code and HTTP stuff that you have to deal with before writing your remotely accessible functions and application code. With Joint, we were trying to figure out the most minimal way to whip up a single page web app that does some real-time stuff. We think that not exposing protocol/header stuff makes programming this stuff a little more fun.
Also see the responses regarding DNode.
- SjuulJanssen 14y agoI've been programming with NowJs and could you point me to the "Boiler plate" stuff you're talking about? I don't get it. It is very clean.
- rgbrgb 14y agoSo at the top of any nowjs app you're going to have some kind of HTTP stuff to serve files and something about listening on a port. You might also have some Express stuff with routes. If there's logic there that you need, Joint isn't going to work out. If you can get by with the limitation of just serving static files, Joint will take care of that setup and encourage you not to reach for HTTP when you add a feature, nothing personal.