At the time of this writing Divvy hasn't been updated for OS X 10.9 so it tries to direct you to the Accessibility panel of the System Preferences. Actually the assistive device settings have been moved to the Security pane as shown below:
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <?xml version="1.0"?> | |
| <!-- Key Mappimgs for http://pqrs.org/macosx/keyremap4macbook/ --> | |
| <root> | |
| <item> | |
| <name>German Umlaute on US Keyboard Layout with ALT modifier</name> | |
| <appendix>Change Option+o to ö</appendix> | |
| <appendix>Change Option+a to ä</appendix> | |
| <appendix>Change Option+u to ü</appendix> | |
| <identifier>remap.org.openhort.german_umlaute_with_ALT_modifier</identifier> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| const calculate = (n, k) => { | |
| const exponent = (-k * (k - 1)) / (2 * n) | |
| return 1 - Math.E ** exponent | |
| } | |
| // where `n` is the number of possible unique hashes | |
| // where `k` is the number of values created | |
| // calculate(100000, 25) => 0.0029955044966269995 aka 0.29% chance of collision |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /** | |
| * Two column <dl> with two lines of CSS! Thank you Grid Layout! | |
| * Limitation: Breaks if we have multiple consecutive <dt>s or <dd>s | |
| */ | |
| dl { | |
| display: grid; | |
| grid-template: auto / 10em 1fr; | |
| } |
Figuring out how Next.js handles code splitting and routing so that we can decide if it fits our needs or if we can take inspiration from it for our own internal solution.
There is no special documentation about Next.js SSR, since it's supported out of the box and handled transparently.
