| 12 Oct 2022 |
 ckie (they/them) | but emacs is not an enjoyable thing for me | 08:28:46 |
| ckie (they/them) | lisp pile too big.. | 08:28:57 |
| ckie (they/them) | (and doom "helpfully" catches the stack trace and trims most of it, so that's a thing) | 08:31:23 |
|  Josefine joined the room. | 11:27:11 |
 @hab25:matrix.org | In reply to @qe7ftcyrpg:matrix.org
If you make a minor change to config.el, nix has to rebuild a lot of things. For me it builds 30 minutes to 1 hour, if I remember correctly. could content-adressed nix be a big help regarding this? | 17:40:35 |
 k0kada (he/him) | In reply to @ckie:ckie.dev
lisp pile too big.. Nothing against Lisp, I programmed in Clojure for a time in my previous company and I would say that I love the language (probably still my favorite language, however Nix is a close second) | 19:39:13 |
| k0kada (he/him) | But I hate Emacs Lisp | 19:39:21 |
| k0kada (he/him) | Too much state | 19:39:30 |
| k0kada (he/him) | In reply to @ckie:ckie.dev
(and doom "helpfully" catches the stack trace and trims most of it, so that's a thing) Yeah, there is that
And to think that I would find something worse the Clojure stack traces.... | 19:40:09 |
| ckie (they/them) | i think i played with clojure or maybe racket a few times but no good library support like rust.. | 19:40:13 |
| k0kada (he/him) | I need to try Rust again, but I much prefer dynamic languages | 19:41:11 |
| k0kada (he/him) | Specially ones that are flexible enough to allow me typing when I want/need | 19:41:53 |
| ckie (they/them) | having to look up types in my head kind of breaks my flow | 19:42:35 |
| ckie (they/them) | rust-analyzer is great | 19:42:39 |
| k0kada (he/him) | In reply to @ckie:ckie.dev
having to look up types in my head kind of breaks my flow Yeah, I mean nowadays I like to have some kinda of typing
I just feel that most type systems are to restrictive | 19:43:30 |
| ckie (they/them) | rust takes an interesting direction with that | 19:43:45 |
| k0kada (he/him) | I actually kinda like mypy for typing Python | 19:43:45 |
| ckie (they/them) | like from that pov it's very restrictive but it seems the more restrictive it is the freer it is in another way | 19:44:02 |
| k0kada (he/him) | Or for Clojure I like spec/schema | 19:44:10 |
| ckie (they/them) | like it's more expressive because it doubles down on forcing you to use it | 19:44:23 |
| ckie (they/them) | still not there imo, but is a neat experience to have | 19:44:39 |
| k0kada (he/him) | In reply to @ckie:ckie.dev
like it's more expressive because it doubles down on forcing you to use it I don't like exactly that part, sometimes I kinda like to say "f*** the type system, let me do what O want" | 19:46:38 |
| k0kada (he/him) | * I don't like exactly that part, sometimes I kinda like to say "f*** the type system, let me do what I want" | 19:46:59 |
| ckie (they/them) | yeah sometimes i also feel like that and then i write horrible javascript for a week or two before running back to rust | 19:47:17 |
| k0kada (he/him) | In reply to @ckie:ckie.dev
yeah sometimes i also feel like that and then i write horrible javascript for a week or two before running back to rust The point is that this is controlled, for example, in only one private function | 19:47:48 |
| k0kada (he/him) | Kinda of marking the block as unsafe, you know something sketchy is happening there | 19:48:08 |
| k0kada (he/him) | So I generally just review it with more attention | 19:48:20 |
| ckie (they/them) | c and js are oddly meditative for me while im using them | 19:50:12 |
| k0kada (he/him) | Can't speak for JS | 19:50:57 |
| k0kada (he/him) | But I concur with C | 19:51:02 |
