Remix.run Logo
▲ jackb4040 2 hours ago

As someone who is actually trying to improve Three.js, this is almost pure slop and you may as well have just posted the prompt you used to generate it instead.

▲bhouston 2 hours ago | parent | next [-]

> As someone who is actually trying to improve Three.js

Hmm... Since spring, I have contributed Gaussian splats, uv unwrapping, and the light baker and much of material x support as well as ~70 other PRs. I am the fifth largest contributor by commits to threejs. I have contributed since 2012.

▲dwaltrip 2 hours ago | parent | next [-]

That is very impressive and quite commendable. However, it doesn't really address the comment you are replying to.

▲bhouston 34 minutes ago | parent [-]

I replied to his claim I wasn't improving ThreeJS. But you mean this part:

> this is almost pure slop and you may as well have just posted the prompt you used to generate it instead

The blog posts references dozens of PRs that I have made, many of which are accepted. It isn't just a random plan created by a single prompt but over 400 hrs of focused work. It was distilled by AI true, but it is a large project that is hard to keep track otherwise for one person. I have to jump from the high level plan down to specific implementation details, profiling, and memory usage while maintain backwards compatibility in each of these PRs to get them accepted.

▲sansseriff 2 hours ago | parent | prev [-]

Impressive!

▲sansseriff 2 hours ago | parent | prev [-]

Are the goals in the post even in line with how three.js wants to improve in the future? Its a web rendering engine after all. I love it, but trying to achieve AAA graphics in a javascript ecosystem seems a little odd to me

▲bhouston 38 minutes ago | parent | next [-]

> trying to achieve AAA graphics in a javascript ecosystem seems a little odd to me

It is quite possible in the way I outline in the post. I have everything prototyped and working, it is mostly just about getting it into ThreeJS in an incremental way that also respects maintainers wishes. It really isn't that much code, mostly reworking what ThreeJS has and replacing the parts that are problematic.

▲simonw 2 hours ago | parent | prev [-]

Now that we know it's getting towards possible (see recent demos like https://x.com/felixrieseberg/status/2119925633564463609 and https://gta.mehranjalali.com), why not go after that?

▲starkparker an hour ago | parent [-]

everything that strays from the "easy-to-use, lightweight" headline goals of the project feels like it should go into a project actually pursuing AAA features

if that changes, the biggest blockers to AAA use of three.js, for agents and humans alike, are the documentation and test holes for best practices and footguns in its existing features

there are outstanding requests for just examples, documentation, and/or test coverage of SSR, GI, reflection, Gaussian splats, virtual textures, multi-canvas rendering, lighting, even TSL (happy 2nd birthday, #29829)

it'd be a lot easier to stomach scope-creeping three.js out of its founding principles if that process included bringing support for already implemented table-stakes AAA features up to AAA level. and whatever benefits vibe-coding, or even measured use of AI to improve PRs, can bring to the codebase, they aren't going to be as effective in improving the already strained support and docs for those advanced features

▲bhouston 40 minutes ago | parent [-]

> there are outstanding requests for just examples, documentation, and/or test coverage of SSR, GI, reflection,

I am redoing SSR in fashion - my full analysis has identified that it is pretty broken:

https://ben3d.ca/series/fixing-threejs-ssr

To be clear this AAA quest project is to fix GI, SSR and integrate it with reflection and diffuse probes along with light baking - that is what I am doing. It is a large task but I've made a lot of progress already and nearly every feature is prototyped and working.