| 7 Sep 2023 |
|  woobilicious joined the room. | 17:11:46 |
| 8 Sep 2023 |
 JoelMcCracken | yeah its hard to say | 03:10:42 |
| JoelMcCracken | doom is tricky | 03:10:49 |
| JoelMcCracken | it just has soo much code | 03:11:03 |
| JoelMcCracken | its quite a big project, too big imo | 03:11:08 |
| JoelMcCracken | not to say that like there aren't good reasons for all that code; i d; | 03:11:34 |
| JoelMcCracken | (that I can't comment) | 03:11:44 |
| JoelMcCracken | but i can say that most of it just really doesnt seem very simple | 03:11:55 |
| JoelMcCracken | ive been wondering if thats why it has stalled | 03:12:14 |
| JoelMcCracken | * ive been wondering if thats why it has stalled; the big refactor is ending up in a big mess | 03:12:40 |
| JoelMcCracken | but, FYI, I think doom development is now un-stalling | 04:01:49 |
|  @ulli:hrnz.li left the room. | 20:41:32 |
| 9 Sep 2023 |
| woobilicious | Is that doom upstream, or the nix package? | 02:26:45 |
 mei 🌒& | woobilicious: JoelMcCracken's last messages were about doom itself | 03:11:27 |
| woobilicious | Ahh okay :-) | 03:12:13 |
| woobilicious | I wouldn't mind moving to a "simple-emacs" thing using nix that lets me quickly setup a decent setup of emacs without having to learn lisp. | 04:05:00 |
| mei 🌒& | i've changed my mind a bit on that since then | 04:06:42 |
| mei 🌒& | i think doom having its own module system is good, but it should be way more modularized. almost like nixpkgs' evalModules is reusable. it shouldnt be a part of The Big Doom Blob | 04:07:19 |
