Based on our record, GitHub Pages seems to be a lot more popular than aerc. While we know about 467 links to GitHub Pages, we've tracked only 18 mentions of aerc. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
You have some points, for some I do think it isn't as bad as you write. FWIW, some comments inline. > - You can't subscribe to a single PR/bug/feature-request thread. Subscription to the mailing list is all-or-nothing. And no, setting up email filters is not a reasonable solution. You can use tools like public-inbox or lei, the former is hosted for bigger projects on https://lore.kernel.org/ If you're interested,... - Source: Hacker News / 7 months ago
> Another problem is how badly email threading is displayed in these clients. Email UI is still abysmal. Fair point. However, given that the current alternative is "use another service entirely (e.g. GitHub)", I think it would be fair to assume that devs could choose a good e-mail client and learn how to format such e-mails correctly. It works for Linux, for instance. I started using Aerc, and I love it:... - Source: Hacker News / 9 months ago
For fans of Mutt/NeoMutt looking to try something new, I've been getting a lot of mileage out of Aerc[1] and can recommend it as a somewhat more approachable alternative for the Mutt-curious. [1] https://aerc-mail.org/. - Source: Hacker News / over 1 year ago
Try aerc, I recently set it up and it was really easy to do. The only tricky part was making it so my password is read from the KDE wallet instead of being stored as plain text in the config file. Source: over 1 year ago
I'm not sure how much longer, but at least for me aerc still works with Outlook e-mails. Source: over 1 year ago
You can deploy to Github Pages in under 2 minutes by following their documentation. - Source: dev.to / 4 days ago
For this application, Elm controlled the routing. So, I had to adapt the scripts to deploy to Netlify instead of GitHub Pages. Why? Because you need to be able to tell the web server to redirect all relevant requests to the application. GitHub Pages doesn't have support for it. - Source: dev.to / 23 days ago
It's super easy to publish a static site like the resume with GitHub Pages. Just check out the docs. - Source: dev.to / about 1 month ago
GitHub Pages: Host your static websites directly from your GitHub repository. - Source: dev.to / 3 months ago
As per many other comments, it sounds like a static site generator like Hugo (https://gohugo.io/) or Jekyll (https://jekyllrb.com/), hosted on GitHub Pages (https://pages.github.com/) or GitLab Pages (https://about.gitlab.com/stages-devops-lifecycle/pages/), would be a good match. If you set up GitHub Actions or GitLab CI/CD to do the build and deploy (see e.g.... - Source: Hacker News / 3 months ago
Mu4e - Starting with version 0.9.8, mu provides an emacs-based e-mail client which uses mu as its back-end: mu4e.
Vercel - Vercel is the platform for frontend developers, providing the speed and reliability innovators need to create at the moment of inspiration.
Mutt - Mutt is a small but very powerful text-based mail client for Unix operating systems.
Jekyll - Jekyll is a simple, blog aware, static site generator.
NeoMutt - NeoMutt is a command-line mail reader. It's a version of https://alternativeto.
Netlify - Build, deploy and host your static site or app with a drag and drop interface and automatic delpoys from GitHub or Bitbucket