[External] : Re: JEP-412 & OpenGL

[Samuel Audet]

Hi, Martin,

For what it's worth, OpenGL is considered legacy tech these days. I 
would suggest looking into Vulkan...

Samuel

On 11/15/21 02:27, Martin Pernollet wrote:
> Thank you John!
> 
> My assumption about throwing JOGL & Java3D was that the complexity of the OpenGL world prevents to ensure the "Write it once, run it everywhere" at a reasonnable cost, hence was not worth pursuing.
> 
> OpenGL has its own way of dealing with GPU versions and capabilities. Lot of opengl features rely on extensions and you do not really know in advance which extensions are available on your clients' computers. There is also GLSL which can also be versionned separately from OpenGL. Sven Gothel has done a great work in JOGL to improve this. Yet, it remains a bit of headache to have a consistent multiplatform experience in such an heterogeneous world!
> 
> Anyway, good news if it rather a "mindset" change rather than a technological limitation :)
> 
> Sent with [ProtonMail](https://protonmail.com/) Secure Email.
> 
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> Le dimanche 14 novembre 2021 à 03:10, John Rose <john.r.rose at oracle.com> a écrit :
> 
>> On Oct 17, 2021, at 6:20 AM, Martin Pernollet <martin.pernollet at protonmail.com> wrote:
>>
>>> Beside these technical questions I have an historical one : JOGL was initially created by Sun and I presume Java3D relied on it when it was released in 1998. Java3D was dropped in 2004 from JDK and JOGL was given to the community. Does someone know what the reasons were? I fear writing something similar to what was done 20 years ago would fail the same way :)
>>
>> I’m not an expert in AWT or graphics APIs but I do know a little about this history. First, 15-20 years is so long that you shouldn’t assume today’s conditions would be at all the same.
>>
>> Second, JOGL was built at a time when Sun had skunkworks projects investigating better native interoperation, similar in some ways to Panama, but Sun made a clear decision not to productize. At the time, JNI was seen by some as kind of defensive wall for Java. Now, not nearly so much. In fact, now Panama’s much more welcoming stance to native code is an important side to Java. Panama has been inspired, in part, by some of those old projects from 20 years ago.