FWIW I've been experimenting with Three.js and AI for the last ~3 years, and noticed a significant improvement in 5.4 - the biggest single generation leap for Three.js specifically. It was most evident in shaders (GLSL), but also apparent in structuring of Three.js scenes across multiple pages/components.

It still struggles to create shaders from scratch, but is now pretty adequate at editing existing shaders.

In 5.2 and below, GPT really struggled with "one canvas, multiple page" experiences, where a single background canvas is kept rendered over routes. In 5.4, it still takes a bit of hand-holding and frequent refactor/optimisation prompts, but is a lot more capable.

Excited to test 5.5 and see how it is in practice.

▲

CSMastermind 7 hours ago | parent | next [-]

> It still struggles to create shaders from scratch

Oh just like a real developer

	▲	accrual 6 hours ago \| parent [-]
		Much respect for shader developers, it's a different way of thinking/programming

▲

Pym 4 hours ago | parent | prev | next [-]

One struggle I'm having (with Claude) is that most of what it knows about Three.js is outdated. I haven't used GPT in a while, is the grass greener?

Have you tried any skills like cloudai-x/threejs-skills that help with that? Or built your own?

▲

import 4 hours ago | parent | prev [-]

Using Claude for the same context and it’s doing really well with the glsl. since like last September