CFV: Project Trinity

mark.reinhold at mark.reinhold at
Wed Apr 26 14:31:16 UTC 2017

2017/4/24 12:54:54 -0700, karthik.ganesan at
> ...
> It may look ambitious, but if we restrict ourselves to a particular 
> domain of bulk data processing and look at this library as a domain 
> specific java library that offers a standard interface backend to 
> multiple accelerators, it is still a plausible goal to achieve. Such an 
> API will have the best chance for adoption in the "portable" Java world.

Aside from the potential overlap with existing Projects, which others
have already pointed out, what I don't yet see here is a strong reason
for why this needs to be an OpenJDK Project.

The Sumatra, Panama, and Valhalla Projects are exploring changes that
are intimately tied to the JDK.  Trinity, as far as I understand it,
proposes to build a library on top of the JDK.  The OpenJDK Community
aims (per the Bylaws [1]) to foster the development of "implementations
of present and future versions of the Java Platform, Standard Edition,
as defined by the Java Community Process, and ... closely-related
projects."  Trinity may, in the end, prove to be a huge success, but
if it's not intimately tied to the JDK then why does it need to be
developed in OpenJDK Project?  Why can't this work be done on GitHub
or Bitbucket?

- Mark


More information about the discuss mailing list