Well, we'll soon have it all in C++ 🤔

Reply to this note

Please Login to reply.

Discussion

you see, that's gonna be a problem

Go was literally invented to replace C++ for servers, by people of which two of them are the most legendary names in Unix history

Anyone who knows C++ doesn't see that as a problem.

have fun doing coroutines without clumsy syntax then

or atomic queues, fun fun fun

C++ has the throughput advantage but Go can reduce request latency

which is more priority in the domain of servers?

This is for the client-midware, tho.

in the real world of the internet, latency is everything

throughput is for training your AI

"training your AI"

Don't threaten me with a good time, bro.

😁 Okay, gotta go. Getting carsick and Hubby needs to grab a coffee.

I'm aware.. use case.. Network effects would be felt better with go because of those choices made by other teams. for relays I see a lot of people get very upset when it's not go or rust specifically. I'm not religious when it comes to language and it's not a good idea to get stuck into one or two.

We're using Typescript, PHP, Python, Go, SQL, Rust, and C/C++.

Super glad to see! Kudos! 💯

Seriously.

Well, there's just so many of us. 😂

The PO whines that it's too many languages and that adds technical debt, but we pretend to be deaf.

We're not programming a server in C++ though.

not only that, there's no need to because i've already got a pretty much mature relay server already built that is easy to extend, and it probably beats strfry already for latency of responses