GNU guix is a functional package manager, that can be installed on any distribution and used to manage packages, including emacs packages.
How is this different from straight.el
straight.el is also a functional package manager, but unlike guix, it only manages emacs packages, while with guix you can include external programs that you will make use of from emacs (like ripgrep), emacs
| from krita import * # type: ignore | |
| from time import time | |
| from PyQt5.QtCore import QByteArray | |
| ''' | |
| Pseudo Pixel Perfect (PPP) post-process for Krita: | |
| It removes double pixels (in an L-shaped configuration) | |
| and then thins it using the Zhang-Suen thinning algorithm, | |
| aiming to recreate the feel of a pixel-perfect stabilization brush. |
| #!/usr/bin/env bash | |
| # Download a podcast episode from anchor.fm | |
| # | |
| # Usage: | |
| # grab-anchor-episode "https://anchor.fm/emerge/episodes/Robert-MacNaughton---Learnings-from-the-Life-and-Death-of-the-Integral-Center-e31val" # (m4a example) | |
| # grab-anchor-episode "https://anchor.fm/free-chapel/episodes/Are-You-Still-In-Love-With-Praise--Pastor-Jentezen-Franklin-e19u4i8" # (mp3 example) | |
| # | |
| # anchor.fm serves a list of m4a or mp3 files that need to be concatenated with ffmpeg. | |
| # |
A collection of articles by AngularJS veterans, sometimes even core committers, that explain in detail what's wrong with Angular 1.x, how Angular 2 isn't the future, and why you should avoid the entire thing at all costs unless you want to spend the next few years in hell.
Reason for this: I'm getting tired of having to explain to everyone, chief of which all the indiscriminate Google Kool-Aid™ drinkers, why I have never believed in Angular, why I think it'll publicly fail pretty soon now (a couple years), and why it's a dead end IMO. This gist serves as a quick target I can point people to in order not to have to parrot / compile the core of the articles below everytime. Their compounded reading pretty much captures 99% of my view on the topic.
This page is accessible through http://bit.ly/angular-just-say-no and http://bit.ly/angularjustsayno, btw.
This post also appears on lisper.in.
Reader macros are perhaps not as famous as ordinary macros. While macros are a great way to create your own DSL, reader macros provide even greater flexibility by allowing you to create entirely new syntax on top of Lisp.
Paul Graham explains them very well in [On Lisp][] (Chapter 17, Read-Macros):
The three big moments in a Lisp expression's life are read-time, compile-time, and runtime. Functions are in control at runtime. Macros give us a chance to perform transformations on programs at compile-time. ...read-macros... do their work at read-time.