magicdude4eva

Add the following in .zshrc:

...
plugins=(osx git zsh-autosuggestions zsh-syntax-highlighting zsh-nvm docker kubectl)
...

### Fix slowness of pastes with zsh-syntax-highlighting.zsh
pasteinit() {
  OLD_SELF_INSERT=${${(s.:.)widgets[self-insert]}[2,3]}
  zle -N self-insert url-quote-magic # I wonder if you'd need `.url-quote-magic`?

tclementdev

libdispatch efficiency tips

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

lattner

Swift Concurrency Manifesto

Author: Chris Lattner

Chinese Translation by Jason Yu

Contents

• Introduction
• Overall Vision

myell0w

import Foundation
import UIKit


/// Used to create a layout guide that pins to the top of the keyboard
final class KeyboardLayoutGuide {

    private let notificationCenter: NotificationCenter
    private let bottomConstraint: NSLayoutConstraint

scturtle

import pyautogui

# constants
O, R, B = -1, 1, 0
width = 50

# global variables
topy, topx = None, None
mat = []

pythonesque

use list::Node;

mod list {
    use std::mem;

    #[derive(Show)]    
    pub struct Node<T> {
        pub data: T,
        prev: Option<Box<Node<T>>>,
        next: Option<Box<Node<T>>>

bzerangue

Verify and Repair Disk Permissions via Terminal (Mac OS X)

Verify Permissions

diskutil verifyPermissions /

Repair Permissions

diskutil repairPermissions /

src.c

#include "/usr/include/stdio.h"
#include "/usr/include/unistd.h"
#define optind 0,*argv="flag"
#include "/usr/src/linux-headers-3.13.0-30/scripts/unifdef.c"

nicklockwood

Hacking UIView animation blocks for fun and profit

In this article, I'm going to explore a way that we can create views that implement custom Core Animation property animations in a natural way.

As we know, layers in iOS come in two flavours: Backing layers and hosted layers. The only difference between them is that the view acts as the layer delegate for its backing layer, but not for any hosted sublayers.

In order to implement the UIView transactional animation blocks, UIView disables all animations by default and then re-enables them individually as required. It does this using the actionForLayer:forKey: method.

Somewhat strangely, UIView doesn't enable animations for every property that CALayer does by default. A notable example is the layer.contents property, which is animatable by default for a hosted layer, but cannot be animated using a UIView animation block.

randomsequence

@implementation CIContext (IntermediateImage)

- (CIImage *)rsq_renderToIntermediateImage:(CIImage *)image {
    CIImage *intermediateImage = nil;
    CGSize size = image.extent.size;
    CVPixelBufferRef pixelBuffer = NULL;
    CVReturn status = CVPixelBufferCreate(kCFAllocatorDefault,
                                          size.width,
                                          size.height,
                                          kCVPixelFormatType_32ARGB,