Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2022-04-26

Channels

#graalvm
<
2022-04-26
>
Ben Sless12:05:48

Wonder if the small loop unrolling will play in clojure functions such as get-in

ericdallo12:04:27

Release notes not on webpage yet 😅

borkdude12:04:28

release notes coming tonight. I think they might now have some way to develop faster

ericdallo12:04:32

Why faster? not aware of what they were working

borkdude12:04:34

a development mode which doesn't optimize everything straight away

ericdallo12:04:15

Hum, interesting!

ericdallo13:04:55

> support for darwin-aarch64 Will this be the correct option for M1 users?

borkdude14:04:03

But now we need a CI which can actually build this

ericdallo14:04:16

yeah, good point

ericdallo14:04:20

Nice, it seems there are good improvements on size, will try on clojure-lsp later

borkdude14:04:51

Image build time goes down in linux CI from 3m11 to 2m41, nice improvement

metal 2
borkdude14:04:43

image size goes down by ~ 1mb. nice :) Not huge, but I'm already glad the size is not going up. There were a few releases in the past that added 5mb for unclear reasons.

borkdude14:04:01

it's a keeper, merged :)

Chris Lowe15:04:49

Is there any information on GraalVM EE licensing for targeting AWS Lambda? Specifically, the Oracle Java SE Subscription states that a processor metric is used. If there are a number of Lambda functions, each compiled using GraalVM EE native, how would this map to the processor metric? Any information would be appreciated

borkdude15:04:18

Ask the graalvm folks

Chris Lowe15:04:03

Sorry - wrong place 🙂