brennanMKE

Using UIWindowScene and UIWindow with SwiftUI to Create a Debugging Window

This tutorial explains the relationship between UIWindowScene, UIWindow, and UIScene, and shows how to create a secondary debug window using SwiftUI inside a UIKit-hosted UIWindow. This is especially useful for developers working on internal tools or debugging overlays for iOS, iPadOS, or visionOS apps.

---

Overview

Apple's scene-based lifecycle (introduced in iOS 13) allows multiple UI scenes per app. Each scene is an instance of UIScene, and for UIKit-based apps, it takes the form of a UIWindowScene. Each UIWindowScene can own multiple UIWindow instances.

brennanMKE

🧠 Distinction: Thrown Errors (Swift) vs Exceptions (Other Languages)

✅ Swift: Thrown Errors

• Swift’s throw/try/catch is designed for predictable, recoverable errors.

• Swift requires explicit syntax:

  • func foo() throws
  • try foo()

• do { try foo() } catch { ... }

brennanMKE

✅ Debugging Memory Leaks with LLDB

🔍 1. Inspect What Is at a Given Memory Address

Yes — if you have a memory address from a leak report, LLDB can tell you what object it points to:

memory read --format x --size 8 --count 1 0xADDRESS

brennanMKE

🔧 Sponsor Access Protocol – Revised Access Model

✅ Overview

Each sponsor token grants access rights based on a defined access type, including:

Access Type	Description
timed	Fixed expiration (e.g., 7 days from claim)
day_pass	Each use activates 24-hour access; multiple passes can be held

brennanMKE

✅ Swift 6 Study Notes — any, some, Existentials, Boxing, Dispatch

(via ChatGPT)

🧱 any vs some — Existential vs Opaque Types

any Protocol

• Existential type: Can hold a value of any type that conforms to the protocol.
• Requires heap allocation (boxing).
• Uses dynamic dispatch via a witness table.

brennanMKE

Tailscale and WireGuard

(via ChatGPT)

🔧 Overview: Platform Features Supporting WireGuard & Tailscale

Modern OSes like macOS, Linux, Windows, and iOS have built-in support for networking features that make tools like WireGuard and Tailscale work smoothly:

💡 Core Platform Features Used

| Feature | Description | Used By |

brennanMKE

What sending enforces

Using sending tells the compiler:

• This value will be consumed by a concurrent context (e.g., a task).
• It must not be accessed again from the current task.
• If it is accessed again (e.g., reused or mutated), the compiler will raise an error.

In the code below, it enforces running the operation once. Using it in the 2nd Task causes a compiler error.

brennanMKE

🛠 Getting Started with Tailscale: A Practical Guide

(via ChatGPT)

✨ Overview

This guide will help you set up Tailscale to:

• Connect multiple Macs at home
• Remotely manage Raspberry Pis in other networks

brennanMKE

import Foundation

let fizzValue = "Fizz"
let buzzValue = "Buzz"
let fizzBuzzValue = "FizzBuzz"
let emptyValue = ""

enum FizzBuzz: String {
    case fizz = "Fizz"
    case buzz = "Buzz"

brennanMKE

Swift Arrays, Sequences, and Performance Optimizations

(via ChatGPT)

Overview

Swift provides powerful collection types, with Array and Sequence being fundamental. This document explores their differences, best practices, and common pitfalls, including Copy-on-Write (CoW), stride, and Lazy Sequences.

---

Sequence vs. Collection vs. Array