This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-11
Channels
- # announcements (3)
- # babashka (62)
- # beginners (58)
- # calva (40)
- # cider (3)
- # clj-kondo (75)
- # cljdoc (14)
- # clojars (8)
- # clojure (110)
- # clojure-australia (6)
- # clojure-europe (38)
- # clojure-hungary (1)
- # clojure-india (4)
- # clojure-italy (1)
- # clojure-nl (3)
- # clojure-spec (4)
- # clojure-uk (3)
- # clojurescript (45)
- # conjure (4)
- # cursive (35)
- # data-science (1)
- # datomic (11)
- # events (2)
- # exercism (4)
- # figwheel-main (4)
- # fulcro (103)
- # graphql (16)
- # helix (1)
- # holy-lambda (16)
- # honeysql (1)
- # introduce-yourself (3)
- # jobs (1)
- # keyboards (2)
- # lsp (4)
- # malli (11)
- # membrane-term (3)
- # mount (2)
- # nextjournal (2)
- # off-topic (53)
- # pathom (30)
- # pedestal (2)
- # portal (22)
- # rdf (1)
- # re-frame (7)
- # reagent (3)
- # reitit (5)
- # remote-jobs (6)
- # shadow-cljs (20)
- # sql (8)
- # tools-build (10)
- # vim (4)
- # xtdb (12)
AWS wants to gather some basic information about the Java/HL Lambda version usage. The version of Java + HL would be send via user agent. I would like to ask you guys if you are okay with me providing that information to AWS starting from next HL version?
I think so. What is the reason you would like to have it optional?
I don’t mind sharing but forcing analytics sharing on anyone isn’t a good choice. hence the option
Would you be ok with it if there would be an option to disable analitics, but the default option would be „analitics enabled”?
I guess the real question is how giving this information to amazon helps them and why should we care
> when customers use the provided.al2 runtime we don't know how they use it we don't know whether they're doing R, PHP, GraalVM native or anything else. since AWS is a data driven company, we want to try and learn more about how our customers are using the platform so that we can best support improvements This what has been said to me by AWS Architect. I think that they also want to measure how much GraalVM impacts the usage of Java for AWS Lambda. AWS does a lot of stuff with Oracle and GraalVM lately.
> since AWS is a data driven company, we want to try and learn more about how our customers are using the platform so that we can best support improvements This is the most vague possible statement > I think that they also want to measure how much GraalVM impacts the usage of Java for AWS Lambda. AWS does a lot of stuff with Oracle and GraalVM lately. This is projection
Chances are they just want to make a pie chart and justify investments into graalvm or whatever. Its still not good science though, and i don’t fully buy that they can’t figure out what people are using provided.al2
for. I would buy that they can’t do it legally
i’m not going to avoid using HL if you include info in responses. We send *Server:* Jetty(...)
in all our regular http responses. Its okay.
Fwiw I would share because they have supported me with credits. I think you'll find a lot of Devs who are suspicious of AWS based on some of their moves. At least optional means you don't lose those Devs
Mark was asking if I could include it because he does not know Clojure himself. Anyway this information is very basic, so I don’t feel like it's something that we should protect at all cost. AWS supports the development via occasional credits. It's not much, but I would also like to say thanks that way.
Thank you all for your input. 🙂