4 ms·
I think that if tcp[1] is in the stdlib, tls probably should be too. Maybe even ssh. I get there was a time when "listen to the network" meant plain text networ
by e12e 6y ago
I think that if tcp[1] is in the stdlib, tls probably should be too. Maybe even ssh. I get there was a time when "listen to the network" meant plain text networking - but today, for a large subset of applications and libraries, not supporting tls is a bug.
[1] https://doc.rust-lang.org/std/net/struct.TcpListener.html https://doc.rust-lang.org/std/net/struct.TcpListener.html
- ChrisSD 6y agoImplementing crypto is much much harder than simply providing abstractions over the OS' TCP/UDP APIs. Far better to let the experts do it.
- e12e 6y agoThat's not really an argument against having it in stdlib, though?
- ChrisSD 6y agoIt's much simpler to develop complex libraries outside of the stdlib. And given Rust's strong stability guarantees, it can't stabilize any APIs until they're finalized anyway. So development of new APIs often happens outside the stdlib and then if a third party library proves itself and can commit to a completely stable API then it might be uplifted into the stdlib, so long as there's a very strong case to do so. I should also add that most applications won't even be using the TCP/UDP primitives directly. They'll likely be using a third party library. Rust's stdlib is intentionally minimal and lacking a lot of higher level features that are practically necessary for many applications.
- baby 6y agoTls is part of Golang’s stdlib