Conversation

Notices

1. Embed this notice
   anna (navi@social.vlhl.dev)'s status on Sunday, 06-Oct-2024 15:43:21 JST anna
   i've been actually programming without auto-complete the past two days
   
   (because i broke nvim-cmp and didn't have motivation to fix)
   
   tbh it's not that bad
   • Embed this notice
     rakoo (rakoo@blah.rako.space)'s status on Sunday, 06-Oct-2024 15:43:19 JST rakoo

     in reply to
     @navi
     
     I've been simplifying my dev env for some time now: no colors, no autocomplete, no goto definition etc... it started with limitations from my editor and me not configuring it, but then something hit me: all those dev tools are here to tame complexity, meaning it makes complexity easier to work with. But, crucially: it doesn't reduce complexity. Which is my goal. I want software to be easy/simple enough that anyone can jump inside it and fiddle with it. If completion becomes quasi-mandatory then it is a failure.
     
     I now think that not using those things is helping me keep complexity low, and are Bad Practice (tm). Follow me in this weird path !
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Sunday, 06-Oct-2024 16:06:05 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • rakoo

     @rakoo @navi Interestingly for me configuring editors beyond basic settings also is quite uninteresting because I frequently jump in random codebases, some of them with really weird code styles or languages I barely ever use, or so gigantic something like ctags would take ages.
     And usually things like variables/function names are in the terminal's backlog so I just background the editor (Ctrl-Z and then fg command to get it back) to copy-paste them.

     And syntax highlighting is something I appreciate but should be improved, like assignment and comparison operators aren't the same, and I think there's often too many things being highlighted. That said not really worth it for me to tweak this.

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Sunday, 06-Oct-2024 16:54:00 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • rakoo
     @navi @rakoo Yeah but editorconfig by definition messes with the way the editor behaves, I don't want that, put a "make format" or something like that instead.
   • Embed this notice
     anna (navi@social.vlhl.dev)'s status on Sunday, 06-Oct-2024 16:54:03 JST anna

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • rakoo
     @lanodan @rakoo
     
     for the former, there's editorconfig, which a surprising number of projects i've contributed to uses, and some editors (nvim in my case) pick it ip out of the box
     
     for the latter, treesitter provides actual semantic matching on the parser, and failing that, lsp-based color matching is a full on compiler giving you token information to color with (i never used the latter though)