225 private links
Get people to start their own websites as easily as possible.
At the time of writing, it is a great work in progress.
A backend compiler and an alternative of LLVM
A list of what to do after reading the rust book
Critics of Git, if someone had to improve from its weaknesses.
sha1 was a bad choice back then. The moral here is "treat your identifiers as opaque strings" along with "sometimes a sha1: prefix doesn't hurt anyone"
Email and names in every commits:
I guess when you read lkml, the notion of spam isn't too worrying, but putting names and emails into every commit means any time someone changes name or email, they might as well be a whole different person to the repo.
Sure enough, when you store names in the files, you have to rewrite history when someone changes email address, but in another world, you'd use a UUID and a file called .gitauthors that maps one to the other
There are two different mechanisms for almost every feature.
git forces you to make a choice. use merge and get a noisy, but representative history. use rebases and lose some of the work, but the log is a lot easier to navigate.
we could also have a version of git log that didn't make merges look like shit, but that's another problem altogether.
the unix philosophy is about building toolkits, not applications
in other words: have you ever accidentally committed inside a rebase? or accidentally committed a conflict? tough shit, fucko.
git commands are named after implementation, not use, and there's absolutely no excuse for it
flat files kind of suck if your state gets corrupted.
git is made from papercuts
there's bits where you can't check in an empty directory, or how you can set files to ignore but not files to include.
Examples of relevant class names.
A consistent set of design tokens already defined
It handles CSS grid and flexbox
A project to list all email issues.
The state of the art CSS parser and minifier.
This tool is used by Mozilla for Firefox.
Each theme provides an accent, special, and neutral palette with 6 tints and 6 shades for a total of 13 generated colors each. Some themes use preset hues for each color, and others are generated based on color-theory.
A dark mode with an invert option is provided.
It spots files that does not follow the XDG specifications.
To solve XDG misconfiguration, if wanted.
A Jupyter notebook demo style for JS.
blog-cells can turn any web page into an interactive code notebook, similar to Jupyter notebooks, but powered by JavaScript and running entirely in the browser.
There's no server-side component, so you can share your notebooks on static site hosts like GitHub pages. Check out the source for this page here.
Check it out https://github.com/rameshvarun/blog-cells
Impressive! There are a lot of system stuff projects or JS
The tool install binaries directly. It can be especially useful for CI (or maybe Raspberry Pi).