On 14.02.2022 22:13, Dick Balaska wrote:
> It seems to me that Oracle is doing their best to kill Java. One uses
> Java 16 for "security" reasons and one uses Java 8 if one actually wants
> the shit to work. (And Java 11 if you don't know which way to go, so
> then you have neither).
Oh never get me started on Java. If you want a real screwed up part, try
the accessibility layer, known as Java Access Bridge. On Windows up to
today it even has live-lock bugs on such simple functions as button
presses (reason: the call is synchronous and if the menu item or button
press displays a modal file dialog, you are locked out of accessing that
dialog because all communication tunnels through a single thread).
And documentation? Forget it. So for the record, Java isn't for the
disabled, and all existing screen readers use terrible hacks to somehow
work around all this. Honestly, how can this be in 2022? The liability
alone, especially in the US...
Post a reply to this message