JyB

9 ms·

1.
by JyB 7d ago
Life is not intelligence.
2.
by JyB 7d ago
Why would weights need to be « loaded again » for the 2nd pass? Weights never change at inference time no?
3.
by JyB 27d ago
One can hope that the Go maintainers won't keep caving as they did for generics.
4.
by JyB 27d ago
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.
5.
by JyB 27d ago
No. You're down a very bad path if you 're seeking that.
6.
by JyB 27d ago
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.
7.
by JyB 27d ago
No thanks. Reduced feature-set is the appeal.
8.
by JyB 1mo ago
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 l
9.
by JyB 1mo ago
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 subp
10.
by JyB 1mo ago
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.
11.
by JyB 1mo ago
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
12.
by JyB 1mo ago
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 me
13.
by JyB 3mo ago
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.
14.
by JyB 5mo ago
What credentials related to software engineering? Please expand and do not post nebulous comments like these.
15.
by JyB 5mo ago
Courage is not the appropriate word
16.
by JyB 5mo ago
This specifically is super annoying.
17.
by JyB 5mo ago
Restrictions don’t have to be confusing, they can be clear. You are missing the whole point.
18.
by JyB 6mo ago
> modern MCP clients do smart tool search that obviates the entire "I am sending the full list of tools back and forth" mode of operation This has always surprised me as this always comes up in MCP discussions. To me, it just
19.
by JyB 7mo ago
I don’t know if you’re being serious but that’s laughable
20.
by JyB 10mo ago
How is that specific to antigravity? Seem like it could happen with a bunch of tools
21.
by JyB 10mo ago
That’s exactly what it is in essence. The MCP protocol simply doesn’t have any mechanism specifications (yet) for not loading tools completely in the context. There’s nothing really strange about it. It’s just a protocol update issue.
22.
by JyB 10mo ago
The MCP standard will and has to evolve to address this context issue. It’s a no brainer and this is a perfect example of the direction mcp is going / will go. There’s fundamentally nothing wrong, it’s just protocols updates that have
23.
by JyB 10mo ago
In also interested in n8n. From what I gathered it’s a everything baked in app, not a lib. Meaning that unless you re doing upstream contributions you don’t actually code anything. Just manage big configs. How are you planning to use this t
24.
by JyB 10mo ago
Concurrency. Unless you’re happy stopping the world on llm io… Go excels at handling network calls and the like. It’s basically what agents are.
25.
by JyB 11mo ago
I think you are right.
26.
by JyB 11mo ago
Claude Skills just seem to be the same as MCP prompts: https://modelcontextprotocol.io/specification/2025-06-18/ser... I don't really see why they had to create a different concept. Maybe makes sense "ma
27.
by JyB 11mo ago
I'm super confused as well. This seems like exactly that, just some default prompt injections to chose from. I guess I kinda understand them in the context of their claude chat UI product. By I don't understand why it's a th
28.
by JyB 1y ago
I never understand why there's always one of the top comment on every Go post being derogatory and mentioning Rust. It never fails. It starts to feel like a weird mix of defensiveness and superiority complex.
29.
by JyB 1y ago
No one think any form of "prompt engineering" "guardrails" are serious security measures right?
30.
by JyB 1y ago
Assuming you're using GitHub or similar, make pushing branches and creating PRs part of their prompts, and review on the GitHub app or equivalent? Seem like an orthogonal problem to those LLMs tools.

More ›