JyB

Have you considered submitting an upstream patch to the widely used actions/setup-go as well?

You can blame the media and journalists with sensationalist headlines

Life is not intelligence.

Why would weights need to be « loaded again » for the 2nd pass? Weights never change at inference time no?

One can hope that the Go maintainers won't keep caving as they did for generics.

Pretty childish. People have no trouble looking past it when they care about actually shipping reliable software that properly handles all code paths. Including error paths that are ignored in so many codebases.

No. You're down a very bad path if you 're seeking that.

That comment is a good reminder that a good chunk of people commenting on HN are completely out of touch with the real world, the actual popular ecosystems out there, and what companies actually do and use nowadays to ship.

No thanks. Reduced feature-set is the appeal.

You are unfortunately right. I am a bit relieved because it seem generics don't seem that over-used in the community. But still, the language lost a lot with this change that felt super-forced and unnecessary. Biggest downside of the language by far.

That's funny because that's factually untrue. Go's early popularity and professional adoption were largely driven by its perceived productivity boost linked in part to the small surface area of its spec, long before this subpar generic implementation was forced into it.

That's actually very popular with pretty much anyone who's dealt with errors happening in programs... which I would assume is most devs after some time.

Right. On a related note: "MCP is invisible to the LLM, or should be, under normal use". I am not convinced there are any downsides for the harness to explicitly feed MCP keywords into the LLM. It seem explicitly doing it has many advantages. For example, it allows the user to ask to interact with a resource through "the configured MCP" rather than directly through some local cli or HTTP endpoints; which can steer the LLM towards the proper actions. Otherwise, the model could in-theory be "clueless" with such a request.

Not sure I understand what you mean. MCP servers and methods available do have to be visible to the model in some way so that it can spit out tool calls instructions to be executed by the orchestration layer around it. But you probably meant something else?

While that is true, the overarching point is that it fundamentally still is, just a story. You're just describing real world consequences, precisely because humans/societies believe in that story and enforce it.