On Tue, 18 Feb 2025 19:52:44 GMT, Andy Goryachev <ango...@openjdk.org> wrote:
>> Ease of use for JavaFX developers. Easily maintainable code is one of the >> most important aspects, miles ahead of chasing bytes and chasing >> nanoseconds. There's no tangible value in spending any considerable amount >> of time on thinking how to shave 150 bytes off of a window. > > a) we are _constantly_ adding runtime bytes, we have to be aware of the cost > b) I think we should rather focus on the application developers, and they do > not see the complexity behind the API. And moving a rarely used stuff into a > rarely initialized object should not be a problem for any JavaFX developer, > or am I mistaken? Here's the problem: we're also constantly adding code that needs to be written, reviewed, tested, and maintained. We're talking about a small amount of code here in this particular example, but then again, what particular straw broke the camel's back? I think we have to be aware of runtime overhead where it matters most: in hot loops, or where something is instantiated tens of thousands of times. In all other cases, focusing on bytes and nanoseconds can actually be detrimental in the long run. It makes code inherently harder to reason about, and when many such "optimizations" are taken together, we can end up with code that you can't change any more for fear of breaking the myriads of code paths. ------------- PR Review Comment: https://git.openjdk.org/jfx/pull/1605#discussion_r1964634245
