Should carbond be carbon-io?

[tfogo]

Jotting down my current thoughts on this:

This is the current structure (not a dependency map, just how modules are exported):

• carbon-io
  • carbond
  • carbon-core
  • atom
  • bond
  • ejson
  • fibers
  • http-errors
  • leafnode
  • logging
  • test-tube

carbon-io just wraps carbond and carbon-core. It would simplify the project structure if we just let carbond wrap carbon-core and made it the top level module.

@willshulman, when I was talking to you, you seemed to like the idea but you had two concerns that you said we should mull over:

1. The initial reason this was structured this way was due to issues with versioning. Do we see any potential issues with versioning switching to this structure? We should probably map out the dependencies of the modules to see if there are any weird shapes that might cause issues.

2. You didn't want the top-level namespace to be crowded. Having all the carbon-core modules alongside the carbond exports would dirty the namespace. This could be solved by exposing all the current carbond exports on a carbond property.

let carbondExports = { ... }

module.exports = {
  carbond: carbondExports,
  atom: core.atom,
  ... etc...
}