chockenberry

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>NSPrivacyAccessedAPITypes</key>
	<array>
		<dict>
			<key>NSPrivacyAccessedAPITypeReasons</key>
			<array>
				<string>CA92.1</string>

ole

#!/bin/zsh

# Test if the Swift compiler knows about a particular language feature.
#
# Usage:
#
#     swift-has-feature [--swift SWIFT_PATH] [--language-version LANGUAGE_VERSION] FEATURE
#
# The feature should be an upcoming or experimental language feature,
# such as `"StrictConcurrency"` or `"ExistentialAny"`.

Sherlouk

//
// DebugDevice.swift
//
// Copyright 2022 • Sidetrack Tech Limited
//

import Foundation

// This must be called on the main-thread.
var isDebugProfileInstalled: Bool {

JunyuKuang

let overrideCatalystScaleFactor: Void = {
    guard let sceneViewClass = NSClassFromString("UINSSceneView") as? NSObject.Type else {
        return
    }
    if sceneViewClass.instancesRespond(to: NSSelectorFromString("scaleFactor")) {
        // old
        swizzleInstanceMethod(
            class: sceneViewClass,
            originalSelector: NSSelectorFromString("scaleFactor"),
            swizzledSelector: #selector(swizzle_scaleFactor)

DakotaLMartinez

You need to do this if you try this command:

ssh -T git@github.com

and you get something that says

git@github.com: Permission denied (public key).

diamantidis

activate application "SF Symbols"

tell application "System Events"
    tell process "SF Symbols"

        -- Click the “list” radio button.
        click radio button 2 of radio group 1 of group 3 of toolbar 1 of window 0

        tell outline 1 of scroll area 1 of splitter group 1 of window 0
            select (row 1 where value of static text 1 of UI element 1 starts with "All")

ethanhuang13

//
//  FacebookAuth.swift
//  GitHub: ethanhuang13
//  Twitter: @ethanhuang13

import AuthenticationServices
import SafariServices

/*
 Updated: 

stefanceriu

//
//  UINSSceneView+CTX.h
//  EFClass
//
//  Created by Stefan Ceriu on 28/11/2019.
//  Copyright © 2019 EF Education First. All rights reserved.
//

#import <Foundation/Foundation.h>

iKenndac

Hello,

I attended WWDC this year, and overall it was a fantastic experience. I would, however, like to give some feedback on one particular aspect of the conference.

Before I begin, I understand that it would be easy to brush off my feedback as coming from just some grumpy English guy, but I genuinely believe this is important feedback. Please do read until the end.

I would like to ask that the cheering, whooping, clapping and hollering by conference staff is toned down.

I'm a person that would describe myself as "slightly introverted". I cannot begin to describe how deeply uncomfortable it was to walk into the registration room on Sunday to multiple employees cheering and clapping at me, trying to give me high fives. I understand the want to make people excited, but this needs to have its limits. During the conference, I got cheered and high-fived pretty much the entire week for things like:

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