nananana9

Is this only about when you explicitly click on a thumbs up/down button and provide a message, or is it also for the nagware "How is claude doing today [1] bad [2] fine [3] good" that shows up after 15 minutes of work in the CLI and and requires literally pressing 1 key while in the prompt input field to "send feedback"?

I always press 3 to just get it out of the way (although I treat anything I send OAI/Anthropic as training data, so I don't really care) but if this little popup counts, I wouldn't be surprised if the vast majority of CC sessions out there are now "feedback training data"

What this toy shows you is that both points in your original comment are moot.

  1. "fucking over my battery consumption and asking for my GPU to spin" - it renders frames on demand
  2. "2D sucks to make, 2D eats half of your frame time by just existing and slicing those triangles" - frametime is in the microseconds when a frame does need to be rendered, and no triangles need to be sliced because shaders exist.

Let me remind you of what we were arguing about - whether or not you can render UI with a GPU API, without blowing up your computer. I would love to hear how handling taps, adding a mobile-friendly layout to the demo, handling selection or accessibility would change the calculus on that.

In the midst of your ad hominem, your argument seems to have changed from "don't use a GPU API" to "making a production grade UI library is hard", which I'm more than happy to give you.

You don't need most of this. Give me 30 minutes, it will be easier to just build it than describe it.

If your program does 1/1000 of the GPU work Overwatch does every frame, it will cost in the order of magnitude of 1/1000 of what Overwatch costs to render (some fixed costs aside) -- taking aside the fact that you also don't need to re-render the entire window every vblank.

What?

You can try rendering a 2D rectangle as 2 quads in whatever GPU API you like the most, then try pushing the same amount of pixels to a CPU buffer via the widest CPU memory write instructions you can have (and then wait the GPU-accelerated compositor upload them to the GPU anyways to present them...).

I can tell you for a fact one will be 2 orders of magnitude faster, want to make bet which one?

Using a GPU api does not imply you have to render at the screen's refresh rate, or even that you have to update the entire window.

Why is that a talking point now, all of a sudden?

From my POV it looks like you guys tried "They're distilling us! Very immoral!", saw that and nobody cares, and now you're trying to run the more emotionally impactful "They're distilling us... with your grandma's stolen credit card! They're stealing from your grandma!!"

I read it more as "don't implement JS, 3D object rendering, slideshow transitions, sound annotations and the other 999 insane features that I'm not even aware exist"

I would be worried if even they don't have access to the patch.

PHP don't support it and likely won't patch it (even though this is probably big enough that they should), it's up to your distribution whether or not they will.