Why is almost everything in the API final
Stefan Fuchs
snfuchs at gmx.de
Tue Sep 3 11:06:50 PDT 2013
Mario Torre wrote:
> In this case, since JavaFX is Free Software! you can actually suggest
> the fix, prototype and propose the patch yourself, limiting the round
> trip time substantially.
>
> This also increases the chances to get a better fix in the end, since
> more eyes are focusing on it.
>
> Cheers,
> Mario
>
>
>
...and then wait a year or longer until the fix is delivered with the
next major java release.
Sorry, this is not really a viable option. Besides we still use
webstart, so forking the jdk is not an option either.
Wouldn't it be better to allow developers to override methods at their
own risk.
So, instead of making methods final, add a special annotation like
@DoNotOverride to methods, which are not intended to be overridden by
the designer of the framework.
The compiler can emit warnings, if the developer decides to override the
method anyway.
This would clearly indicate to the developer, that his change is
dangerous and he can not count on support from oracle, if his
application breaks.
Yet, those that are willing to take the risks, can do something to keep
their business alive.
Stefan
More information about the openjfx-dev
mailing list