Is vendoring a standard approach or is it obsolete? [closed] - go

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I'm about to setup a new project in Go. I came across the term vendoring. Is this standard or an obsolete concept. I'm coming from a nodejs world and this feels like copying the nod_modules folder to a separate directory or am I confusing the whole purpose of this?

It's not technically obsolete, but most cases should use go modules instead.

Related

How to do logging in a go library [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 days ago.
Improve this question
What is the correct way to implement logging in a go library?
For example I want to signal that something gone bad in my library but I also want to user of my library have flexibility in log displaying, filtering and storing logs.

Golang project folder structure - Good Practise [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 days ago.
Improve this question
Does GoLang have any bootstrap CLI command like create-react-app? What is the best project scaffolding structure to follow for newbies like me? Most of the tutorial doesn't give any project structure. They just focus on Golang syntax.
Do we have any good tutorial which covers project setup on Golang?

package convention for java Springboot lightweight controllers? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
We have the controllers already being used with many apis in the package
com.mycomp.myapp.controllers
The controllers developed are heavy, so planning to add light weight apis with minimum request parameters.
confused between these two
com.mycomp.myapp.controllers.lite or com.mycomp.myapp.lite.controllers
Can anyone suggest the package names with conventions?
I think you should go with com.mycomp.myapp.controllers.lite.
Because actually you are creating controllers only and now controllers would be distinguished by light or heavyweight. That's why the distinguishing part should be inside the controller package.
Happy coding :)

Spring application profile name suggestion [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
What is the standard naming convention to create several peer profile.
application-peer1-test.properties or application-peer1_test.properties
Naming of the profiles is up to you.
I think that best practice in this case would be not to mix different approaches and best name would be application-peer1-test.properties

Why does Go support Plan9? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Why does the Go developers spend time supporting Plan9, rather than on making Go better for Unix?
This question is off-topic, but there is some information about the decision to use/learn from Plan 9 in the Go at Google: Language Design in the Service of Software Engineering talk by Rob Pike.

Resources