dakom

You're making a straw-man argument with "anything exposing gender metadata". It's not like I dug up some obscure article - it's literally his chosen brand name. There's nothing arbitrary to use "he" for somebody who calls himself "mr".

Is it possible that you have a good point about inclusive writing in general, but you just happened to hop on the wrong case to make your stand, didn't realize that we're talking about an explicit "mr"?

His brand is literally "Mr Doob"

The consensus in English-writing guides like the APA or Elements of Style is about staying true to a person's self-identified pronoun while preferring specificity over ambiguity. In a case where you don't know - "they" is perfectly acceptable. In a case where "they" is an explicit self-identity - it's the only correct option. In this case, where he literally calls himself "Mr", it's stylistically incorrect to choose a more ambiguous pronoun where "he" is the correct one for someone calling themselves "mr"

How does it deal with latency? Afaict remote LLMs need seconds to process, but Tetris can move much faster..

I agree wholeheartedly. It's like the energy and motivation has to go somewhere, and talking too much is a vacuum.

I love this, simple, fun, and easy-to-read source :)

FYI - there's a security problem with the leaderboard, I added the Testy McTester score of 42 to see if it would go through, feel free to delete it

Yeah, I split the crates so `renderer-core` deals with the web-sys part, `renderer` is pretty much plain Rust (and wgsl with Askama templates)

I prefer this for 100% browser-only, but that's a niche. I do think wgpu makes more sense when you like the WebGPU headspace but want to target other backends (native, mobile, VR, etc.)

Mostly because I want insight and control at a lower level, which breaks down into two different use-cases:

1. Debugging. The nature of bugs in this space is a lot more of "it doesn't look right on the screen" as opposed to "it breaks compilation", so I want to easily do things like peek into my buffers, use native js logging, etc. It's just a lot easier for me to reason about when I have more manual control.

2. Leaky abstractions. wgpu is a pretty low-level but it can't avoid the pain that comes with different backends, async where it should it shouldn't be, features that aren't available everywhere, etc.

That said, it would probably be pretty straightforward to convert the renderer into wgpu, most of the data structures and concepts should map cleanly