> it still depends on how its compiled. Most distros have the "core" modules as php extensions. But if you WANT to, you can compile php to include these modules into the lib/exe so you don't have to load the shared libraries.
Of course, you can do.
And in a C program you can statically link the libsodium.a. So what?
> I believe you can compile ANY php extension INTO php so you don't have to load it every time
You won't notice.
> because binding with a static library allows the software to function even if the underlying shared libraries have been updated.
That's a reason. On the other hand, you update your libs and your php stays insecure. No good idea.
> The point here is that once this library is included, distros will have this in by default, and it won't require you to install a compiler and pear/pecl software to get the extension into your php
Yep. But that's still a strange definition of "the first langauge to add modern cryptography" (btw. why the quotes in the title, libsodium IS modern cryptography).