This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-26
Channels
- # announcements (1)
- # asami (7)
- # aws (3)
- # babashka (30)
- # beginners (21)
- # calva (48)
- # cider (11)
- # clj-commons (5)
- # clj-kondo (12)
- # cljdoc (5)
- # cljfx (1)
- # cljs-dev (32)
- # cljsrn (4)
- # clojure (218)
- # clojure-europe (88)
- # clojure-nl (11)
- # clojure-uk (31)
- # clojurescript (8)
- # cursive (98)
- # data-science (6)
- # datomic (49)
- # emacs (12)
- # events (4)
- # fulcro (47)
- # graalvm (3)
- # graphql (4)
- # introduce-yourself (5)
- # java (13)
- # juxt (9)
- # lsp (74)
- # meander (3)
- # membrane (4)
- # missionary (31)
- # off-topic (24)
- # pathom (41)
- # portal (4)
- # reagent (3)
- # releases (1)
- # remote-jobs (3)
- # rewrite-clj (4)
- # shadow-cljs (10)
- # slack-help (2)
- # testing (20)
- # tools-deps (43)
Looking for stats on happiest programmers / female programmer ratio / vegetarian programmer ratio. All those would be useful making my friends and coworkers be interested in clojure. I've heard it mentioned that clojure scores high on these
Hipster to programmer ratio 😄
https://github.com/Dobiasd/programming-language-subreddits-and-their-choice-of-words
Happy... what an interesting comment in a lisp forum xD
Are there developers who choose what programming languages they learn based upon the fraction of existing developers of that language who are vegetarians?
happiest I can understand.
IDK, Alex. There was just something so comforting about Hal and Gerry balancing parens by hand on the chalkboard, in the SICP video lecture seires.
https://insights.stackoverflow.com/survey/2021#technology-most-loved-dreaded-and-wanted only about the "happiest" bit, but still.
What makes me happy is when i can sit down at a system and tell it i want something and its like... sure.
Naming question: is there a common name for the input to a cryptographic signature? i.e. (sign <this-thing> private-key). I'm writing the function that prepares the input for signing, and right now I'm calling it
signing-input` but I don't love it.
Oh, sorry, I'm looking for a name for the function that produces x
- so, maybe finalize-doc
, signature-payload
, signing-input
...
Can't that function be a part of sign
, so it never becomes a part of the API and you don't have to worry about its name?
Unfortunately it can't be part of sign
because we need to sign different types of things that have different canonical serializations, and sign
really shouldn't have to care about what it's signing.
plaintext
, payload
, input
, s
, bytes
, data
> because we need to sign different types of things that have different canonical serializations
Am I correct in inferring that the function you're trying to name is simply serializing its argument? If so, why not something like serialize
or serialize-for-signing
?