News for hackers. Stuff that matters.
Re:The Machine That Builds Itself: The Strengths of the Lisp... by fnordsensei on Monday July 02, 2018 @11:36AM (#17442555)
I found this pretty interesting: https://medium.com/criciumadev/serverless-native-java-functi...

Single data point, but nevertheless.

Cold Execution Times:

  Java Function -> 660 ms
  Native Java Function -> 460 ms
  Go Function -> 470 ms
Hot execution times:

  Java Function -> 30 ms
  Native Java Function -> 30 ms
  Go Function -> 30 ms
Container Memory usage of Hot Function:

  Java Function -> 17.8 MiB
  Native Java Function -> 0.9 MiB
  Go Function -> 1.2 MiB
Container Image Size:

  Java Function -> 266 MB
  Native Java Function -> 13.6 MB
  Go Function -> 15.1 MB
Re:The Machine That Builds Itself: The Strengths of the Lisp... by dorfsmay on Monday July 02, 2018 @02:25PM (#17444184)
What are "Native Java Functions"?
Re:The Machine That Builds Itself: The Strengths of the Lisp... by tkxxx7 on Monday July 02, 2018 @02:48PM (#17444364)
Already compiled to bytecode?
Re:The Machine That Builds Itself: The Strengths of the Lisp... by pjmlp on Tuesday July 03, 2018 @07:59AM (#17449423)
Machine code.