Sharing experiences with the latest EA build // #ReflectiveAccessToNonExportedTypes #ResourceEncapsulation

[Malachi de Ælfweald]

On Fri, Sep 30, 2016 at 8:16 AM, Rafael Winterhalter <rafael.wth at gmail.com>
wrote:

> This would be a way to go but I am afraid that currently, the most likely
> outcome would be to make all modules weak and keep them weak forever.
> Personally, I believe that weak modules might become the default choice for
> most developers as migration to proper module turns out so difficult and
> would especially bind senior developers who tend to have the least amount
> of time available.
>

​The most likely scenario, for most developers, is going to be whatever the
tools do for them automatically.
If it requires a lot of manual investment to setup, it will either not be
done or will be replaced with the first 3rd party tool to automate the
process (regardless of how that tool does it).​
​Devs in general may want to spend time figuring it out, but the Product
team will be unlikely to allow it to be prioritized over other tickets in
their backlogs.​




Malachi de Ælfweald
http://www.google.com/profiles/malachid