Re: [threeten-develop] API size requirements and actual API size

[Stephen C. <sco...@jo...>]

On 20 July 2012 07:00, Meno Hochschild <mho...@gm...> wrote:
> After the newest proposal to postpone java modularization jigsaw
> concept, what is the effect on jsr 310 / Threeten?
>
> According to former mails by Roger Riggs I have understood that Oracle
> wished to limit the overall size of the api to approximately 100 KB +/-
> 20%. As far as I have seen the api size of Threeten has ALWAYS been much
> bigger than that, even after the split of Threeten into several modules
> (core/standard/etc). Now the formatting package and base classes of
> chrono package also repacked into core, the api size has undoubtedly
> increased again far beyond the given numbers above. So I would like to
> know if the given api size requirements have anything been more than
> just a soft requirement (a wish rather than a requirement), or is it
> even a constant threat to including of Threeten into Java 8 regarding
> the actual size of surely more than 200KB, or are those requirements now
> completely obsolete after postpone of jigsaw and can be lessened?

Personally, I'm working to the constraints that Oracle provide.
Previously, that was a strong reduced core module, however I always
viewed that as being in conflict with the need for a suitably powerful
API for the needs of enterprise Java. The emphasis on reduction has
served us well to reduce down the codebase to something more effective
in other ways. And secondary calendar systems can continue to be a
secondary module.

My personal opinion is that modularizing the core of Java in JDK 9 (3
to 4 years away) will be too late for many embedded devices. And in
reality, splitting the core of Java is now a very difficult task.

For now , and Early Draft Review 2, the current layout makes sense.

Stephen