Backwards compatibility issue?

Richard Bair richard.bair at
Fri May 31 11:31:33 PDT 2013

Sorry Tom! Made public (not scheduled until after 8).


On May 31, 2013, at 11:05 AM, Tom Schindl <tom.schindl at> wrote:

> the JIRA mentioned is not public - we the e(fx)clipse project are working on such a feature as well for one of our next releases - so if openjfx does provide it we could spend our time on other important improvements!
> Tom
> On 31.05.13 19:54, Richard Bair wrote:
>>>>> What's so horrid about css to bss compiling?
>>>> A) It's broken
>>>> B) What's the point?
>>>> Not trying to be unduly critical but is it for some performance gain or something? Surely the load time is minimal. Given that I have a dozen XML config files, a handful of property files and a thousand FXML files that are being loaded by my app it seems like a whole lot of extra complexity and space for bugs to crawl in for no gain. Maybe I'm missing some benefit of this?
>>> The benefit is performance. It is much faster to deserialize the binary format than to invoke the parser.
>> And we're talking orders of magnitude here. And don't forget about iOS / Android / PI / Beagle / and friends. We didn't do bss because we thought it was cool, I can promise you that. Neither are we looking at compiling FXML into class files (RT-23527) for the fun of it ;-).

More information about the openjfx-dev mailing list