3 ms·
I love Elpaca! The built-in package management story has gotten so much better in the past 10 years, but Elpaca is so, so good. My personal config is kinda the
by ashton314 25d ago
I love Elpaca! The built-in package management story has gotten so much better in the past 10 years, but Elpaca is so, so good. My personal config is kinda the antithesis of Bedrock—it's bloated, slow, and uses over 100 packages. Elpaca handles installing/updating/managing those like a charm, however.
I kept Elpaca out of Bedrock because I wanted a strictly built-ins-first experience, but if anyone asks what I use when they outgrow package.el, Elpaca is my first and only recommendation.
- sph 24d agoI've done use-package, straight, quelpa, tried elpaca a few years back when the hype grew and it was a buggy mess, back to use-package when it was merged into core. I'm tired boss. There's a little too much churn I feel these days. I dislike the default package management system, but until a better one is merged into core, I'll keep updating my packages manually once a year when I remember.
- ashton314 20d agoExhaustion very understandable. Elpaca is nice and stable now, and the integration with use-package is fabulous. But if the built-in is working for you, no need to change it. Now that use-package supports the :vc keyword, there’s imo much less of a compelling reason to use Elpaca and the like.