Posted by gouessej on Jan 10, 2015; 12:09pm
URL: https://forum.jogamp.org/road-map-release-builds-tp1853748p4033827.html

Hi

I'm sorry to refresh this very old thread.

I have been recently accused of defamation by a moderator of another forum, he wrote that I "totally 'defamed'" the team working on this set of bindings "like they weren't worthy of the air they breathed". This is how he understands my replies to Cork's comments here.

According to Wikipedia, defamation is

the communication of a false statement that harms the reputation of an individual person, business, product, group, government, religion, or nation

I'm going to prove that there was no intentionally false statement in my posts.

gouessej wrote

Its support of OpenGL ES and OpenCL is younger. OpenGL ES is not really homogeneous with the rest of the API

At first, Michael worked hard on the very first Java binding for the OpenCL API whereas some discussions about supporting OpenCL in the other set of bindings started in 2010 (its first successful OpenCL call was done in September 2010) whereas the initial import of the JOCL prototype was done in July 2009.

Secondly, the second major version (2010) of this library manages OpenGL ES in a completely separate API which was known to be less stable than the ES "part" of JOGL. Maybe Xerxes can confirm as I remember that he tried to build it.

gouessej wrote

its support of Linux and/or lots of "old" graphics cards is not reliable enough for production. LWJGL has 4 releases with tiny changes except OpenCL/OpenGL ES support. I complained several years to get some major bugs fixed in LWJGL. I had only a pretty black screen when using it during several months because its maintainers refused to admit that they had caused a regression on ATI cards, I had to prove I was right, they were saying it was a driver bug.

There were 4 major bugs annoying me:
- a black screen on some machines
- some straight lines drawn on the desktop and in the task bar when leaving an application under GNU Linux with KDE
- some random crashes after 15 minutes of run under Windows with some very old (2001) VIA chipsets
- a bug in a picking example
- a crash or a black screen under GNU Linux when multiple bit depths are supported and/or the refresh rate is unknown

I talked about the first bug here, I investigated for 4 months, it was fixed in the Space Invaders example.

I realized several years later (in 2013 or 2014) that the second bug was reproducible with NEWT (JOGL) when modifying the refresh rate of the main monitor, it wasn't coming from this library but I had no mean to reproduce this bug with JOGL in 2010 because of the API changes occurring later.

The third bug has never been fixed. It wasn't reproducible with JOGL.

I fixed this bug in JOGL. I asked them to fix it in the same example in their library but nothing has been done and I'm unable to find where I talked about that, sorry. There are only 2 lines to fix.

The very last bug isn't fully fixed in the second major version of this library as far as I know but I can't reproduce it because my current configurations expose the refresh rate unlike the one I used in 2010.

gouessej wrote

I wish you good luck when some users complains about "nothing works", "pixel format not supported", "heu...... rather use software rendering

It is necessary to use an "hidden" switch to allow software OpenGL when using this library if you don't want to get the error message "pixel format not supported". I admit that I was annoyed by the common excuse consisting in claiming that there was no bug in their library and that it was coming from the desktop manager, the operating system or the driver. Just look at the occurrence of "driver bug" and "driver issue" in some of their replies. As I explained here, I had numerous problems with this library under GNU Linux. I consider that I cooperated a lot to improve the situation, I sent some screen captures to the developers, I investigated for several months.

I remind that some users of this library claimed that JOGL was dead for years even before Sun Microsystems / Oracle abandoned it which lead to some stress. There's no smoke without fire. Just use your favorite search engine and look for the words "jogl" and "dead" to see it by yourself. This is usually what I mean when I talk about their FUD campaign against JOGL.

Therefore, I see no intentionally false statement in my posts. In my humble opinion, his accusation of defamation is legally inadmissible and the potentially insulting term was removed from my post. He has the right to lodge a complaint against me if he still considers I defamed his team but there are some statutory limitations (in other words, it's too late for legal actions). I would be grateful to him if he stopped misquoting my posts.

Finally, I should behave myself to avoid causing some troubles and harming JogAmp in the future. In my humble opinion, it's difficult to keep cool, smart and polite with a very few people who instrumentalize some Java websites and IRC channels to harm my reputation (one of them used my last name with the word "terrorist") and to deny the reality (especially the FUD campaign and the fact that most major engines don't only support their library) but I must not answer to those provocations. I would like to set some rules for this forum to prevent it from being used to harm JogAmp users.