Ah, fellow Butterick fonts enjoyer—Butterick's fonts have spoiled me: compared to pretty much every other professional font I've seen, they're the cheapest and most conveniently licensed fonts out there.
Someone has already mentioned Matthew Butterick's fonts and his online "book" Practical Typography [1]—absolutely fantastic material there.
Some concrete suggestions from me:
- Fira Sans [2] is a lovely, legible sans-serif font that's free and incredibly easy-to-read. This would make a fine body font.
- Source Sans [3] is another good sans-serif that might be closer to your current font. It's about as readable as Fira, but it's a little less warm imo.
- Make your line length a little narrower and your line spacing (i.e. leading) just a hair wider—that will do wonders for readability.
Definitely check out Practical Typography for more tips from a real professional.
Hey! I'm doing great, thanks. Kimball's class was a lot of fun. Nice you "see" you again. (Can't tell who you are by your username—feel free to email me at the address on my blog if you want.)
No shade on wgrep, mind you—I used that for a long time and it's been one of my favorite tools. But now I just… don't need it. It's so nice being able to do consult-ripgrep -> export results to a buffer -> change to edit mode -> search-and-replace project-wide.
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.
Exhaustion 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.
Every Emacs user eventually finds their rock bottom, er, Bedrock :D
Kidding kidding... Cool project, thanks for sharing and kind of validating the stuff I ended up doing [0]. Hooray, use-package! That meandering (floundering?) culminated in my Emacs, which is a single `init.el file` (hooray, use-package): https://github.com/adityaathalye/dotemacs
[0] The blow-by-blow of which is documented in this excessively long blog post series I ended up writing as I was..., well, the title says it all;
The linked post is the first in the series, and it enumerates what features / capabilities I was going for, and the key references I used while figuring out the configuration, from scratch.
Julia is my go-to when I need a fast language that I can reason about in a functional way. The type system is fine, the pattern matching is pretty darn good, the metaprogramming story could be significantly better but it’s not bad and boy howdy it’s fast. So stinking fast.
CeTZ is a really good package, but I still reach for a tool like Omnigraffle if I need to make a really complicated diagram.
reply