每日新聞摘要

This article explains how Hibernate's proxy mechanism interacts with inheritance and why lazy-loaded associations can be proxied to the declared base type instead of the actual subclass. Using a simple HogwartsHouse/Gryffindor/Slytherin example, it shows that a lazily fetched association typed as the base class produces a proxy that fails instanceof and casting checks for subclass-specific properties. One workaround—unproxying—forces initialization and defeats lazy loading. Hibernate 6.6 introduced @ConcreteProxy: annotating the abstract base prompts Hibernate to inspect the discriminator column and create a proxy typed to the concrete subclass, allowing safe casts and access to subclass fields. The trade-off is a slightly slower query when resolving the concrete type. Examples and code are provided for setting up dependencies and entities.

文章通过 HogwartsHouse/Gryffindor/Slytherin 的示例，说明在 Hibernate 的继承关系中，延迟加载时生成的代理会使用声明的关联类型而非实际子类，导致对子类进行 instanceof 检查或强制转换失败。虽然可通过 unproxy 强制获取真实实体，但会初始化代理，违背延迟加载目的。Hibernate 自 6.6.0 起提供 @ConcreteProxy，标注在抽象基类后，Hibernate 会在延迟加载时检查 discriminator 列以识别实际子类，并生成对应子类类型的代理，允许安全转换和访问子类特有属性，但解析步骤会略微降低查询性能。

This article explains why java.io.NotSerializableException occurs and how to resolve it. The exception is raised when the Java runtime tries to serialize an object graph that includes a class not implementing java.io.Serializable. Problems frequently stem from nested objects or runtime-managed third-party instances rather than the root object. The tutorial demonstrates with examples (User/Address and AuditContext) and shows three practical approaches: make nested classes Serializable when their state must persist; declare non-persisted or runtime-only fields transient; or extract and store only the serializable parts (for example, copying a traceId from a third-party AuditContext). The piece emphasizes that successful serialization requires every referenced object to be serializable or explicitly excluded, and recommends choosing the approach based on whether the field represents persistent state or ephemeral runtime context.

本文介绍了导致 java.io.NotSerializableException 的常见情形及对应修复措施。Java 在序列化时会遍历完整对象图，若其中任何类未实现 Serializable 就会失败。问题通常源于嵌套对象（如 Address）或第三方运行时对象（如 AuditContext），而非顶层对象。作者通过示例说明三种处理方式：当需要持久化时为类实现 Serializable；对于仅在运行时使用的字段将其标记为 transient；或从外部对象中提取并保存可序列化的数据（例如 traceId）。文章强调应根据字段是否需持久化选择方案，以确保稳定可靠的序列化。

This installment outlines practical guidance for creating a professional Jetpack Compose development workflow, with emphasis on tooling and testing for modern Android applications. It highlights the role of inspection tools like the Layout Inspector to examine and debug UI, and presents visual regression as a technique to detect unintended visual changes. The article stresses combining these capabilities with automated testing and repeatable processes so teams can iterate quickly with confident feedback. Rather than deep-dive code samples, it surveys Compose-oriented practices and encourages a systematic approach that improves reliability, reduces regressions, and helps scale Compose development from exploratory work to production-ready delivery.

本系列第八部分提供实践性建议，聚焦为 Jetpack Compose 建立专业开发工作流程的工具与测试方法。文章以 Layout Inspector 展示 UI 检查与调试的重要性，并提出视觉回归作为检测界面意外变动的手段。强调将这些工具与自动化测试、视觉基线比对和检视流程结合，形成可重复且可维护的步骤，帮助团队在开发中获得快速反馈并降低回归风险。总体上鼓励以系统化流程把 Compose 从探索阶段推进到可规模化、质量稳定的交付。

This article examines how to control “real world” interactions in Jetpack Compose by using side‑effect APIs and coroutines in a lifecycle‑aware way. It explains LaunchedEffect for running suspending work scoped to a composable, and how keys affect when effects restart. DisposableEffect is described as the mechanism to perform setup and ensure cleanup when a composable leaves the composition. The piece also reviews patterns for launching and cancelling coroutines safely, coordinating work with rememberCoroutineScope or structured concurrency, and avoiding common pitfalls such as leaking jobs across recompositions. Overall, it presents practical guidance for integrating asynchronous work and lifecycle management in a declarative UI.

本文探討如何在 Jetpack Compose 中利用副作用 API 和協程，以生命週期為導向地控制與外部系統或長時間任務的互動。文章闡述 LaunchedEffect 用來在組件存在期間執行掛起函數並根據 keys 決定何時重新啟動，而 DisposableEffect 提供了在組件退出時執行清理的機制。作者還討論了使用 rememberCoroutineScope、結構化併發等模式來啟動與取消協程的實務，並提醒如何避免在重組或生命週期變化時洩漏任務，給出整合非同步作業與生命週期管理的具體建議。

This Medium post by Vivek Yadav, titled "How to Implement Lottie Animations in Jetpack Compose," highlights that animations play a crucial role in enhancing user experience. The article centers on integrating Lottie—an animation library—within Jetpack Compose, Android's modern UI toolkit. It emphasizes the value of thoughtful animation to improve usability and visual feedback, and points readers to Medium for the complete discussion. The full Medium article contains the detailed presentation of the topic; readers who wish to apply animated assets in Compose UIs are encouraged to consult the original post for full guidance, sample code, and demonstration of Lottie integration specifics.

本文为 Vivek Yadav 在 Medium 发表的文章《How to Implement Lottie Animations in Jetpack Compose》，指出动画在提升用户体验上的关键角色。文章以 Lottie 与 Jetpack Compose 为主题，说明在 Compose 界面中导入动画的重要性与应用面向。欲取得完整实现细节、代码示例或演示，请参考 Medium 上的原文链接继续阅读。

This piece introduces the challenge of building whitelabel mobile applications using Kotlin Multiplatform and emphasizes that success goes beyond simply sharing business logic. It frames Kotlin Multiplatform as a means to centralize common functionality while noting teams must still handle platform-specific integration points, customization, configuration, and release practices. The article treats these topics as high-level considerations rather than a step-by-step tutorial, calling attention to architecture decisions, trade-offs between reuse and platform fidelity, and strategies such as configuration and feature toggles to manage multiple branded variants. Readers are encouraged to consult the full Medium post for concrete examples and implementation details.

本文从高层介绍了使用 Kotlin Multiplatform 构建白标（whitelabel）应用的关键议题，强调成功不仅在于共享业务逻辑，还需妥善处理平台特有的集成点、界面与配置、测试与发布流程。文章将這些視為設計與架構上的重要考量，讨论在代码复用与平台体验一致性之间的权衡，并建议通过明确配置与功能开关来管理多个品牌变体。文章以概念性说明为主，并建议读者查看完整 Medium 帖文以获取具体实现细节。

This article by Tung Doan presents a complete professional guide to optimizing HashMap and Set performance in Android Kotlin. It focuses on advanced optimization techniques, practical trade-offs between time and memory, and how to apply these techniques in real-world Android applications. The piece emphasizes profiling and measurement as the basis for optimization decisions, and offers a decision matrix to help developers choose the appropriate collection types and tuning strategies for different use cases. While the article is hosted on ProAndroidDev and includes deeper examples and guidance in the full post, the core message is to combine empirical profiling with a set of proven optimization patterns and best practices when working with HashMap and Set in Kotlin on Android.

Tung Doan 在 ProAndroidDev 上发表的这篇文章，提供了一份针对 Android Kotlin 中 HashMap 与 Set 的完整专业性能优化指南。文章以性能分析和量测为出发点，介绍进阶优化方法、时间与内存的权衡，并说明在不同使用场景下如何选择合适的集合类型与调优策略。文中还整理出一个决策矩阵，帮助开发者有系统地应用最佳实践与优化模式；欲获取具体例子与详细步骤，可参阅 ProAndroidDev 上的完整文章。