Context and expectations

Daniel Latrémolière daniel.latremoliere at gmail.com
Fri Jul 20 15:43:42 PDT 2012


>> ...
>>
>> I don't know if I was the target of your comment, but given your response at my
>> mail was the preceding message in the mailing list, I will respond, ...
> You were in no way the intended target of my comment.  I'm sorry that
> you interpreted it that way.
I am sorry for overreacting (I like history and History learn that 
rumours or unnamed messages has killed many people). Your response on 
another topic and your lack of response after David and Debasish 
responses to your mail, triggered mine. In this mailing list and given 
long and conflictual history of Java modularity, coming back with an old 
topic like JSR 294 seemed, to me, mostly off-topic for Jigsaw but good 
fitting for "asking questions that've already been answered" (but I had 
no other living mailing list for my question).

Honestly, I continue to dislike Jigsaw remembered goal: "The goal of 
this Project is to design and implement a standard module system for the 
Java SE Platform, and to apply that system to the Platform itself and to 
the JDK.", because "module" say all or nothing depending of reader, but 
is not a clear set of potentially independent features (internal 
improvement of OpenJDK code, abstraction for hiding some parts of 
implementation, deployment package compatible with RPM/DEB, object with 
an externally managed lifecycle, storage repository for code and JIT 
metadata, etc.) coming each with his improvements to developer/sysadmin 
life (the only real goals of OpenJDK for me) and needing or not new 
public API/language changes.
I would prefer something like "The goal of this Project is to design and 
implement a module system for the Java SE Platform, to improve 
abstraction in Java code and increase performance of VM and simplicity 
of deployment."
For me, Java developers has no direct interest to know if Jigsaw is used 
by OpenJDK itself or not (it is an OpenJDK-implementation detail and not 
a goal, even if it is a big detail). By example, OpenJDK can use 
specific extensions to Jigsaw (not public module API) for his own 
modularisation without any knowledge from Java developer.

> In anticipation of an influx of newcomers to this list as a result of
> the proposal I made earlier this week, I thought it'd be useful to relay
> some basic information and set expectations.  I don't think that what I
> said is particularly unusual or controversial for open-source projects.
I have most frequently seen these rules remembering in the subscription 
mail for new users or when discussions on mailing list becomes 
problematic but not when all is normal (then triggering my mail). Sorry.

I am sorry for my overreaction,
Daniel.



More information about the jigsaw-dev mailing list