This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-12
Channels
- # aleph (6)
- # announcements (11)
- # babashka (24)
- # beginners (127)
- # calva (33)
- # chlorine-clover (5)
- # cider (7)
- # clara (9)
- # cljs-dev (54)
- # cljsrn (5)
- # clojure (61)
- # clojure-australia (8)
- # clojure-bay-area (11)
- # clojure-europe (36)
- # clojure-italy (3)
- # clojure-nl (3)
- # clojure-spec (6)
- # clojure-taiwan (1)
- # clojure-uk (8)
- # clojurescript (94)
- # code-reviews (2)
- # community-development (6)
- # conjure (26)
- # core-typed (1)
- # cursive (3)
- # datahike (4)
- # datomic (14)
- # events (1)
- # graphql (1)
- # honeysql (49)
- # introduce-yourself (5)
- # jobs-discuss (15)
- # kaocha (6)
- # lsp (8)
- # malli (1)
- # meander (5)
- # nrepl (1)
- # off-topic (21)
- # other-languages (1)
- # pathom (13)
- # podcasts-discuss (1)
- # polylith (1)
- # reitit (16)
- # shadow-cljs (50)
- # spacemacs (11)
- # sql (11)
- # tools-deps (21)
- # unrepl (1)
- # vim (9)
so git basically has an objects directory and a refs directory
> The objects
directory stores all the content for your database, the refs
directory stores pointers into commit objects in that data (branches, tags, remotes and more)
By the pigeonhole principle, because there is magic there, it must be in one of those two places, maybe both.
magic, i mean.
I'm using this "read to me" text to speech chrome add on ... it's called... Read Aloud. Highly recommend it. It's by some company named "LSD Software" :rolling_on_the_floor_laughing: So I'm thinking "wow i'm a genius" when I have it reading Git documentation to me from the other room... until it starts reading SHA1 hashes out loud ONE SIXTY NINE THIRTY THREE THOUSAND SEVEN almost perfect
Reminds me of when I used to get robocalls from Pagerduty in the middle of the night and it was just constantly shouting IP addresses
Hahaha that's great
How did I only learn today that GitHub Actions has a ābadgeā you can add to your README to show the status of your builds?
I finally getting my covid vaccination on Monday! It feels like I've been waiting forever
Hi, I just received an invitation to this group and am glad to be a part of it š I am a co-founder of a startup in the IT industry, I will be glad to share my experience and help you here! Have a great week, everyone!
Reading the "Lisp: Good News, Bad News, How to Win Big" paper. Can someone explain to me why continuations are an "ugly stain"? > There should be a simple, easily implementable kernel to the Lisp. That kernel should be both more > than Schemeā modules and macrosāand less than Schemeācontinuations remain an ugly stain > on the otherwise clean manuscript of Scheme.
Well, that is Richard Gabriel's writing, so his opinion, but I can say from my own view (I am not an expert in continuations) that continuations seem to be a theoretically interesting feature from a language implementer and "from what smallest set of lego blocks can I build everything anyone would ever want in a programming language" kind of approach, which Scheme definitely exemplifies, but in most cases a developer who wants multiple threads, for example, would far prefer a thread library, not to build them out of continuations.
Clojure is my first (and only) Lisp that Iāve learned/used. Iāve always wondered if thereās any value in exploring other Lisps? From the outside, all the ones Iāve looked at look kinda archaic (few good data structures, mutable by default, problems with basic multithreading, etc). Am I wrong? Where can Common Lisp, Scheme (or other Lisps) be appropriate where Clojure is not?
Racket is one I've always found interesting. Clojure is very against macros, while racket takes the opposite approach. What if you really leveraged macros to create DSLs?
(I just posted this, itās quite strange) https://news.ycombinator.com/item?id=27131477
This is not strange nor undocumented behavior.* It is illegal, though. But the worst that happens is a fine is applied, and it would appear that that fine does not outweigh the profits garnered by coercing users into device upgrades via artificial slowness. *documented by users and newspapers and courtroom stenographers. not apple directly
Related (Feb 2020 finally brought a judgement around in Gaul) https://www.bbc.com/news/technology-51413724 May 2020 via the verge. Apple agrees to pay $500 million (715,000 iPhone's worth) in artificial slow down settlement https://www.theverge.com/2020/3/2/21161271/apple-settlement-500-million-throttling-batterygate-class-action-lawsuit
upgrade more like delayed am i rite
I think itās just a background job that runs after an upgrade. But it would be helpful for there to be some sort of a notification, at least for developers.
upgrade more like delayed am i rite
Clojure is my first (and only) Lisp that Iāve learned/used. Iāve always wondered if thereās any value in exploring other Lisps? From the outside, all the ones Iāve looked at look kinda archaic (few good data structures, mutable by default, problems with basic multithreading, etc). Am I wrong? Where can Common Lisp, Scheme (or other Lisps) be appropriate where Clojure is not?