🚨 VCPKG keeps removing this repo from their registry.

[elzii]

I made the case that this is pretty feature-complete and I use it in a production environment at a Fortune 500 company, but IDK if they just have a very ignorantly coded bot that removes libs from its registry if it doesnt see a release or activity in X period of time, of if there is some bias happening @uilianries since you work on Conan. VCPkg showed great promise but it removing things with no --legacy / --override switch breaks my CI and just feels immature.

1 of 2 issues threads I made on their repo in case any maintainer here wants to weight in: microsoft/vcpkg#50114

Cheers. I guess I'll just switch to Conan if it goes unresolved 🤷‍♀️

[jfayot]

Hi @elzii
I completely understand your frustration with package registry policies. It’s a tricky balance between maintaining a clean ecosystem and ensuring stability for production dependencies.

For what it’s worth, I’ve been working on sioxx, a socket.io-client-cpp alternative built on Boost.Beast and nlohmann-json, with the goal of addressing some of the gaps in the legacy lib.

I’m currently in the process of publishing sioxx to ConanCenter and submitting it to vcpkg to ensure it’s easily accessible for CI/CD pipelines. If you’re open to giving it a try, I’d love to hear your feedback. The API is designed to be familiar to users of socket.io-client-cpp.

That said, I’m not here to push sioxx as a replacement. My goal is simply to provide an alternative for those who need active maintenance, modern features, or better package manager support.

If you have thoughts on what you’d like to see in sioxx, I’d be happy to discuss or collaborate. And if you do end up switching to Conan, I hope sioxx can be a viable option for you down the line.