Fatbobman's Swift Weekly #065
Fatbobman's Swift Weekly #065Perspective Shift: Viewing the Developer's Dual Identity Through the Airport Debate
Weekly CommentPerspective Shift: Viewing the Developer's Dual Identity Through the Airport Debate
I spent the weekend catching up with several friends, one of whom is currently involved in managing the construction of a new airport. During our gathering, we had a lively discussion about the future of our city's airports. My city has a unique setup—the existing airport sits in the heart of the urban area, no more than 10 kilometers from any of the main districts. This ideal location has long made travel remarkably convenient for residents. However, this very location has become a constraint on the airport's growth: for the past decade, the airport has been running at full capacity, with little room to open new routes. Meanwhile, dense residential zones surrounding the airport limit its runway classification and potential expansions. The new airport under construction is the largest offshore airport in the world. It promises a higher runway classification, greater operational capacity, and a fully planned airport economic zone, incorporating logistics, warehousing, and other complementary facilities. From a strategic urban development perspective, the significance of this new airport is undoubtedly monumental. Still, despite the fact that the new airport's distance to the city center is noticeably shorter compared to other airports of similar scale, it's undeniably farther out than the current setup—making many frequent flyers uneasy. They look forward to the growth opportunities the new airport could bring, yet they also wish to preserve the old airport's convenience. Ten years ago, when I used to fly dozens of times a year, I absolutely would have supported keeping the old airport. But as my flight frequency has gone down, I now firmly back the government's decision to close the old airport and fully develop the new one. This shift in my perspective has been particularly enlightening. Our perspectives often depend on where we find ourselves. As developers, we hope users will understand a product's shortcomings and grant us time and space to improve it. But when we switch to the user's viewpoint, we naturally expect a flawless product experience. Perhaps this constant role-switching and the resulting collision of perspectives is precisely what drives continuous product improvement and industry advancement. If we, as developers, regularly step into our users' shoes during development, our products will likely become more aligned with user needs, more responsive to their concerns, and ultimately help guide the entire industry toward a better future. Previous Issue｜Newsletter Archive Recent SelectionsUnderstanding _VariadicViewAt WWDC 2024, enhancements to Using Copilot to Write a Raindrop Audio Synthesizer Using AVAudioEngineMatt Gallagher explores the capabilities of VSCode + Copilot through a raindrop audio synthesizer project. The article meticulously documents the entire process, from crafting prompts to optimizing code, and critically evaluates the utility of AI programming assistants. Gallagher highlights Copilot's strengths in working with unfamiliar SDKs, cross-language code migration, and algorithm implementation. However, he also points out significant issues with code quality, including redundancy, lack of abstraction, and poor adaptation to platform-specific requirements. How to Keep Your macOS App's Menu Bar Item Running after Quitting the AppBy default, macOS applications developed with SwiftUI fully terminate upon quitting, including their menu bar items. Pol Piella Abadia shares how to retain a menu bar item even after closing the app's main window. The article details how to use the Swift’s Hidden Gem: Understanding the @retroactive KeywordWith the introduction of SE-0364 in Swift 6, developers may encounter compiler warnings when adding protocol conformances to non-owned types. Using Concurrency Step-by-Step: Stateful SystemsIn the third article of the "Concurrency Step-by-Step" series, Matt Massicotte uses a realistic example to delve into critical aspects of Swift concurrency. He focuses on managing reentrancy and the resulting logical races when using Actors to avoid data races, providing insights and practical strategies for stateful systems in concurrent programming. Getting Started with MongoDB in Swift using MongoKittenMongoDB is a popular NoSQL database that stores data in flexible, JSON-like documents. MongoKitten, developed by Joannis Orlandos, is a pure Swift MongoDB driver built on Swift NIO, offering type-safe queries and 肘子的话视角转换：从机场之争看开发者的双重身份 周末与几位朋友聚会，其中一位正在参与新机场的建设管理工作。席间，大家就新旧机场的去留展开了热烈讨论。 我所在的城市颇具特色 —— 现有机场位于市区中心，与各核心区域的距离都不超过 10 公里。这样得天独厚的地理位置为市民出行带来了极大便利。然而，正是这个位置制约了机场的发展：近十年来，机场一直在满负荷运转，几乎无法开通新航线；同时，由于四周被密集的居民区包围，跑道的飞行区等级也受到限制。 正在建设的 新机场 是全球规模最大的海上机场。它不仅拥有更高的飞行区等级、更大的运营规模，还规划了完整的环机场经济区，涵盖物流、仓储等配套设施。从城市发展的战略高度来看，新机场无疑具有里程碑式的意义。 然而，即便新机场到市中心的距离仍明显短于其他同规模机场，但与现状相比还是让不少经常乘机的市民感到不适应。他们既期待新机场为城市带来的发展机遇，又希望保留旧机场以维持出行便利。 十年前的我，每年都要乘坐至少数十次航班，彼时必定会倾向于保留旧机场。但随着出行频次的减少，我现在则坚定支持政府关闭旧机场、全力发展新机场的政策。这种观点的转变让我深感触动。 人的认知往往会受所处位置的影响。作为开发者，我们希望用户能够理解产品的不足，给予改进的时间和空间；但当我们切换到用户的视角，又渴望获得完美的产品体验。 或许，这种角色转换带来的思维碰撞，恰恰是推动产品持续优化、行业不断进步的重要动力。在开发过程中，如果我们能够经常性地切换视角，站在用户的立场思考问题，相信会让我们的产品更贴近用户需求，更理解用户的抱怨，也让整个行业朝着更好的方向发展。 近期推荐理解 _VariadicView (Understanding _VariadicView)在 WWDC 2024 中， 使用 Copilot 和 AVAudioEngine 编写雨滴音频合成器 (Using Copilot to Write a Raindrop Audio Synthesizer Using AVAudioEngine)Matt Gallagher 通过一个雨滴音频合成器项目，探索了 VSCode + Copilot 在实际开发中的表现。文章详细记录了从提示词编写到代码优化的完整过程，并对 AI 编程助手的实用性进行了深入评估。Gallagher 指出，Copilot 在处理不熟悉的 SDK、跨语言代码迁移和算法实现等方面表现出色，但在代码质量方面仍存在诸多问题，如代码冗余、缺乏抽象以及未能充分适应目标平台特性等。 如何在退出应用后保持 macOS 应用的菜单栏项持续运行 (How to Keep Your macOS App's Menu Bar Item Running after Quitting the App)在默认情况下，基于 SwiftUI 开发的 macOS 应用在退出后会完全关闭，包括其菜单栏图标。Pol Piella Abadia 分享了如何实现应用主窗口关闭后依然保留菜单栏图标的功能。文章详细介绍了通过实现 🪜 理解 @retroactive 关键字 (Swift’s Hidden Gem: Understanding the @retroactive Keyword)在 Swift 6 中，随着 SE-0364 的引入，开发者在为非自有类型添加协议符合性时，可能会遇到编译器警告。这时，可以通过显式使用 并发编程逐步解析：有状态系统 (Concurrency Step-by-Step: Stateful Systems)在 “Concurrency Step-by-Step” 系列的第三篇文章中，Matt Massicotte 通过一个更贴近现实的示例，深入探讨了 Swift 并发编程中的一些细节和注意事项。尤其是当使用 Actor 避免数据竞争时，如何有效处理重入（reentrancy）以及由此引发的逻辑竞态（logical races）。 使用 MongoKitten 在 Swift 中访问 MongoDB (Getting Started with MongoDB in Swift using MongoKitten)MongoDB 是备受欢迎的 NoSQL 数据库，采用灵活的 JSON-like 文档存储数据。MongoKitten 是由 Joannis Orlandos 开发的纯 Swift MongoDB 驱动，基于 Swift NIO 构建，提供了类型安全的查询和 Welcome to my blog Fatbobman's Swift Blog( 肘子的Swift记事本 )
|
