Re:Major standard library changes in Go 1.20
by SergeAx on Tuesday January 17, 2023 @03:21AM
(#34410287)
What's wrong with Python that you want an alternative?
[ Parent
| on HN ]
Re:Major standard library changes in Go 1.20
by vultour on Tuesday January 17, 2023 @04:33AM
(#34410662)
Dynamic typing. Dealing with structured data and (de)serialisation was a major pain. To me Go feels like a stricter python, still having enough freedom to do most things relatively easily, but not having to worry about what's being passed around.
Re:Major standard library changes in Go 1.20
by 7to2 on Tuesday January 17, 2023 @04:50AM
(#34410763)
I desperately miss static typing.
Re:Major standard library changes in Go 1.20
by thiht on Tuesday January 17, 2023 @04:51AM
(#34410770)
Dynamic Typing, Dependency management, Bundling, Speed
Re:Major standard library changes in Go 1.20
by SergeAx on Tuesday January 17, 2023 @05:50AM
(#34411094)
Interesting, three replies and all about strict types. In my own experience moving to Go from PHP downsides was exactly strict typing and (de)serialization. It is a major pain to handle variable JSON schemas, especially in verbose multi-nested objects in Go without falling back to reflections, which is faux pas there.
Re:Major standard library changes in Go 1.20
by doctor_eval on Tuesday January 17, 2023 @06:15AM
(#34411243)
I’m learning a bit of Django and I can’t believe how much ceremony is involved.
Idiomatic Go eschews frameworks and - as a former Java developer - that is something I really like about it.