| 13:15 <xQuasar> | HASKELL IS FOR FUCKIN FAGGOTS. YOU'RE ALL A BUNCH OF | |
| | FUCKIN PUSSIES | |
| 13:15 <xQuasar> | JAVASCRIPT FOR LIFE FAGS | |
| 13:16 <luite> | hello | |
| 13:16 <ChongLi> | somebody has a mental illness! | |
| 13:16 <merijn> | Wow...I suddenly see the error of my ways and feel | |
| | compelled to write Node.js! | |
| 13:16 <genisage> | hi | |
| 13:16 <luite> | you might be pleased to learn that you can compile | |
| | haskell to javascript now |
| -480p - Run tenfoot in 480p rather than 1080p | |
| -720p - Run tenfoot in 720p rather than 1080p | |
| -accesscode - | |
| -all_languages - show longest loc string from any language | |
| -batterytestmode - rapidly cycle battery percentages for testing | |
| -bigpicture - Start in Steam Big Picture mode | |
| -blefw - | |
| -cafeapplaunch - Launch apps in a cyber cafe context | |
| -candidates - Show libjingle candidates for local connection as they are processed | |
| -ccsyntax - Spew details about the localized strings we load |
| /** | |
| * USB HID Keyboard scan codes as per USB spec 1.11 | |
| * plus some additional codes | |
| * | |
| * Created by MightyPork, 2016 | |
| * Public domain | |
| * | |
| * Adapted from: | |
| * https://source.android.com/devices/input/keyboard-devices.html | |
| */ |
| cmake_minimum_required(VERSION 2.8) | |
| set(CMAKE_LEGACY_CYGWIN_WIN32 0) | |
| project(ReaderModeExample) | |
| if(MSVC) | |
| add_compile_options("/MP") | |
| endif() | |
| add_executable(ReaderModeExample WIN32 | |
| ReaderModeExample.c |
| In https://github.com/ekmett/lens/wiki/Derivation, we see some types for | |
| composition of compositions: (.).(.), (.).(.).(.), and so on. Let's prove that | |
| the type of (.).(.) is (a -> b) -> (c -> d -> a) -> c -> d -> b, as stated in | |
| the site. We'll stick with prefix notation, meaning that we want the type of | |
| (.)(.)(.). | |
| Recall the type of composition. This should be intuitive: | |
| (.) :: (b -> c) -> (a -> b) -> a -> c [1] |
This document contains some ideas for additions to the Nix language.
The Nix package manager, Nixpkgs and NixOS currently have several problems:
enableFoo, but there is no way for the Nix
UI to discover them, let alone to provide programmatic ways to
The libdispatch is one of the most misused API due to the way it was presented to us when it was introduced and for many years after that, and due to the confusing documentation and API. This page is a compilation of important things to know if you're going to use this library. Many references are available at the end of this document pointing to comments from Apple's very own libdispatch maintainer (Pierre Habouzit).
My take-aways are:
You should create very few, long-lived, well-defined queues. These queues should be seen as execution contexts in your program (gui, background work, ...) that benefit from executing in parallel. An important thing to note is that if these queues are all active at once, you will get as many threads running. In most apps, you probably do not need to create more than 3 or 4 queues.
Go serial first, and as you find performance bottle necks, measure why, and if concurrency helps, apply with care, always validating under system pressure. Reuse
