Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #38728 > unrolled thread

Re: Release Frequency

Back to article view | Back to comp.lang.java.programmer

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Release Frequency Robert Klemme <shortcutter@googlemail.com> - 2019-02-24 18:13 +0100
    Re: Release Frequency Daniele Futtorovic <da.futt.news@laposte-dot-net.invalid> - 2019-02-24 19:16 +0100
      Re: Release Frequency bursejan@gmail.com - 2019-02-24 18:15 -0800
        Re: Release Frequency Graeme Geldenhuys <graemeg@example.net> - 2019-04-08 12:37 +0100
          Re: Release Frequency Arne Vajhøj <arne@vajhoej.dk> - 2019-04-13 22:45 -0400

#38728 — Re: Release Frequency

On 24.02.19 16:05, Stefan Ram wrote:

>   Someone writes a book on Java SE 12 - It's outdate on its
>   release date already (or at least readers might think so
>   when they read that Java SE 13 is out).

Are books still a thing?  I thought this was so 20th century...

;-)

	robert

-- 
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/

[toc] | [next] | [standalone]

#38729

On 2019-02-24 18:13, Robert Klemme wrote:
> On 24.02.19 16:05, Stefan Ram wrote:
> 
>>   Someone writes a book on Java SE 12 - It's outdate on its
>>   release date already (or at least readers might think so
>>   when they read that Java SE 13 is out).
> 
> Are books still a thing?  I thought this was so 20th century...

Right. He meant: a podcast that you can listen to while eating while
exercising while repainting your home.

[toc] | [prev] | [next] | [standalone]

#38730

I guess the release frequence is in revers proportion
to the speed of the new JDKs. I get for the same
byte code on the same mac machine:

JDK 1.8.0 202 : 9'126 ms

GraalVM 1.0.0 rc12 : 9'667 ms

JDK 13 : 13'646 ms

And the winner is, good ole JDK 1.8. Interestingly
on a newer windows machine, the winner is GraalVM.
Unix, I didn't test.

On Sunday, February 24, 2019 at 7:16:51 PM UTC+1, Daniele Futtorovic wrote:
> On 2019-02-24 18:13, Robert Klemme wrote:
> > On 24.02.19 16:05, Stefan Ram wrote:
> > 
> >>   Someone writes a book on Java SE 12 - It's outdate on its
> >>   release date already (or at least readers might think so
> >>   when they read that Java SE 13 is out).
> > 
> > Are books still a thing?  I thought this was so 20th century...
> 
> Right. He meant: a podcast that you can listen to while eating while
> exercising while repainting your home.

[toc] | [prev] | [next] | [standalone]

#38881

On 25/02/2019 02:15, bursejan@gmail.com wrote:
> JDK 1.8.0 202 : 9'126 ms
> 
> GraalVM 1.0.0 rc12 : 9'667 ms
> 
> JDK 13 : 13'646 ms
> 
> And the winner is, good ole JDK 1.8. 


Umm.... That's interesting. I thought the whole idea of JRE "modules"
was to improve efficiency and remove bloat.... Guess not!

Regards,
  Graeme

[toc] | [prev] | [next] | [standalone]

#38917

On 4/8/2019 7:37 AM, Graeme Geldenhuys wrote:
> On 25/02/2019 02:15, bursejan@gmail.com wrote:
>> JDK 1.8.0 202 : 9'126 ms
>>
>> GraalVM 1.0.0 rc12 : 9'667 ms
>>
>> JDK 13 : 13'646 ms
>>
>> And the winner is, good ole JDK 1.8.
> 
> Umm.... That's interesting. I thought the whole idea of JRE "modules"
> was to improve efficiency and remove bloat.... Guess not!

Not accurate.

https://openjdk.java.net/projects/jigsaw/spec/reqs/

<quote>
  As outlined in the JSR, the specific goals are to provide and enable:

     Reliable configuration, to replace the brittle, error-prone 
class-path mechanism with a means for program components to declare 
explicit dependences upon one another;

     Strong encapsulation, to allow a component to declare which of its 
APIs are accessible by other components, and which are not;

     A scalable Java SE Platform, whose components can be assembled by 
developers into custom configurations that contain only the 
functionality actually required by an application;

     Greater platform integrity, to ensure that code that is internal to 
a platform implementation is not accessible from outside the 
implementation; and

     Improved performance, by applying whole-program optimization 
techniques to complete configurations of platform, library, and 
application components.
</quote>

Arne

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.java.programmer

csiph-web