Nitro will undergo a complete rewrite (no longer stable)

[asim]

After having moved all Go Micro interfaces into micro/micro/service. I have realised, that was the end of life for Go Micro. That is effectively a complete merge and deletion of old code and the only reason Go Micro still existed was because of the github stars and popularity.

Nitro is however going in a totally different direction, and the interfaces no longer make sense. For that reason, Nitro will undergo a ground up rewrite. Meaning, Nitro is no longer stable. I'm going to shred this repo down to nothing, and start again. Why not do it elsewhere? Personal choice. I see this as the continuation of a journey. Many products and services undergo ground up rewrites in their lifetimes, brand changes, etc and I think this is no different. The world isn't what it was 6 years ago and Micro itself now solves the problem I set out to conquery in the microservices world but Nitro, to me, is something embeddable, small, lightweight, for dapps, IoT, edge, p2p, wasm, etc. A thing that can 10x what Go Micro was but I think interfaces are the wrong approach for this perhaps, or maybe the naming or the structure. I will start from scratch because thats the only way to make this work.

I do not expect this to be received well, but it will happen.