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

Programs vs. Libraries #6

Open
jbuberel opened this issue Jul 5, 2015 · 0 comments
Open

Programs vs. Libraries #6

jbuberel opened this issue Jul 5, 2015 · 0 comments

Comments

@jbuberel
Copy link
Collaborator

jbuberel commented Jul 5, 2015

Another topic I'd like your opinion on...

With the new experimental vendor folder support coming in 1.5, and the rapid adoption of Dave Cheney's gb project, I've been thinking about how to make the Go newcomer experience better.

For example, if you are developing a program in Go, I'd argue that you should:

  • Make binary builds available on Mac, Linux, Win
  • Use semantic versioning to label those releases
  • Not ask users to download and install Go in order to build your program source
  • Not have to care about whether your program can be installed via go get

However, if you are creating a library in Go, then you really should:

  • Make sure that your library is go get-able
  • Your project should be listed/registered in godoc.org
  • Your top-level readme should include information about API stability, etc.

Do you think this distinction is important? If so, how best to communicate that to the developer and user communities?

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