News for hackers. Stuff that matters.
Re:Windows 3.1 All Over Again by noncoml on Sunday September 24, 2017 @10:26PM (#15327683)
Completely agree.

What saddens me is that only Erlang/Elixir get the “it’s slow” argument although they are in the same class as python and ruby.

Re:Windows 3.1 All Over Again by dahauns on Monday September 25, 2017 @05:55AM (#15329122)
I know what you mean. I don't know how often I've read "I prefer python/ruby/etc. because its not as bloated and slow as Java"...sigh
Re:Windows 3.1 All Over Again by kpil on Monday September 25, 2017 @06:46AM (#15329353)
The only thing slow about java is the time to start the jvm.

For everything else to be faster you need asm, c, c++, fortran, or rust.

Loading an applet over a modem in 1998 doesn't count...

Re:Windows 3.1 All Over Again by sz4kerto on Monday September 25, 2017 @07:15AM (#15329472)
Starting the JVM is <0.5 seconds. On my box it's ~0.1 sec.
Re:Windows 3.1 All Over Again by majewsky on Monday September 25, 2017 @09:20AM (#15330173)
I have programs doing nontrivial things that run in 5 ms, from execve() to exit(). That's milliseconds, not seconds.
Re:Windows 3.1 All Over Again by kpil on Monday September 25, 2017 @10:12AM (#15330630)
Exactly, even fairly complex script languages manages to boot, execute and exit in just a few milliseconds.

Maybe jigsaw is one piece in the puzzle to reduce the time it takes to start.

I doubt it's so bloody complicated, except AOT compilation of all system jars, I suspect it's mainly a matter of getting the time and resources to look at what happens when hello.world is executed.nu

That and relabling executable jars to jxe and the desktop is Java's to grab (that last part was a joke)

Re:Windows 3.1 All Over Again by dahauns on Tuesday September 26, 2017 @07:08AM (#15337639)
Exactly what I was going for.