RFR: 8313424: JavaFX controls in the title bar [v49]

[Andy Goryachev]

On Tue, 18 Feb 2025 19:43:15 GMT, Michael Strauß <mstrauss at openjdk.org> wrote:

>> ease of use for whom?
>> 
>> bloated code: a few bytes in extra methods
>> bloated data: thousand of bytes added per instance
>> 
>> Since we are adding properties to Window, it's probably ok because the number of instances is relatively low (a real app won't have hundreds of windows).
>> Still, I would like to recommend investigating the alternative: the memory is not an unlimited resource, and in my experience, it's worth thinking about it.
>
> 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?

-------------

PR Review Comment: https://git.openjdk.org/jfx/pull/1605#discussion_r1960496373