Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add comparison to Duo #4

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

jasonkuhrt
Copy link

Add comparison to Duo. Pretty rough, just a start.

Add comparison to Duo. Pretty rough, just a start.
@jasonkuhrt
Copy link
Author

Based on issue #3

@jasonkuhrt jasonkuhrt changed the title Update README.md Add comparison to Duo Nov 23, 2014

A package system that supports any `ComponentJS` module as well as, thanks to file-path walking, any `bower` module or module that otherwise has a built `distribution` file committed to the repo, on Github.

A manifestless system wherein module `require`s are recursively crawled to build a dependency tree. Moudles may be CSS or JavaScript files. Dependencies of CSS may be any static file (which are reliably output into the final build), other CSS modules, other types via plugins. Dependencies of JS may be `.js`, `.json`, `.svg`, `.html`, and others. Further, like with CSS, plugins may add support for additional types: `.yaml`, `.coffee`, etc. Plugins may also transform files (e.g. `5to6` to convert ES6 JavaScript into ES5 JavaScript) or inject synthetic files (e.g. allow the application to `require('env')` to access `process.env` etc.).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small typo in Moudles 😀

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Will fix.

@jhnns
Copy link
Member

jhnns commented Nov 24, 2014

👍

@jasonkuhrt
Copy link
Author

@sokra Might as well merge and let improvements continue rolling in. No point in holding this up for days.

@sokra
Copy link
Member

sokra commented Nov 25, 2014

hmm...

This is not a comparison about build systems or package managers. I just wanted to compare the module style. This means you shoud concentrate on these questions:

  • how are dependencies declared by files? (i. e. CJS, AMD, @import etc.)
  • how is the type of a file declared? (i. e. css, js, es5, etc.)
  • how are files preprocessed?
  • how are the concerns divided between application developer and module/package developer?
  • how are different environments (node.js, browser, webworker, node-webkit, etc.) handled?

Your duo comparision is pretty good, but it doesn't fit the intend of this document. Parts of your commit are useable, but I havn't had time to extract it yet...

@jasonkuhrt
Copy link
Author

@sokra Don't bother extracting anything, I'll just integrate your feedback, now that I have it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants