I've been doing c++ for 20 years, each time I touch boost::beast trying to do basic http/websocket stuff I absolutely hate. It's garbage. Absolute shit.

I wrote a working websocket from scratch in python using just native sockets. You can implement websocket protocol fairly easy yourself. Can put it on a gist somewhere or maybe you can vibe it.

I wrote a working websocket from scratch in python using just native sockets. You can implement websocket protocol fairly easy yourself. Can put it on a gist somewhere or maybe you can vibe it.

Agree on boost btw, wtf indeed.

Agree on boost btw, wtf indeed.

Winsock are way nicer than that boost beast shite.

@whimsical I've also done websocket impl from scratch in c++. It was easier than to use boost::beast. WebSocks in nodejs is a no brainer, while boost::beast is nonsense. Perf wise boost::beast is very fast

I have my own impl of websocks (that uses libcurl under the hood) and I simply wanted to run some tests against beast::boost to check perf measurements. It's incredibly painful to do ANYTHING with beast::boost.

I want to compare raw perf of libcurl vs beast. Things like mem allocations per message, timings etc. I run a local ping-pong test to compare (client sends "ping#0", server replies "pong#0". On the reply client sends "ping#1" and so on thousands of times). With first boost::beast sample code that I got working it's extremely fast. But it's still unusable pile of shit.

Mine did not do the ping pong 😁