Consider renaming the library about repeater HOT 2 CLOSED

I’m thinking about using the name “repeater.” “Repeat” is a synonym of “iterate,” and in telecommunications, “a repeater is an electronic device that receives a signal and retransmits it,” which is basically what channels/async iterators do. It captures the iterative/asynchronous/concurrent nature of channels, isn’t widely used in the context of JavaScript/TypeScript, and follows a long tradition of borrowing concepts/names from telecommunications ("muxer", "duplex", "channel").

As far as breaking changes go, we would need to

1. deprecate all @channel packages (💆‍♂️) and publish new packages maybe under a @repeater or @repeaterjs org name. I’m temporarily parked on the @repeaterjs github org and @repeater/@repeaterjs npm org. Part of me wonders if we should just use @repeaterjs for uniformity for when npm implodes and everyone switches to the github package registry.
2. replace every instance of the name Channel with Repeater in public APIs.

The channel packages are currently hovering around <50 downloads a week, so I’d like to make this change now when no one cares. However, in the interest of a smooth upgrade path, I think we should republish all the published versions under the new name, and increment versions as necessary. So @channel/channel would still be available at 1.0 under @repeaterjs/repeater or whatever, and the version with the actual renamed APIs would be available under 2.0.

from repeater.

Leaving this open until checklist in #28 is complete.

from repeater.