Fork me on GitHub
Slack Archive

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

2023-03-10

Channels

#off-topic
<
2023-03-10
>
teodorlu11:03:00

From https://play.teod.eu/nassim-taleb/’s https://play.teod.eu/the-bed-of-procrustes/, chapter “Chance, Success, Happiness, and Stoicism”: > They are born, then put in a box; > they go home to live in a box; > they study by ticking boxes; > they go to what is called “work” in a box; > where they sit in their cubicle box; > they drive to the grocery store in a box to buy food in a box; > they go to the gym in a box to sit in a box; > they talk about thinking “outside the box”; > and when they die they are put in a box. > All boxes, Euclidian, geometrically smooth boxes. Try substituting “type” for “box” 😄 Edit 2023-03-16: fixed links! Should have been http://play.teod.eu all along, not localhost 😅

😅 4
😁 2
dvingo14:03:51

or hashmap... or list... We're all the same just different boxes..

😄 2
Gerome11:03:56

That link points to localhost.

teodorlu12:03:24

@UPJP9G4G1 man, sorry! Thanks for letting me know. The links should have been https://play.teod.eu/nassim-taleb/ and https://play.teod.eu/the-bed-of-procrustes/.

Gerome13:03:26

Um, why is this pointing a page with just a couple of links instead of directly to Wikipedia?

teodorlu13:03:15

I guess linking directly to wikipedia would make sense in this case. I like maintaining my own foregin references for a few reasons: 1. I can link to Wikipedia from one place, meaning there's only one place I have to change the link 2. I can expand a foreign reference page to a page commenting on that foreign reference (like https://play.teod.eu/the-beginning-of-infinity/) a. Which in ideal world, perhaps renders in a way that makes it easy to go straight to Wikipedia 3. I'm using Org-roam to manage my content, and adding https://github.com/org-roam/org-roam/blob/74422df546a515bc984c2f3d3a681c09d6f43916/org-roam-node.el#L673-L715 is more ergonomic when I'm writing than maintaining HTTP(S) links by hand. Perhaps more of a lengthy answer than you wanted, given that you don't necessarily care too much about my personal knowledge base 🙂

hiredman22:03:53

I saw this video the other day https://www.youtube.com/watch?v=o-4jOG_ayuI with some interesting shots fired at the jvm's existing (and some nextgen garbage collectors)

👀 6
hiredman22:03:04

it seems to connected to the Immix gc, which was the inspiration for a new gc that is being worked on for guile

hiredman22:03:20

https://dl.acm.org/doi/pdf/10.1145/3519939.3523440 is the paper about the new gc they gets talked about a fair bit at the end of the talk, it is an interesting mix of ref counting and gc at different granularities

👍 2
Daniel Gerson11:03:27

I imagine it's very workload specific. Targeting pause time rather than latency probably makes sense if you're writing a mobile game, even though I know most premium games wouldn't dream of using the JVM.

genekim05:03:17

This was a cool talk — thanks for posting. What caught my attention: one is the coauthors was able to implement a new GC for openjdk in 11 weeks, thanks to modularity , and which beat all the other GCs in performance. And they built the GC in Rust, which apparently is a big selling point for them. What blew me away: they’re adapting this GC into ruby, Python, Julia, etc. said OpenJDK was easiest because of there with they did to modularize it 5+ years ago. I think I’ve seen in GraalVM talks about how they’re still dealing with places where the vm/JIT still knows too much about the GC.