Re: [External] : Re: JEP draft: Integrity and Strong Encapsulation

2023-05-22 Thread Ron Pressler
> On 22 May 2023, at 15:01, Andrew Dinn wrote: > > Hi Ron, > > I've been studiously reading all the discussion on the integrity JEP > (currently numbered 8305968) -- whether direct comments in this thread or > indirect comments from the various threads that relate to changing the > dynamic

Re: JEP draft: Integrity and Strong Encapsulation

2023-05-22 Thread Andrew Dinn
Hi Ron, I've been studiously reading all the discussion on the integrity JEP (currently numbered 8305968) -- whether direct comments in this thread or indirect comments from the various threads that relate to changing the dynamic agent load default. It seems obvious to me that there is a rath

Re: [External] : Re: JEP draft: Integrity and Strong Encapsulation

2023-05-11 Thread Ron Pressler
> On 11 May 2023, at 12:04, Dan Heidinga wrote: > > I had read this JEP as a position statement on future directions given it > refers to the preventing dynamic loading of agents (a future action) and > restricting JNI (future) while also talking about strong encapsulation (past). Restrictin

Re: [External] : Re: JEP draft: Integrity and Strong Encapsulation

2023-05-11 Thread Dan Heidinga
On Wed, May 10, 2023 at 2:42 PM Ron Pressler wrote: > Before I get to your specific points, let me clarify that this > informational JEP is a summary of *past* work and decisions (except maybe > the FFM/JNI restriction) that, though already delivered or announced, their > full motivation was neve

Re: [External] : Re: JEP draft: Integrity and Strong Encapsulation

2023-05-10 Thread Ron Pressler
Before I get to your specific points, let me clarify that this informational JEP is a summary of *past* work and decisions (except maybe the FFM/JNI restriction) that, though already delivered or announced, their full motivation was never canonised in JEP form. Everything it describes has either

Re: [External] : Re: JEP draft: Integrity and Strong Encapsulation

2023-05-08 Thread Dan Heidinga
Thanks for the response, Ron. My comments are in line. On Fri, May 5, 2023 at 8:10 AM Ron Pressler wrote: > > > On 4 May 2023, at 21:32, Dan Heidinga wrote: > > > I’ve read this draft a number of times and each time I struggled with the > framing of the problem given Java’s success over the pa

Re: [External] : Re: JEP draft: Integrity and Strong Encapsulation

2023-05-05 Thread Ron Pressler
On 4 May 2023, at 21:32, Dan Heidinga mailto:heidi...@redhat.com>> wrote: I’ve read this draft a number of times and each time I struggled with the framing of the problem given Java’s success over the past almost 30 years. The old regime worked when: 1. Almost all the runtime was written in

Re: JEP draft: Integrity and Strong Encapsulation

2023-05-04 Thread Dan Heidinga
Hi Ron, I’ve read this draft a number of times and each time I struggled with the framing of the problem given Java’s success over the past almost 30 years. Framing the problem with statements like: “Strong encapsulation offers a solid foundation to build on. Without it, code is a cas