Am I missing something or does sorting by Duration not work? Chrome on Android mobile
I tested 10 model/harness combinations on the same Three.js task
51–60 of 84 posts
Re: I tested 10 model/harness combinations on the same Three.js task
#52[flagged]
Re: I tested 10 model/harness combinations on the same Three.js task
#53Damn its unreal how much Astra is better than anything else :(
Would be cool to see total cost
Re: I tested 10 model/harness combinations on the same Three.js task
#54How do you judge which one produces the best result? They all look the same to me more or less.
Re: I tested 10 model/harness combinations on the same Three.js task
#55Damn its unreal how much Astra is better than anything else :( Would be cool to see total cost
[deleted]
Re: I tested 10 model/harness combinations on the same Three.js task
#56Btw in my quest for a good desktop codex/claude like app - https://github.com/openchamber/openchamber - this seems to be front-runner. I pair it with OMP via https://github.com/alvins82/omp-openchamber-server/ . I wanted a powerful GUI+harness setup for open models so I could use/test as they came out.
I like Paseo https://github.com/getpaseo/paseo But I am annoyed at these GUIs implementing features I don’t care about. I want them to just wrap my harness and forward it to my iPhone, but they can’t help themselves from feature creep.
i liked paseo too but its not optimized at all. let alone the feature bloat.
Re: I tested 10 model/harness combinations on the same Three.js task
#57What is DSH / PTC?
Ptc is programmatic tool calling or code mode
Basically it can run these mini programs where each input might be another toolcall, so it can run without waiting for whole LLM response and ready the parameters async.
Re: I tested 10 model/harness combinations on the same Three.js task
#58I love everything about OpenCode except for the stuff it outputs. On paper it has everything I want in a harness and more, but it tends to struggle to deliver the desired outcome. Last I used it the context was massive and tool calls were reliably unreliable. Is it worth revisiting as a daily driver?
i moved from opencode to omp and i don't think I'm ever going back
Re: I tested 10 model/harness combinations on the same Three.js task
#59Btw in my quest for a good desktop codex/claude like app - https://github.com/openchamber/openchamber - this seems to be front-runner. I pair it with OMP via https://github.com/alvins82/omp-openchamber-server/ . I wanted a powerful GUI+harness setup for open models so I could use/test as they came out.
I created my own in-browser terminal, so it can sit in chrome, accessible, and with some enhancements like animating the tab when the agent is doing some work. It's a layer on top of ttyd/tmux.
Re: I tested 10 model/harness combinations on the same Three.js task
#60The Astra version seems to have used three.js r170, which is from October 2024. Sol used an even earlier version. GLM's code used the latest version, but I think it's just getting three.js@latest from jsdelivr so it's unlikely to be writing code against that version. Qwen on OpenCode also fetches from jsdelivr, but using a pinned version at r160. I don't think any of these examples are using things like tone mapping…
What’s a good way to drive models to use current versions?
[flagged]