I tested 10 model/harness combinations on the same Three.js task

Post by polyterative » Tue, Sep 08, 2026, 11:07 AM UTC

onion2k wrote: post #14

The 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…

Post by stuaxo » Tue, Sep 08, 2026, 12:00 PM UTC

Post by Axsuul » Tue, Sep 08, 2026, 12:16 PM UTC

sdey11 wrote: post #56

pprotas wrote: post #25

Earlier quoted context omitted.

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.

Post by andai » Tue, Sep 08, 2026, 12:28 PM UTC

polyterative wrote: post #61

onion2k wrote: post #14

The 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…

The fact that these tools are capable of doing anything at all is a miracle to me.

Post by andai » Tue, Sep 08, 2026, 12:32 PM UTC

stuaxo wrote: post #63

We have differing ideas of what a simple prompt contains.