What Swift devs can learn from C++
summary
Photoshop on iPad runs the same 31 year old C++ core wrapped in Objective‑C so you see how C++ integrates into a real product, teams tune tight performance by batching work into L1 cache chunks to do ~40 operations per pixel for real‑time sliders, TensorFlow and Apple job listings still require modern C++, and the C++20 committee finally settles two’s‑complement integers. Expect measured community maturity, long tenures, and concrete engineering constraints that affect design, tooling, and hiring.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:59Learning from C++
- 2:05Photoshop for iPad
- 2:51Condolences
- 4:27Domain Driven Design
- 5:11Indirect spark
- 7:00Swift compiler
- 7:20Performance
- 7:38Vectors vs Maps
- 9:23How far away is it?
- 11:19Live rendering complex calculations
- 12:02Customizing for hardware
- 14:33Interconnected history
- 15:57Maturity & kindness
- 17:09Maturity & mentors
- 17:43Maturity & kids
- 21:50Language choice matters
related talks
57mCatching up with Swift
47mTime Traveling With Swift: Where We Started, Where We Are, and Where We’re Going
58mSwift: safety, ergonomics, productivity and legacy preservation
50mTime traveling with Swift
18mScientific Swift
19mUsing C, C++ and Objective C frameworks in Swift apps
47mAn Introduction to the Swift Programming Language
53mSwift: New Paradigms for iOS Development