I'll say a couple things. First, yes, node embraces the UNIX philosophy of
having lots of little modules that perform small tasks that can be combined in
interesting ways. In node these modules are usually hosted on npm. As you
develop your application, you'll probably find some functionality you've
written can stand on its own; by all means, separate that out into its own
module, license it liberally, and publish it on npm, and then use that module
in your application. Of course you don't have to license it liberally and
publish it freely; you can still benefit from modularization even if you keep
the code to yourself and host it in a private repository.
Also, there is benefit in writing the same kind of code for the client and
server. That not only means using the same JavaScript language, but also the
same module system and modularization. In node it's nice to put different
functionality into different files and tie them together with require() and to
have access to the vast npm module repository; it's annoying when you try to
run such code in the browser and it doesn't understand ("require is not
defined"). Many tools exist to solve this problem; I use browserify. Perhaps
you will find it or one of the other similar tools useful as well.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
