upvote
My Quest to push native Three.js quality match AAA Game Engines

(ben3d.ca)

This was written by AI as other comments suggest but I still found it pretty informative. I have a side project that I use three.js on where I ended up having to play with lighting and reflection settings, so this write up was relevant enough for me to understand what the AI was talking about. If anyone is interested: https://portland.ooo-yay.com
reply
I use hybrid techniques. I have a swarm of agents and external context where my plans are refined. This series of blog posts is extract from that refined external context. It is generally right as I have refined it over about two months now. Probably a hundreds of prompts and refinements. I am also a 30 year computer graphics veteran and the fifth largest contributor to three.js by commits of all time.
reply
Excited about the idea but then immediately off-put by the slop.

If you intend no-one to use what you built except for LLMs, this is fine. If you intend for humans to read it and if you value your ideas in the context of other humans, you can't drop 15 pages of generated material. You can be a Nobel laureate and I will still feel like the text is a massive waste of time because I can't know if you even read it yourself.

reply
> If you intend no-one to use what you built except for LLMs, this is fine.

This is a plan for moving ThreeJS towards this new pipeline. It isn't intended for everyone, rather it is a detailed and specific implementation plan, intended to be read by fellow computer graphics people, with justifications, that is half way towards being realized. It isn't intended for ThreeJS users to actually use this plan. But this plan does help align and keep track of my work.

reply
Please don't waste my time with slop. If you ain't written it, I ain't reading it.
reply
This would be interesting to read if it wasn't just AI slop. I'm interested in this as an endeavor but if an AI is just writing about it's own progress with some nebulously defined goal, the only thing I care about is "does it work or not".
reply
I am using AI of course but it is a multi month project of which I’ve had over 20 PRs merged in the last two months.
reply
That's great. We'd like to hear what you have to say. Not your thoughts shredded by the woodchipper teeth of an LLM.

Not anti-AI on code, but LLMs are really not good at clear writing, and they are not getting better, so please write your own words if you wish to be heard, even if you feel they are clumsy or if you feel you are "not a good writer."

And even though it may feel like it is a waste of time, or that it can be done quicker with an LLM, the life returns are really high to you to have an audience knowing who you are and how you think about problems, and you're not going to get that with an LLM, so there's no point to writing about it at all if you're not going to be authentic.

reply
> the only thing I care about is "does it work or not".

This matches general AI supported work. We have the result but no idea how we got there and nobody learned anything valuable along the way. Shareholders never cared anyway so that's that done with.

reply
Agreed. But then what do we make of it when a single user moves more rapidly with their fork of a library than the library maintainers. Both are probably using AI, but the maintainer is much more concerned with compatibility, politics and maintainability.

So are compatibility, politics and maintainability the things that differentiate 'slop' from 'not slop' now?

reply
Ben - since you're active in the comments here...what motivated you to fill your blog with Claude/AI slop? You're obviously a talented person who has been active in the space for a long time - don't you want to speak with your own voice? Who is your blog even for at this point? Humans don't want to read that - it's immediately off-putting (and in parts quite non-sensical). So who is this written for? For other Claude instances to use?

I don't understand at all people who are immediately surrendering their entire voice, personality, audience, credibility, etc. to Claude? I mean at this point why not just rename the entire site to "Claude's Blog" and tell it to adopt the persona of a Graphics Developer and "Write a post a day".

reply
If feel like this points to different people having ideas about what a blog is for. Some people will think the written word is downstream of the actual content they want to share (new features in three.js), which for all we know they put a bunch of time into. The blog is like a compile target, even if its describing something the author thinks is meaningful.

Other people think of a blog more like substack or poetry where the whole point is to read what a human wrote.

reply
Some people write because they like to write, some people write as a byproduct of doing cool shit. I can't speak for everyone but it's clear a lot of people posting LLM content are in the latter category.
reply
[dead]
reply
I love it when a post leaves me dumbfounded and awed like this.

I thought I had the slightest idea about Three.js and computer graphics until this post burst that bubble!

reply
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.
reply
> As someone who is actually trying to improve Three.js

Hmm... Since, 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.

reply
That is very impressive and quite commendable. However, it doesn't really address the comment you are replying to.
reply
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.

reply
Impressive!
reply
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
reply
> 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 an replacing the parts that are problematic.

reply
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?
reply
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

reply
> 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.

reply