Why is this one big repo rather than many little repos? (one repo for each component) about noflo-strings HOT 1 CLOSED

It's mostly for legacy reason. A lot of these components used to be part of NoFlo itself. When we decided to migrate all components out of NoFlo into their own repos, we separated them into several major packages: noflo-core, noflo-strings, noflo-packets, noflo-objects, etc. There just so happened many more components manipulating strings.

I must note that it's not necessarily the case that one repo has only one component. In fact, that's rarely the case. It's more common to have only one public-facing component though.

For backward-compatibility, components/graphs in core packages like noflo-strings will not be moved out at least until NoFlo v0.5.0 (perhaps even permanently). Feel free to write your own components to work alongside with core components. Composability and choice is one feature of flow-based programming that I absolutely love. ;)

By the way, I'm a HUGE fan of DocPad. Thanks for the wonderful creation.

from noflo-strings.