As an exercise, just try to develop your own code to support https fully and correctly - including common add-ons as Digest and OAuth security - you must depend upon a library to do that.
OAuth isn't an HTTP extension, it's an OSI application level protocol. Also, of all the protocols you could have picked, OAuth is a really simple one. You could code a custom implementation in an afternoon. HTTP isn't even so bad, even with the HTTP/2 modifications, you could definitely do it yourself, depending on your reading comprehension ability (reading code standards is not a skill every programmer has).
The built-in functions for Javascript (and their typical runtime environment - the browser) are minimal leading to a lot of dependence upon 3rd-party libraries.
Ever since most of JQuery functionality got added to the Javascript standard library, you mostly don't need third party libraries. Something like React can be useful if you are working on a web app with a large team because it gives you encapsulation, but even then, the number of third party library dependencies is small enough that a security team can review them all, which some companies do.
I don't know of a better language than Rust for the specific case it's designed for: performance critical code.
That's because you don't know how to use a search engine and look at benchmarks.
https://benchmarksgame-team.pa...
Seriously, think before you post.
The problem with your comment is that the most destructive exploits were introduced by well trained programmers who knew what they're doing.
Which exploits are you talking about here?
What I'm saying is, you're a liar.
The real solution is to have programming tools that can allow average programmer to produce safe compiled code.
That is not Utopian, according to you?
I think there's a world market for about five computers. -- attr. Thomas J. Watson (Chairman of the Board, IBM), 1943