<discocaml_>
<diligentclerk> When I was first starting to use Emacs I listened to all this great stuff people told me about it - it's infinitely customizable! You can do literally anything you want with it!
<discocaml_>
<diligentclerk> there's Org Mode for managing your notes and your whole life in plain text!
<discocaml_>
<diligentclerk>
<discocaml_>
<diligentclerk> it took several years and some software engineering experience for me to realize that I shouldn't be taking all this adoration and praise at face value. The things that people love about Emacs also have their downsides. I don't mean that it's terrible but there are things I wish people told me.
<discocaml_>
<diligentclerk> The flexibility and customizability ultimately comes down to it being written in a highly dynamic language without module boundaries. You can change everything but you potentially have to understand everything if you want to change one thing. Customizing a package feels like going down a rabbit hole where I end up in the innermost workings of a file, trying to modify it without breaking things. I don't like highly dynamic languages! Eli
<discocaml_>
<diligentclerk> People use Org Mode to store lots of metadata in files like goals, with deadlines, scheduled to-do dates, habits they want to track, time logging on projects, etc. all in plain text, but this is all highly structured data which would be a lot easier to query and edit if it was stored in a database instead of being stored in a homebrew markup language with an implementatation-defined syntax. I looked into the Org code and I was disappoin
germ- has quit [Ping timeout: 244 seconds]
germ_ has joined #ocaml
germ- has joined #ocaml
germ_ has quit [Read error: Connection reset by peer]
<discocaml_>
<functionalprogramming> most elisp code i've seen explicitly enables lexical binding
<discocaml_>
<functionalprogramming> also, i think the buffer-as-a-source-of-truth approach is very predictable from an end-user perspective. i see how it gets annoying when some things are just hidden though
<discocaml_>
<diligentclerk> I agree that it opens up a can of worms to have a data structure that could be out of sync with the buffers. It seems like a thorny problem. I guess this is why tree-sitter is becoming so popular because it should make it fast to re-parse and recreate the associated data structure every time you need it.
<discocaml_>
<diligentclerk> Although the fact that you can't save tree-sitter queries to a file is kind of frustrating. It takes me several seconds to open up a Typst file because that's how long it takes to JIT compile the queries it uses for syntax highlighting and indentation
Anarchos has quit [Ping timeout: 265 seconds]
Anarchos has joined #ocaml
tremon has joined #ocaml
remexre has quit [Ping timeout: 260 seconds]
remexre has joined #ocaml
germ| has quit [Read error: Connection reset by peer]
Anarchos has quit [Quit: Vision[]: i've been blurred!]
germ_ has joined #ocaml
rgrinberg has joined #ocaml
rgrinberg has quit [Quit: My Unrecognized Mac has gone to sleep. ZZZzzz…]