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
Subs or Substitutions? #53
Comments
Good point. What do you folks think? @danigb @itrelease @maraisr @tzellman @evgenykochetkov @terkelg I'm 💯 with the idea. |
I think it's a good idea considering that it's inspired by |
I was thinking the same thing. |
I like |
I agree, good idea! |
subs is an array, so its description should be a noun, not a verb. subscribes would indicate a function. |
@rbiggs Changed to subscriptions. Code still handles and will handle .subs for a while, at least after >=0.0.13, examples have been updated and due mourn time has been given. |
@rbiggs Can this be closed? @jbucaran Is there anything else to do before releasing |
Shipped. See the release notes. |
I really like the API, a complete copy of ElmArchitecture in JavaScript. My only peeve is
subs
. I think it would be better to use the termsubscriptions
like Elm and Choo. I remember the first time I looked at the counter example and saw the sub function in the update method. I immediately assumed it was a singular instance of subs, whatever they were. Then when I saw the subs in actions I was thinking, hmmm... substitutions?, subtractions? subordinations? subscripts? or maybe he wants to give us all foot long subs!!! Yay! I'll have two please. OK, I know you usedsubs
to save a few letters typing, but going forward if you want this project to gain traction it would be better to use the more explicit termsubscriptions
to save people the mental work of constantly translating subs to subscriptions in our heads. Even in yourREADME
you describesubs
as: Subscriptions are functions that run once when the DOM is ready. Use a subscription to register global events, like mouse or keyboard listeners. I'm suspecting you probably just lobbed off the tail end of pubsub for the term. My point is explicit terms are always better than implicit terms in API design. It's not like people would have to type the term a thousand times. It's just once. Then when you scan the page and seesubscriptions
it would be immediately clear what you are looking at, even if you were not familiar with this API.The text was updated successfully, but these errors were encountered: