msgpack-go
msgpack-go copied to clipboard
msgpack
Deprecate msgpack-go (in favor of go-msgpack)
As msgpack-go is no longer actively maintained mainly because of the original developer being a way too busy to pay attention (kudos to @methane and all the guys having worked on it), I think it's time to start thinking of deprecating msgpack-go and possibly embracing a great alternative, go-msgpack (please supply any if there are more) as a new, official Go implementation of msgpack.
+1 @moriyoshi , I appreciate all your work so far. @ugorji, I look forward to your further initiatives on go-msgpack.
@ugorji i personally discussed with @frsyuki about moving your go-msgpack implementation under msgpack organization. Because both @methane and @moriyoshi accepted this migration, all i need to say is: please be msgpack committer to have better and improve golang implementation :)
As a separate note, @ugorji's implementation also has some forks. > https://github.com/ugorji/go-msgpack/network
to avoid the fragmentation, it would be better to notice them about this migration.
Hi folks.
Yes, I will be delighted to contribute go-msgpack as a de-facto Go implementation.
I've done some refactoring to the code to make it easier to follow while still keeping the feature set. I'd like to clean it up some more over the next few days, then make an update.
When that is done, would you like me to update the msgpack wiki?
However, if it's alright with you folks, I'd like to leave it under go-msgpack (just like with the node, lua and javascript libraries). I'm hoping that will encourage me to stay on top of it, and improve collaboration.
Side question: Has anyone thought about using github pages to host the site? I just realized the pages feature and it looks pretty cool.
@ugorji i'll coordinate the process including github pages. could you give me your mail address? mine is [email protected]
However, if it's alright with you folks, I'd like to leave it under go-msgpack (just like with the node, lua and javascript libraries). I'm hoping that will encourage me to stay on top of it, and improve collaboration.
Sorry, what do you mean? You want to have respository name as go-msgpack, instead of msgpack-go...?
Hi @kzk,
I meant that I would like to keep it at the current location, as opposed to moving it under the msgpack, as opposed to moving it under the msgpack user in github.
Got your email. I'd send you one now so you'd have mine.
The README.md for go-msgpack says:
DEPRECATED as of May 29, 2013. Please use github.com/ugorji/go/codec which is significantly faster, cleaner, more correct and more complete. See [https://github.com/ugorji/go/tree/master/codec#readme]
Perhaps the README for this project should be updated as well?
