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

Design question #19

Open
inancgumus opened this issue May 26, 2017 · 0 comments
Open

Design question #19

inancgumus opened this issue May 26, 2017 · 0 comments

Comments

@inancgumus
Copy link

inancgumus commented May 26, 2017

Hi Michael,

I started learning Go 1 week before (I'm switching from node.js after 5 years). I noticed that you're not using channels much and leaving the channel work to your api user. You designed your library not around channels but only for output. I found this interesting.

And, I still look for callbacks everwhere due to my node.js background, what would happen if you just used callbacks instead of channels? What channels provide you more here? And why you let pass the channels to the clients side, and you even didn't create them yourself (you let the client do the channel management etc & because the chan owner manages the chans?).

Also, is there any resources I might be following for proper Go code design. I'm trying to read opensource project codes mostly to learn more about it.

Thanks!

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

No branches or pull requests

1 participant