Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Go 1.27

go.dev

Post reply on HN
Print view View original

121–130 of 277 posts

Re: Go 1.27

#121

Post by Xeoncross »

greg9381 wrote: post #107
Xeoncross wrote: post #83

Earlier quoted context omitted.

I wrote a blog on it if you're interested: https://xeoncross.com/2026/better_go_handlers.html

Thanks for the link, looks like a very pleasant framework to use! I was interested to see "Mid-fasthttp" on the slower end in the benchmarks at the bottom, do you know why that is? Btw, the Gin and Echo examples reference an "input" variable but it doesn't seem to be defined there? Maybe it was intentional, since the examples are just to give a general idea of how the handler looks in each library, but thought I woul…

Due to the fact that fasthttp is not net/http compatible it is due to the conversion being required from a https://pkg.go.dev/net/http#Handler. It was included for information purposes as I though someone would be curious.

Re: Go 1.27

#122

Post by win311fwg »

AdieuToLogic wrote: post #118
evantbyrne wrote: post #109

Generic methods are a huge win for the language. I've been waiting on these kinds of improvements to the type system before resuming work on my database toolkit.

> Generic methods are a huge win for the language. I've been waiting on these kinds of improvements to the type system ... It's funny that you and many others have found the introduction of "generics" in Go to be highly valuable, considering one of the motivations for Go's existence was: Its designers were primarily motivated by their shared dislike of C++[0] One of the language features C++ provides, "templates", wa…

Generics were always planned, of course: https://www.youtube.com/watch?v=rKnDgT73v8s&t=3267s

Rejecting templates does not mean rejecting generics.

Re: Go 1.27

#123

Post by drivebyhooting »

tyho wrote: post #33

The SIMD stuff is incredible. I have been having lots of fun with it. You can use LLMs as a scalar to SIMD transpiler, it works amazingly well. Sure a SIMD expert writing assembly can probably do a better job than an LLM using these new intrinsics, but it’s still massively faster.

“Do a breakthrough and make this SIMD fastest”

Re: Go 1.27

#124

Post by freakynit »

As I've always said: every non-functional programming language, as it matures, it's adoption rises in enterprise, eventually starts to become more and more like Java in terms of it's syntax and feature-set.

Re: Go 1.27

#125

Post by tugback »

Generic methods finally landing is huge. Having to write a separate typed method for every integer type was one of the most annoying boilerplate patterns in Go.

Re: Go 1.27

#126

Post by whateveracct »

coder543 wrote: post #97
semiquaver wrote: post #94

Earlier quoted context omitted.

Doesn’t the type name uuid.UUID violate go’s style guide for type naming? I seem to recall a fairly specific prohibition on stutter-types.

No. What else could it reasonably be named? Hard to imagine. The rule has always been intended to cover types that have another word in them but still choose to pointlessly repeat the package name. `uuid.UUIDGenerator` is a hypothetical example of the anti-pattern that would instead be better named as `uuid.Generator`.

> No. What else could it reasonably be named? Hard to imagine.

Ocaml often just has it be T

so uuid.T

Re: Go 1.27

#127

Post by whateveracct »

whack wrote: post #120
tester457 wrote: post #61

Earlier quoted context omitted.

> Syntax highlighting is juvenile. When I was a child, I was taught arithmetic using colored rods ( http://en.wikipedia.org/wiki/Cuisenaire_rods ). I grew up and today I use monochromatic numerals. https://groups.google.com/g/golang-nuts/c/hJHCAaiL0so/m/kG3B...

Wow, that thread is a piece of work > Gofmt was written to reduce the number of pointless discussions about code formatting. It succeeded admirably. I'm sad to say it had no effect whatsoever on the number of pointless discussions about syntax highlighting, or as I prefer to call it, spitzensparken blinkelichtzen. > When I was a child, I used to speak like a child, think like a child, reason like a child; when I beca…

he is insufferable. it's his thing lol.

Re: Go 1.27

#129

Post by tomjakubowski »

coder543 wrote: post #97
semiquaver wrote: post #94

Earlier quoted context omitted.

Doesn’t the type name uuid.UUID violate go’s style guide for type naming? I seem to recall a fairly specific prohibition on stutter-types.

No. What else could it reasonably be named? Hard to imagine. The rule has always been intended to cover types that have another word in them but still choose to pointlessly repeat the package name. `uuid.UUIDGenerator` is a hypothetical example of the anti-pattern that would instead be better named as `uuid.Generator`.

uuid.Entifier

Re: Go 1.27

#130

Post by Joel_Mckay »

stryan wrote: post #108
blandflakes wrote: post #106

Earlier quoted context omitted.

bold-faced lie is just the usual English drift that was actually questioned as incorrect when it first surfaced. If a lie is bold, you don't have to suggest that the user's face is bold when doing it. You can in thirty seconds of google searching find numerous sources explaining that "bold-faced" is a malapropism.

It's the usual English drift perhaps, but "bold faced lie" has been used since the 17th century, which is also apparent from "thirty seconds of Google searching". Three hundred years is enough usage for me to count it as correct. On a side note, "bold faced" does not mean the persons face is bold, only that it is said boldly, which implies a level of rudeness that "bald-faced" or "bare-faced" does not.

Colloquialisms and slang have unstable meaning over history, location, and cultures.

Generally, something to be avoided by people striving for clearer communication. =3

Post reply on HN