From: Ryan Prior <ryanprior@hey.com>
To: Development of GNU Guix and the GNU System distribution
<guix-devel@gnu.org>,
Hartmut Goebel <h.goebel@crazy-compilers.com>
Subject: Re: Discover GNU Guix eco-system with awesome-guix!
Date: Sun, 14 Feb 2021 00:27:02 +0000 [thread overview]
Message-ID: <58d4dec98d3a8719b08a6180f5ced51ebff3851c@hey.com> (raw)
In-Reply-To: <b9932666-29e9-c516-e79e-683c865aac4a@crazy-compilers.com>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
On February 13, 2021, Hartmut Goebel <h.goebel@crazy-compilers.com>
wrote:
> Am 09.02.21 um 17:16 schrieb Léo Le Bouter:
> > Commonly awesome lists are used to share links to all things related
> to
> > some topic or some software
>
> I wonder why not just calling it "Link list" then? [This] would be
> much
> easier to understand for non-nerds.
Awesome lists are "a thing." A number of people maintain "awesome
awesome" lists, which list other pages with "awesome lists." The best
known of these "awesome awesomes" is
https://github.com/sindresorhus/awesome which has over 152,000 stars and
19,900 forks on GitHub and almost a thousand commits.
For my fellow recursion enjoyers, there's also an "awesome awesome
awesome" list which lists these lists of lists:
https://github.com/t3chnoboy/awesome-awesome-awesome
So, while saying "link list" is fine and understandable, there are many
people who specifically create and seek out "awesome lists" and find it
easier to share and discover such lists under the less generic name.
Ryan
[-- Attachment #2: Type: text/html, Size: 3468 bytes --]
next prev parent reply other threads:[~2021-02-14 0:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 11:19 Discover GNU Guix eco-system with awesome-guix! Léo Le Bouter
2021-02-09 11:56 ` zimoun
2021-02-09 14:19 ` Tobias Geerinckx-Rice
2021-02-09 16:19 ` Léo Le Bouter
2021-02-09 16:16 ` Léo Le Bouter
2021-02-09 17:51 ` zimoun
2021-02-09 18:11 ` Bonface Munyoki K.
2021-02-09 18:25 ` zimoun
2021-02-13 11:32 ` Hartmut Goebel
2021-02-14 0:27 ` Ryan Prior [this message]
2021-02-10 22:03 ` Ludovic Courtès
2021-02-10 22:55 ` Léo Le Bouter
2021-02-10 22:58 ` Léo Le Bouter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58d4dec98d3a8719b08a6180f5ced51ebff3851c@hey.com \
--to=ryanprior@hey.com \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).