Mumble VS CppCoreGuidelines

I think Sonobus is overkill. I suggest you look at a couple of relatively old-school gamer voice chat tools - Mumble or Teamspeak. Mumble is open-source and the connection is always encrypted, Teamspeak is commercial but the free tier should be fine for you - but you have to make sure to manually turn encryption on yourself. It has been a long time since I used either, so I don't know which is easier. Both of them require you to run their matching server software.

Mumble's latency is unbeatable imo, it's basically their main focus and shows.

The sticking point for me is the lack of persistent messages, something the devs strangely think is a privacy plus. Issue open since 2016: https://github.com/mumble-voip/mumble/issues/2560

If you drop out for a minute you won't have access to anything that was posted in chat, which makes it useless for anything other than voice only comms, that might suit some business purposes but I've always needed to post links or screenshots in chat during meetings.

There's any number of alternative chat applications available, like Element, Mumble, Teamspeak etc.

Mumble?

I think Mumble might fit what you're looking for. It's been a very long time since I've used it, but it seems to still exist: https://www.mumble.info/ - I've used previously for exactly what you're describing, events with lots of crew dispersed around and no budget for radios. I had it installed on an AP running OpenWRT so it was just a case of plugging that in and getting people to install the app and connect to it.

Along with the options already mentioned, if you're not into TeamSpeak, there is an open source alternative called Mumble which operates in the same manner. No internet required, and is supported on multiple platforms.

You need to talk to Bjarne and Herb...

"C++ Core Guidelines" - https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines

In addition to the other comments -

TypeScript deliberately takes a "good enough" approach to improving JavaScript, instead of designing an ideal but incompatible approach. For example, its handling of [function parameter bivariance](https://www.typescriptlang.org/docs/handbook/type-compatibil...) is unsound but works much better with the existing JavaScript ecosystem. By contrast, a more academic functional programming language would guarantee a sound type system but would be a huge shift from JavaScript.

By analogy, Herb Sutter is arguing that something like the [C++ Core Guidelines](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines), with tooling help in this new Cpp2 syntax, can bring real improvements to safety. Something like Rust's borrow checker would bring much stricter guarantees, backed by academic research and careful design, but would be incompatible and a huge adjustment.

https://www.youtube.com/watch?v=2olsGf6JIkU

Take a look at Effective Modern c++ by Scott Meyers and the ISO c++ core guidelines. These resources are great for learning how to write better, more modern C++. I don't think it would be hard to grasp if you're already familiar with the language, just make sure to actually write some code which makes use of this stuff, otherwise it's easy to forget.

Look to the C++ Core Guidelines. It's not perfect, it has some flaws, including some sabotaging advice apparently adopted for political reasons. But at least it has some C++ authorities (Bjarne and Herb) as authors.