Matthew Abbott abbottmg

## CollectionViewDataSource.swift
//
//  CollectionViewDataSource.swift
//  Khan Academy
//
//  Created by Andy Matuschak on 10/14/14.
//  Copyright (c) 2014 Khan Academy. All rights reserved.
//

import UIKit

## .perldb
package Ovids::Debugger;

# vim: syntax=perl

=head1 NAME

.perldb - Customize your Perl debugger

=head1 USAGE

## libdispatch-efficiency-tips.md

      
              1 file
            
          
              93 forks
            
          
              12 comments
            
          
              1000 stars
            
          
                tclementdev
                / libdispatch-efficiency-tips.md
            
            
              Last active
              July 12, 2024 03:33
            
              
                Making efficient use of the libdispatch (GCD)
              
          
    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


## Bindings.swift
/*:
 This is a concept re-implementation of the @Binding and @State property wrappers from SwiftUI

 The only purpose of this code is to implement those wrappers myself
   just to understand how they work internally and why they are needed,

 ⚠️ This is not supposed to be a reference implementation nor cover all
      subtleties of the real Binding and State types.
    The only purpose of this playground is to show how re-implementing
      them myself has helped me understand the whole thing better

## udm-pro-he-ipv6-setup.md

      
              1 file
            
          
              1 fork
            
          
              45 comments
            
          
              32 stars
            
          
                bgrewell
                / udm-pro-he-ipv6-setup.md
            
            
              Last active
              July 10, 2024 06:27
            
              
                This gist describes how to setup a hurricane electric (TunnelBroker) IPv6 tunnel on a Ubiquiti Unifi Dream Machine Pro
              
          
    Setup IPv6 Tunnel on Unifi Dream Machine Pro

Enable SSH


TODO

Configure To Dream Machine Over SSH

SSH to your UDM

  
## semantic-layout.html
<!DOCTYPE html>
<html>
<head>
    <meta charset="utf-8" />
    <title>Title</title>
    <link href="stylesheets/main.css" rel="stylesheet" />
</head>
<body>
    <header>
        <hgroup>

## Shape.swift
import Foundation

// Here's a pretty typical scenario where you want to encode a polymorphic type -
// in this case a Shape type that can be either a Square or Circle. Swift provides
// a nice pattern for doing this in a type-safe way using enums:

struct Circle: Codable {
    var radius: Int
}
	//
	// CollectionViewDataSource.swift
	// Khan Academy
	//
	// Created by Andy Matuschak on 10/14/14.
	// Copyright (c) 2014 Khan Academy. All rights reserved.
	//

	import UIKit
	package Ovids::Debugger;

	# vim: syntax=perl

	=head1 NAME

	.perldb - Customize your Perl debugger

	=head1 USAGE
	/*:
	This is a concept re-implementation of the @Binding and @State property wrappers from SwiftUI

	The only purpose of this code is to implement those wrappers myself
	just to understand how they work internally and why they are needed,

	⚠️ This is not supposed to be a reference implementation nor cover all
	subtleties of the real Binding and State types.
	The only purpose of this playground is to show how re-implementing
	them myself has helped me understand the whole thing better
	<!DOCTYPE html>
	<html>
	<head>
	<meta charset="utf-8" />
	<title>Title</title>
	<link href="stylesheets/main.css" rel="stylesheet" />
	</head>
	<body>
	<header>
	<hgroup>
	import Foundation

	// Here's a pretty typical scenario where you want to encode a polymorphic type -
	// in this case a Shape type that can be either a Square or Circle. Swift provides
	// a nice pattern for doing this in a type-safe way using enums:

	struct Circle: Codable {
	var radius: Int
	}