"When I started learning Emacs, my dad gave me his .emacs file. (That's what we used back in ye olden days instead of .emacs.d/init.el and stuff.) I used it without modification for many years. Eventually I learned how to write my own functions and customizations. This package aims to give other users a similar experience. When someone comes to me and expresses their desire to learn Emacs, I can point them at this to help them get over the initial hump, but not coddle them so much that they're afraid or unable to change things to their liking."
I feel the same way. I don't like or dislike Stallman, and certainly disagree with him on a lot of stuff, but I can appreciate what he stands for and for GNU in general.
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.
I'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.
Comments
Very nice presentation and project.
From the README of the linked repo:
"When I started learning Emacs, my dad gave me his .emacs file. (That's what we used back in ye olden days instead of .emacs.d/init.el and stuff.) I used it without modification for many years. Eventually I learned how to write my own functions and customizations. This package aims to give other users a similar experience. When someone comes to me and expresses their desire to learn Emacs, I can point them at this to help them get over the initial hump, but not coddle them so much that they're afraid or unable to change things to their liking."
I distinctly remember my dad telling my "my .emacs file is older than you are." I'm 41!
People attack Stallman for some things but I guess I'm happy GNU exists and Emacs might be the most visible example
I feel the same way. I don't like or dislike Stallman, and certainly disagree with him on a lot of stuff, but I can appreciate what he stands for and for GNU in general.
Come to think about it, if I wanted a write-once-run-forever-language, Elisp would be the ultimate language to do so...
Holy Batman... You folks are all, literally XKCD 297!
https://xkcd.com/297/ (Lisp Cycles)
I'm still using .emacs today! and I have all my elpaca and the fancy pants stuff in it
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.
I'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.