Is there a reason why so many of these agent harness are written in node.js?
1. it's built for async 2. runs everywhere 3. interpreted, making it fast to iterate on 4. decent performance 5. most popular language, llms are decent at writing it
DeepSeek Harness developer preview
21–30 of 346 posts
Re: DeepSeek Harness developer preview
#22[flagged]
Sadly no backwards direction
Re: DeepSeek Harness developer preview
#23Is there a reason why so many of these agent harness are written in node.js?
Any reason why it should not be written in nodejs?
Re: DeepSeek Harness developer preview
#24Is there a reason why so many of these agent harness are written in node.js?
There’s an interesting counter example for DeepSeek called CodeWhale, though:
Re: DeepSeek Harness developer preview
#25I'm curious what peolle are finding with first party vs 3red party harnesses for coding. Do the first party harnesses really have an advantage when paired with the maker's model?
I also just do a bit of hand-coding to guide the agent still.
I worry the $200 / month plans are loss-leaders encouraging you to maximize token usage to churn out slop, rather than thoughtfully use coding agents in a way that still engages your brain, and produces good software.
Re: DeepSeek Harness developer preview
#26Re: DeepSeek Harness developer preview
#27Is there a reason why so many of these agent harness are written in node.js?
I'm not sure why specifically Javascript instead of something like Python or other options, but using an interpreted environment minimizes the friction for implementing extension systems, which are an important feature in AI harnesses.
Re: DeepSeek Harness developer preview
#28But like, what is it? Odd that this reached #1 on HN. The README is pretty bare outside of installation instructions and a link to "Cordis", which is "A Meta-Framework of Spatiotemporal Composability." and "under active development. The API is not yet stable and may change without notice.".
Re: DeepSeek Harness developer preview
#29Earlier quoted context omitted.
1. it's built for async 2. runs everywhere 3. interpreted, making it fast to iterate on 4. decent performance 5. most popular language, llms are decent at writing it
aren't 3 and 4 a tradeoff though? Yes you have 3 but "decent performance" cannot be an extaled value as compared to "runs everywhere". If its used as a counter balance to 3 then it shouldn't be its own unique point basically saying 4 is true despite 3 in this case.
Re: DeepSeek Harness developer preview
#30But like, what is it? Odd that this reached #1 on HN. The README is pretty bare outside of installation instructions and a link to "Cordis", which is "A Meta-Framework of Spatiotemporal Composability." and "under active development. The API is not yet stable and may change without notice.".
A "harness" is basically what you call Claude Code and such, i.e. a TUI to run the agent.