Review Go guide #891
Merged
Review Go guide #891
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We've already removed Go from the list of core backend languages, in #876. |
|
Yeah, I've seen that :) Now to deprecate this section :D |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The contents are still valid in my belief.
I would like us to consider and look at deprecating this section as a whole possibly next year. I could have suggested it now, however I believe there is still a lot of potential for Go in GDS - especially in the GOV.UK's K8s setup. Not to mention the GDS CLI and remains of PaaS.
I imagine GOV.UK may want to have some custom operators being written and maintained in Go, which may mean deprecating this guide isn't necessarily the right call. But perhaps, the direction the team is going at will constraint the use of Go to simply running an Open Source projects.