On Tue, Jan 22, 2013 at 7:00 PM, Austin William Wright
<[email protected]> wrote:
> On the contrary, what sort of project could Node.js be if everyone actually
> cared about doing things the objectively correct way.
"Objectively correct"? Wow.
Node programs run on filesystems. Every step of indirection away from
"the file on the filesystem" to "the string in the require()
statement" is a cost. Some of those costs provide some benefit, like
how require("foo") can be either locally in node_modules, or up a
level, so that modules can share dependencies (but don't have to, if
they would conflict). Other costs, like how require("foo/bar") can be
either foo/bar, or foo/bar.js, or foo/bar/index.js, are simply
historical mistakes that seemed like a good idea at the time, but
provide no value, and are now too costly to remove.
> Out of simplicity and
> extensibility, however, most of the time you're going to use the filesystem
> to define a module.
100% of the time is "most of the time", yes.
> Cross-platform compatibility is a highly desirable feature.
Cool story.
--
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
