5 ms·
It runs on node, which executes javascript in a development environment.
by wetmore 14y ago
It runs on node, which executes javascript in a development environment.
- WiseWeasel 14y agoAh, I guess I had never really connected the dots, that to use node, you have to do your development in the browser. This is all starting to come together. ; ) [Or not, apparently.]
- deleted 14y ago[deleted]
- jchrisa 14y agoI use node, but I use a normal editor, not the browser
- WiseWeasel 14y agoSo then is there a step where you execute your node (and I guess Jam if you're using that) code in order to generate production client-side code from the node and jam-dependent code? Or is all of this for server-side code where the node and jam libraries would be installed?
- aidenn0 14y agoThis is confusing b/c there are 2 javascript environments involved. Let's pretend that instead of being written in javascript, it was written in ruby/python/c. Now it would look like this: "A (client-side) javascript package manager written in ruby/python/c" It's not for managing node.js packages, it's for managing client-side .js packages, and it just happens to be written in javascript to be run by node.js
- wetmore 14y agoWell, not exactly. From wikipedia: "Node.js consists of Google's V8 JavaScript engine, libUV, and several built-in libraries." So node installs a version of the V8 engine in your dev environment, so it can run js on the server without a browser. That's why jam requires node - it's written on javascript and uses node packages so it can work with the filesystem, and do other server/dev environment things that js in a browser can't do. When you develop with node, it's just like doing development for any other language. Edit: in case this wasn't clear - you aren't working in a node environment. In this case, node is simply used because it can execute javascript in a server environment. So jam can be written in js and do filesystem stuff if it runs using the node utility. Jam simply runs on node, but a project using jam doesn't necessarily need to be a node application.
- WiseWeasel 14y agoThanks for that explanation. One last question: why would you do 'jam install backbone'? Are people developing all their client-side code in the node environment as well? [Or, it seems like maybe node in this case is just a dependency for jam, which is simply a tool used to make all your JavaScript development easier, without introducing any extra runtime dependencies.]
- chrischen 14y agoI believe jam is targeted for the client side, similar in functionality to googles closure compiler.
- quarterto 14y agoThere are two sides to Node. One is the HTTP server environment you're thinking of. The other is just as a generic JavaScript execution environment, with packages for filesystem etc..