.doom.d VS .emacs.d

Yes, I moved over to logseq a year ago (my old config). I was using emacs/orgmode as my daily driver for about 2 years, but the struggle of getting it installed/loaded on my work system was becoming more difficult since our IT department decided to add encryption on top of other existing encryption. It would take my system 10 minutes to initially load emacs, where my personal Win10 box with WSL would take a few seconds. Eventually I just got tired of it and was already playing with logseq as a daily driver, so I made the commitment and moved over.

https://github.com/nmartin84/.doom.d/raw/master/attachments/next-states.gif https://github.com/nmartin84/.doom.d/raw/master/attachments/context-tags.gif https://github.com/nmartin84/.doom.d/raw/master/attachments/projects.gif

Yesterday, I was debugging my configuration because of increased init time (0.5-0.8 seconds), then I realized by a coincidence that if I load straight/bootstrap.el manually, and open a new Emacs instance immediately, it starts much more quick (~%65). It is related native comp I guess but I actually still cannot find the reason for this. I checked out the source code of straight.el, spent 4-5 hours and find out that a find process with all the packages I installed as args takes ~1.5 seconds to finish. I disabled it in source code and my startup time decreased from ~2.3s to 0.8s.

source code: https://github.com/KaratasFurkan/.emacs.d#zoom

You can get ideas from init.el, early-init.el and Applying Changes sections of my literate configuration. They are about loading config and keeping org and elisp files synced.