4 ms·
Absolutely terrible naming collision with another Go Unikernel project: https://github.com/solo-io/unik https://github.com/solo-io/unik
by meddlepal 7y ago
Absolutely terrible naming collision with another Go Unikernel project:
https://github.com/solo-io/unik https://github.com/solo-io/unik
- lainga 7y agoAs is the idiomatic Go style
- xyproto 7y agoIt's convention to try to avoid to use the same name as a different project of the same type, though.
- mapgrep 7y agoParent is making a joke, since Go itself was a namespace collision, arguably: https://en.wikipedia.org/wiki/Go!_(programming_language)#Conflict_with_Google https://en.wikipedia.org/wiki/Go!_(programming_language)#Con...
- TACIXAT 7y agoIt is just a naming collision, not sure you need the superlative and adjective to point it out.
- Semaphor 7y agoisotope (the JS layout library) and isotope.js (the JS view library) are arguably a naming collision despite having slightly different names. I feel like two projects having exactly the same name can have a qualifier to their collision added.
- eyberg 7y agoYeh. Unik is more of a unikernel orchestrator, like OPS is, versus the actual kernel itself. For the go implementation it uses gorump which we sponsored and then retired years ago in favor of Nanos our new kernel. The naming "collision" though is so bad it really feels like a case of squatting the seo though. Outside of Nanos, Unik is the very first thing you'll find when searching for go unikernels.