boblivion

Some car manufacturers are employing ultra wide band for precise location. The VW ID.4 for example has this. I'm not aware of successful (relay) attacks against these kind of systems.

Which may be because you simply can't do everything good without practice and in pure math, well, there are things you don't do as much. When I go back to the 3rd and 4th degree polynoms we solved back in school, it's a hassle. Back then I was quite good at solving them but nowadays it just takes time to get accustomed to these kind of problems.

They weren't the maintainers anymore. That's the reason. OSS is tricky sometimes in that regard.

I thought a LLVM-based compiler would have been nice for a while but in reality a lot of the tooling is C or C++ based and the run-times here are fundamentally different. This is why putting Go and C code together is so inconvenient (and slow), the calling conventions / stack setup is very different.

I really favor the C/C++ binary interface for its simplicity but Go is really good for what it is built for.

But yes, compilers are always a good argument. I can understand however why C++ frustrated people. To get this beast to work for you, even after C++11 - it requires a lot from the developer. Today, things are a lot better though and they keep getting better.

Which is funny because the void keyword specifies that the function receives no arguments. Otherwise you could call it with any amount of arguments you want. However, the linker doesn't care about type-signatures, so in the end this main function still gets called with argc, argv, envp.

Nah, my browser tells me it's insecure.

It's not about runtime objects, its about static code that should be closed for modification. Plugin architectures are most representable thing for this I can think of: You don't need to change any code. You just write new code and extend the capability of the existing code. In this case you don't even need to recompile anything. Of course plugin architectures are the extreme.

Wait, why do they call it amplitude when it's the rotational component? What is the reasoning to call this amplitude?

What is it with mercury and relativity?

Also the security of the theoretic primitives behind symmetric encryption rely on the existence of pseudorandom generators / pseudorandom functions ect. which is not proven either. On top of this, AES for example is "only" an apporoximation of what a pseudorandom function really is. In the end these ciphers are secure as long as nobody finds a flaw in them. However, flawed implementations are the main risk.

For starters nlohmann/json is fuzzed (look at the test directory). From my experience it is really stable. jsoncpp still has some quirks as it relies on unit tests only. Big no no for me.

It's on its way though. Better late than never I guess.

Well if she finds having children not to be attractive, that's fine. But I doubt that further decline of birthrates in the West will stop overpopulation.