Hacker News
My Quest to push native Three.js quality match AAA Game Engines
oooyay
|next
[-]
bhouston
|root
|parent
[-]
augment_me
|next
|previous
[-]
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.
bhouston
|root
|parent
[-]
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.
Oarch
|next
|previous
[-]
I thought I had the slightest idea about Three.js and computer graphics until this post burst that bubble!
sph
|next
|previous
[-]
kkukshtel
|next
|previous
[-]
bhouston
|root
|parent
|next
[-]
mediaman
|root
|parent
[-]
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.
pandemic_region
|root
|parent
|previous
[-]
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.
sansseriff
|root
|parent
[-]
So are compatibility, politics and maintainability the things that differentiate 'slop' from 'not slop' now?
nsainsbury
|next
|previous
[-]
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".
sansseriff
|root
|parent
|next
[-]
Other people think of a blog more like substack or poetry where the whole point is to read what a human wrote.
jackb4040
|previous
[-]
bhouston
|root
|parent
|next
[-]
Hmm... I have contributed Gaussian splats, uv unwrapping, and the light baker and material x support lately as well as 20 other PRs. I am the fifth largest contributor by commits to threejs. I have contributed since 2012.
dwaltrip
|root
|parent
|next
[-]
bhouston
|root
|parent
[-]
> 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
|root
|parent
|previous
[-]
bhouston
|root
|parent
|next
[-]
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.
simonw
|root
|parent
|previous
[-]
starkparker
|root
|parent
[-]
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
|root
|parent
[-]
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.