News for hackers. Stuff that matters.

A comment on Fixing for Loops in Go 1.22. Parent comment

Re:Fixing for Loops in Go 1.22 by kaba0 on Tuesday September 19, 2023 @05:29PM (#37577026)
With all the crazy warts that JS has, it is at least a lisp-like very dynamic language if you squint (a lot) at it. Its greatest fault is probably leaving out integers (I can’t even fathom why they decided on that, floats can’t represent properly ints).

Go is just simply badly designed, relying on hard-coded functionality a lot.

[ Parent | on HN ]
Re:Fixing for Loops in Go 1.22 by Cthulhu_ on Wednesday September 20, 2023 @06:01AM (#37582359)
Which is better, hard-coded functionality or magic? I don't believe it's badly designed, since every design decision is deliberate; bad design would be accidental.
[ Parent | on HN ]
Re:Fixing for Loops in Go 1.22 by za3faran on Thursday September 21, 2023 @01:02PM (#37600560)
This is a false dichotomy. golang is weak that things that should have been in the standard library end up being hardcoded (like maps).
[ Parent | on HN ]