Wanted to see me speak at #FOSDEM but couldn't make it?
Uncategorized
18
Posts
11
Posters
11
Views
-
Here are some other #FOSDEM talks I recommend:
Wastrel: WebAssembly Without the Runtime by @wingo (Wastrel uses #Spritely Hoot!) https://fosdem.org/2026/schedule/event/HT9HAG-wastrel-webassembly-without-the-runtime/
Willow - Protocols for an uncertain future (wins "Christine's award for most charming presentation") by @gwil https://fosdem.org/2026/schedule/event/CVGZAV-willow/
Automerge + Keyhive Design Overview by @expede https://fosdem.org/2026/schedule/event/BZ9CAE-automerge/
BLUE - A generic build-system crafted entirely in Guile by @shepherd https://fosdem.org/2026/schedule/event/3A7VGM-blue/
raylib: a 12-year adventure as a solo-maintainer https://fosdem.org/2026/schedule/event/883PBF-raylib-12-year-adventure/
Too many other good talks to list of course (and I haven't gotten through all of them) but all of the above talks totally rule
-
-
Oh and one more talk I highly recommend, very complimentary to @wingo's Wastrel talk IMO (tho not using the same tech):
High-Speed Linux Application Execution in the Browser with Binary Translation https://fosdem.org/2026/schedule/event/NABRSD-high-speed_linux_application_execution_in_the_browser_with_binary_translation/
-
Wanted to see me speak at #FOSDEM but couldn't make it? Here's the two talks I gave!
How to Level Up the Fediverse
(co-presented with ActivityPub co-author @tsyesika !) https://fosdem.org/2026/schedule/event/HVJRNV-how_to_level_up_the_fediverse/Lisp is Clay: the Power of Composable DSLs https://fosdem.org/2026/schedule/event/HDE7JZ-lisp-is-clay/
Can't get enough? Need more #spritely talks? We gave a bunch... 🧵
@cwebber it was a great talk! I'm curious to read the rest of the slides you had to skip to learn more 😊
-
Wanted to see me speak at #FOSDEM but couldn't make it? Here's the two talks I gave!
How to Level Up the Fediverse
(co-presented with ActivityPub co-author @tsyesika !) https://fosdem.org/2026/schedule/event/HVJRNV-how_to_level_up_the_fediverse/Lisp is Clay: the Power of Composable DSLs https://fosdem.org/2026/schedule/event/HDE7JZ-lisp-is-clay/
Can't get enough? Need more #spritely talks? We gave a bunch... 🧵
@cwebber I don't see a recording for Lisp is Clay, would you know if it's coming?
-
@cwebber I don't see a recording for Lisp is Clay, would you know if it's coming?
-
@cwebber I don't see a recording for Lisp is Clay, would you know if it's coming?
@quartz I approved the recording with a new time but I guess I probably need to re-approve
-
@quartz I approved the recording with a new time but I guess I probably need to re-approve
@quartz Reviewed and approved the new version, hopefully out soon
-
Oh and one more talk I highly recommend, very complimentary to @wingo's Wastrel talk IMO (tho not using the same tech):
High-Speed Linux Application Execution in the Browser with Binary Translation https://fosdem.org/2026/schedule/event/NABRSD-high-speed_linux_application_execution_in_the_browser_with_binary_translation/
To everyone who pointed it out, yes my Lisp is Clay talk video wasn't up when I posted this! Here it is now: https://fosdem.org/2026/schedule/event/HDE7JZ-lisp-is-clay/
I had a really strong positive reaction from the audience on this talk! If you've ever been wondering "well why is Spritely in lisp/scheme and what are those lisp people doing over there anyway" OR if you have had a hard time articulating why Lisp is great (and not just "it has macros"!) here's a talk for you!
-
To everyone who pointed it out, yes my Lisp is Clay talk video wasn't up when I posted this! Here it is now: https://fosdem.org/2026/schedule/event/HDE7JZ-lisp-is-clay/
I had a really strong positive reaction from the audience on this talk! If you've ever been wondering "well why is Spritely in lisp/scheme and what are those lisp people doing over there anyway" OR if you have had a hard time articulating why Lisp is great (and not just "it has macros"!) here's a talk for you!
@cwebber I was eagerly waiting for this one
-
To everyone who pointed it out, yes my Lisp is Clay talk video wasn't up when I posted this! Here it is now: https://fosdem.org/2026/schedule/event/HDE7JZ-lisp-is-clay/
I had a really strong positive reaction from the audience on this talk! If you've ever been wondering "well why is Spritely in lisp/scheme and what are those lisp people doing over there anyway" OR if you have had a hard time articulating why Lisp is great (and not just "it has macros"!) here's a talk for you!
@cwebber kismet! I went to watch this yesterday and was disappointed! On the queue it goes :)
-
To everyone who pointed it out, yes my Lisp is Clay talk video wasn't up when I posted this! Here it is now: https://fosdem.org/2026/schedule/event/HDE7JZ-lisp-is-clay/
I had a really strong positive reaction from the audience on this talk! If you've ever been wondering "well why is Spritely in lisp/scheme and what are those lisp people doing over there anyway" OR if you have had a hard time articulating why Lisp is great (and not just "it has macros"!) here's a talk for you!
@cwebber Nice! I saw there were CLIM and Symbolics graphics bullet points in the "choose your own adventure" section but they weren't chosen for the talk... Are they expounded on in the org file? I'm curious to read those thoughts if so.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
-
@fucinafibonacci @ambiente molto interessante per le spiegazioni sulla complessità della rete e sui costi di gestione!
-
@ryan @tikaro depending on where you live², IKEA duvet cover¹ are an excellent source for fabric that is cheap, easy to work with, often has nice prints, is usually 100% cotton (or at most rayon / lyocell) and is actually usable for things that will get worn (mostly tops, or very lightweight bottoms) and/or used.
And speaking of cotton, one think that will make the difference in the way your clothing will look is pressing all seams as you sew them: you don't need a fancy iron, but an iron is necessary. And cotton and other natural fibers (plus rayon) will work with you under the iron, synthetics will work against you, and will cause you lots of suffering.
¹ other than the very cheapest ones, that tend to be quite lightweight and transparent, and the fancy ones, that are probably good for everything listed above, but not cheap.
² some countries apparently have shops with cheap cotton. I don't live on one of those :D
-
meloni vuole pagare sondaggisti perchè non dicano questo
-
@mos_8502 oh and another more modern choice you could make too, depending on application: disregard package management entirely and treat the entire OS as an immutable image that's built as an atomic unit, with updates being done by having a pair of A/B partitions. You boot off the current active partition, and to update the OS you write out the entire new image to the inactive and reboot onto it.
The Fedora Atomic distros do this, as do the Universal Blue ecosystem (they're essentially running the "new" atomic stack that future Fedora will use). CoreOS was arguably the OG at this for widely known distros, although this is how a large swatch of embedded linux operates, using either buildroot to generate images or Yocto (whose build system is a horrific crime, but it's also very powerful, can generate whole disk images _and also_ a stream of delta updates for efficient upgrading, and is widely supported by embedded linux hardware and software vendors so a lot of stuff ends up using it, even though I find it horrible every time I try touching it)
-
@mos_8502 if you're Ubuntu, you just start with Debian, and then make it worse.
That's also how I do it for the OS my employer ships on our robots. I start with Ubuntu and mostly make it worse, but also make it better by replacing snap packages with regular debs.
-
@mos_8502 The biggest pains, if you're not reusing someone else's package manager: how do you express dependencies between packages? Can you have optional deps like debian's "recommended" ? Can you have virtual packages that can be provided by multiple concrete packages (I don't have an example on tap but debian, arch, gentoo all support this for stuff like swapping out libc implementations or pulseaudio vs. pipewire), how do you version packages where the upstream might have an unhelpful or missing versioning scheme of its own, how do you handle the million different build systems that upstream uses, how fancy is your dependency resolution algorithm (can be anything from "unhelpfully useless" to "NP-hard and sometimes takes hours to compute a solution" - most useful distros land somewhere in the middle).
None of this _has_ to be hard, at every step you can make some simplifying assumptions/decisions that cut off some flexibility from your distro in exchange for a simpler system to build/use/maintain. There not being any "correct" answer is why there's a million distros with more showing up all the time.
-
Eh sì: sembra che eolico, solare, idroelettrico siano più convenienti 🤷♂️. Le rinnovabili rischiano di far saltare i conti del nucleare francese - Startmag https://www.startmag.it/energia/edf-rinnovabili-costi-manutenzione-centrali-nucleari/
