Feature | Ally | SD | Winner |
---|---|---|---|
Looks | Ally is white, looks modern and sleek, really nice touches with the vents, holo strip, RGB | Sleek and industrial | Ally |
Shape | Hands a bit more pronated, console has more sharp angles, back buttons and middle finger tips are awkward together, 3D printable fix | Feels like an F1 steering wheel, very substantial, fingers wrap around nicely, much better | SD |
Weight | Not much of a difference but can be felt | Heavier but better comfort | - |
Top button positioning | Fingerprint is great, volume buttons are awk | Power button is awk | - |
# I'll be doing another one for Linux, but this one will give you | |
# a pop up notification and sound alert (using the built-in sounds for macOS) | |
# Requires https://github.com/caarlos0/timer to be installed | |
# Mac setup for pomo | |
alias work="timer 60m && terminal-notifier -message 'Pomodoro'\ | |
-title 'Work Timer is up! Take a Break 😊'\ | |
-appIcon '~/Pictures/pumpkin.png'\ | |
-sound Crystal" |
/* License: | |
* Public domain. | |
*/ | |
#include <stdio.h> | |
#include <stdint.h> | |
#include <string.h> | |
#include <unistd.h> | |
#include <errno.h> |
RE: WHEN WILL WEB BROWSERS BE COMPLETE? | |
2020-10-31 02:46PM | |
A follow-up. | |
There has been some great conversation around the opinion piece. Having read all | |
200+ comments on YCombinator and Gist GitHub, I think it's most productive to | |
respond to them all in this follow-up piece. | |
The piece will be structured by looking at what I think are the most relevant | |
critiques and comments, followed by adding context to others' comments, and |
# Stick this in your home directory and point your Global Git config at it by running: | |
# | |
# $ git config --global core.attributesfile ~/.gitattributes | |
# | |
# See https://tekin.co.uk/2020/10/better-git-diff-output-for-ruby-python-elixir-and-more for more details | |
*.c diff=cpp | |
*.h diff=cpp | |
*.c++ diff=cpp | |
*.h++ diff=cpp |
package main | |
import ( | |
"crypto/rand" | |
"crypto/rsa" | |
"crypto/x509" | |
"encoding/pem" | |
"fmt" | |
"log" |
I have a pet project I work on, every now and then. CNoEvil.
The concept is simple enough.
What if, for a moment, we forgot all the rules we know. That we ignore every good idea, and accept all the terrible ones. That nothing is off limits. Can we turn C into a new language? Can we do what Lisp and Forth let the over-eager programmer do, but in C?
This is a quick-and-dirty walkthrough to set up a fresh project with Storybook Docs, Create React App, and TypeScript. If you're looking for a tutorial, please see Design Systems for Developers, which goes into much more depth but does not use Typescript.
The purpose of this walkthrough is a streamlined Typescript / Docs setup that works out of the box, since there are countless permutations and variables which can influence docs features, such as source code display, docgen, and props tables.
npx create-react-app cra-ts --template typescript
TAG_COMMIT := $(shell git rev-list --abbrev-commit --tags --max-count=1) | |
TAG := $(shell git describe --abbrev=0 --tags ${TAG_COMMIT} 2>/dev/null || true) | |
COMMIT := $(shell git rev-parse --short HEAD) | |
DATE := $(shell git log -1 --format=%cd --date=format:"%Y%m%d") | |
VERSION := $(TAG:v%=%) | |
ifneq ($(COMMIT), $(TAG_COMMIT)) | |
VERSION := $(VERSION)-next-$(COMMIT)-$(DATE) | |
endif | |
ifeq $(VERSION,) | |
VERSION := $(COMMIT)-$(DATA) |