Is there a reason why so many of these agent harness are written in node.js?
DeepSeek Harness developer preview
121–130 of 346 posts
Re: DeepSeek Harness developer preview
#122I have read the underlying paper, and found it may be useful, but not that useful. For those who want to know what it achieves: it adds hot-reload and dynamic enable/dispose capabilities to a plugin system, like the one in Pi agents, though they push the boundaries further, to the UI components and so on. For those who want to know what it does: if you have some PLT knowledge, ask your agent to explain the algebra to…
The paper mentions agent harness self improvement as one of the use cases. I don't know what's the advantage vs. iterating over a monolithic harness.
Re: DeepSeek Harness developer preview
#123Earlier quoted context omitted.
New coding harness that seems to have some novel concepts and one of the pretty cool things on their landing page for it here: https://deepseek.com/harness/en/ is the Every Run is Traceable view: "Everything the model sees is recorded in an append-only session log: system prompts, reasoning, tool calls and results, subagent scheduling, and every context injection. In the Trajectory view, you can inspect these records…
I promise this isn't meant to be snarky, but is that not just...logs?
Re: DeepSeek Harness developer preview
#124Re: DeepSeek Harness developer preview
#125Re: DeepSeek Harness developer preview
#126In the age of LLMs, if your new hires are pushing npm slop, with all the cargo culting and security pwn issues it brings, your hiring process has failed you oof
Re: DeepSeek Harness developer preview
#127Re: DeepSeek Harness developer preview
#128Earlier quoted context omitted.
JVM apparently has the disadvantage that nobody under the age of 40 wants to touch it anymore. I admit I haven't worked in it in 20 years, but I do think it's a marvel of engineering and unfairly maligned. It used to be my career but I wanted to be closer to the metal. Having Oracle's tramp-stamp on it may have been the final kiss of death in terms of totally-superficial "coolness" factor.
The JVM has a fixed size heap which for me it is wasteful. IMHO, Microsoft made the correct approach on .NET. For LLMs, I prefer C# and C++ instead of TypeScript, JavaScript or Python as the static + compiled language factor keeps the coding agents on track. Plus, they have a true threading/async implementation.
The actual physical RAM is still entirely available to other applications. It's just made the OS know it might want that many pages. Until there's data in the pages, they will not count towards total RSS.
It's the kind of things some sysadmins used to gripe to me about and I would question whether they should be in charge of a machine at all.
To repeat: just because an application mmaps a large region doesn't mean the OS has actually given it all that physical RAM. It's merely made sure the pagetable knows about it.
Re: DeepSeek Harness developer preview
#129Earlier quoted context omitted.
[flagged]
You don’t think it’s because titanic battles are interesting and here’s a company that (a) gives you the weights to a frontier model for free, (b) publishes great papers with LLM architecture innovations, (c) is insanely cheap?