Initial discussion of solutions for issues presented in amber-dev/2022-May/007322

[Julian Waters]

Hi Lutz,

I did outline the issue in a previous posting to the list, though I'd
appreciate feedback on how I could improve my outline of the problem. In my
opinion though, just because it's how Java was initially designed shouldn't
mean Java should always be written strictly OOP only. As Brian said in an
earlier post, not everything has to be forced through OOP. As for (3), this
isn't proposed as a catch-all solution, I'm only hoping to get the
discussion started with very rough and crude suggestions so people with
better ideas than me can contribute to this.

best regards,
Julian

On Thu, May 19, 2022 at 3:48 PM Lutz Horn <lutz.horn at posteo.de> wrote:

> Hi,
>
> what I‘ve learned from silently following this list is, that if you
> propose a solution for a problem you first have to demonstrate that
>
> 1. there is a problem
> 2. it is a problem worth solving
> 3. the proposed solution is a good solution
>
> I think your proposal fails at step 1. I don‘t see much code written
> procedurally. And if I see such code, I argue for it to be changed.
>
> Lutz
>
> > As mentioned, a significant amount of Java boilerplate stems from code
> that
> > is written procedurally
>
>