-
enable bbrplus on debian 9 and above
git clone https://github.com/Xaster/bbrplus-debian.git cd bbrplus-debian # run as root make && make install sysctl -w net.core.default_qdisc=fq
sysctl -w net.ipv4.tcp_congestion_control=bbrplus
.kanban-board { | |
background-color: #fff; | |
} | |
.kanban-card { | |
background-color: white; | |
margin: 8px; | |
box-shadow: 0px 1px 2px #9EB3C0; | |
padding: 10px; | |
border-radius: 2px; |
enable bbrplus on debian 9 and above
git clone https://github.com/Xaster/bbrplus-debian.git
cd bbrplus-debian
# run as root
make && make install
sysctl -w net.core.default_qdisc=fq
sysctl -w net.ipv4.tcp_congestion_control=bbrplus
import { BleManager } from 'react-native-ble-plx'; | |
var Buffer = require('buffer').Buffer; | |
const SERVICE_ID = '0000fefb-0000-1000-8000-00805f9b34fb'; | |
const DATA_TXCH_ID = '00000002-0000-1000-8000-008025000000'; | |
const DATA_RXCH_ID = '00000001-0000-1000-8000-008025000000'; | |
const CREDITS_TXCH_ID = '00000004-0000-1000-8000-008025000000'; | |
const CREDITS_RXCH_ID = '00000003-0000-1000-8000-008025000000'; | |
const MAX_PAYLOAD_SIZE = 240; |
Read this first: http://akrl.sdf.org/gccemacs.html
For that you need to compile gcc (duh). I edited Homebrew's gcc formula:
/* characteristic.js | |
* A simple custom BLE peripheral characteristic for use with Node.js and bleno. | |
* This characteristic supports read, write, and notify properties. | |
* Julian Hays - 10/14/19 | |
*/ | |
var util = require('util'); | |
var bleno = require('bleno-mac'); //or 'bleno-mac' if you are using that | |
var BlenoCharacteristic = bleno.Characteristic; |
;;; package --- Fix permissions for Emacs.app on macOS Catalina | |
;;; Author: Artem Loenko | |
;;; Mail-To: <[email protected]> | |
;;; Commentary: | |
;;; Code: | |
(defconst _default-emacs-app-plist-path "/Applications/Emacs.app/Contents/Info.plist") | |
(defconst _temp-buffer-name "*fixing Emacs permissions*") | |
(defconst _temp-buffer (get-buffer-create _temp-buffer-name)) | |
(with-current-buffer _temp-buffer (erase-buffer)) |
I heard some points of criticism to how React deals with reactivity and it's focus on "purity". It's interesting because there are really two approaches evolving. There's a mutable + change tracking approach and there's an immutability + referential equality testing approach. It's difficult to mix and match them when you build new features on top. So that's why React has been pushing a bit harder on immutability lately to be able to build on top of it. Both have various tradeoffs but others are doing good research in other areas, so we've decided to focus on this direction and see where it leads us.
I did want to address a few points that I didn't see get enough consideration around the tradeoffs. So here's a small brain dump.
"Compiled output results in smaller apps" - E.g. Svelte apps start smaller but the compiler output is 3-4x larger per component than the equivalent VDOM approach. This is mostly due to the code that is usually shared in the VDOM "VM" needs to be inlined into each component. The tr
# Please see the script's new home: https://github.com/alphapapa/magit.sh |
@echo off | |
REM Make sure that the path to the script is correct! | |
@bash -l -c "~/bin/gitkraken-wsl-bash.sh %*" |