Major standard library changes in Go 1.20

Re:Major standard library changes in Go 1.20 by maurice2k on Tuesday January 17, 2023 @03:00AM (#34410162)

Go has one of the best stdlib I've come across. It's very well written and documented, the code is extraordinarily clean and easy to understand, even for advanced topics like cryptography (of course you need some fundamental understanding here).

I think it's comparable to Python.

Go's stdlib was one of the reasons I ended up with Go instead of Rust (might have changed; Rust had a lot community content, but not a comprehensive stdlib; last checked 3-4 years ago).

[ Parent | on HN ]

Re:Major standard library changes in Go 1.20 by bogeholm on Tuesday January 17, 2023 @05:50AM (#34411095)

> Rust had a lot community content, but not a comprehensive stdlib; last checked 3-4 years ago

Still the case now (depending on your definition of ‘comprehensive’ of course). It’s an explicit non-goal of Rust to include “everything” (eg. http, crypto, random numbers) in std because of the stability promises - you can’t make breaking changes to std unless you’re fixing a soundness issue AFAIR.

[ Parent | on HN ]

Re:Major standard library changes in Go 1.20 by maurice2k on Tuesday January 17, 2023 @08:21AM (#34412047)

I was evaluating Rust for some cryptography use case and there were only "random" community libs available that lacked support here and there. And I actually had no trust in any of those libs.

A stdlib must not contain everything but a solid cryptography lib is probably a good idea.

[ Parent | on HN ]

Re:Major standard library changes in Go 1.20 by maurice2k on Wednesday January 18, 2023 @01:40AM (#34424026)

Looks like the situation improved a bit: https://cryptography.rs/

I would still like to have a more comprehensive or high level stdlib for Rust that is maintained by a core Rust team.

[ Parent | on HN ]