# modules A software module is a file or independently developed part of a program containing definitions and statements that can be imported or integrated into other software. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Starting Android at Khan Academy DevFeed: [Starting Android at Khan Academy]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-02-29T23:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Android](), [android-development](), [Development](), [Library](), [modules](), [ci](), [Mocking]() Tags: [android](), [android-development](), [development](), [engineering](), [libraries](), [mobile](), [mocking](), [module](), [modules](), [news](), [open-source](), [picasso](), [play-store](), [pre-commit](), [retrofit](), [test](), [tests]() ### AI overview Khan Academy describes its first Android app, launched in August 2015, and the engineering practices used to build it. The team adopted established Android and open-source libraries, separated Android-independent core code from the app module, and used fast JVM tests and continuous integration. ### Source excerpt By Ben Komalo The journey of a thousand miles... In March, 2015--almost 1 year ago to the day--we ... Read more ## How to Write a Linux Kernel Module That Actually Builds DevFeed: [How to Write a Linux Kernel Module That Actually Builds]() Original publisher: [Read original article]() Author: Chris Roy Published: 2026-09-15T21:10:57Z Content type: tutorial Language: en Sources: [freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More]() Topics: [Kernel](), [Linux](), [modules](), [Compiler](), [Secure Boot]() Tags: [compiler](), [kernel](), [linux](), [linux-kernel](), [module](), [secure-boot](), [tutorial]() ### AI overview This tutorial explains how to build and load a Linux kernel module, including the generated object files, metadata, symbols, debug information, required kernel headers and compiler setup, and common Secure Boot and kernel lockdown restrictions. ### Source excerpt A Linux kernel module is a small piece of code that can be loaded into the running kernel without rebuilding the entire kernel. That sounds simple enough, but even a minimal module produces a surprisi ## The Android Startup Pattern: A Lifecycle-Aware, Multi-Module Approach DevFeed: [The Android Startup Pattern: A Lifecycle-Aware, Multi-Module Approach]() Original publisher: [Read original article]() Author: Ehab Elwan Published: 2026-09-13T05:31:09Z Content type: tutorial Language: en Sources: [ProAndroidDev - Medium]() Topics: [Android](), [modules](), [Jetpack](), [Framework]() Tags: [android](), [android-development](), [app-startup](), [architecture](), [framework](), [jetpack](), [kotlin](), [mobile-architecture](), [module](), [privacy](), [software-architecture]() ### AI overview This tutorial presents a lifecycle-aware, dependency-injection-driven startup pattern for modular Android applications. It contrasts a centralized startup anti-pattern with Jetpack App Startup and discusses process lifecycles, testability, and delaying tracking SDK initialization until privacy consent is evaluated. ### Source excerpt A Clean, DI-Driven Architecture for Managing Cold Starts, Background Wakeups, and Privacy Compliance in Modern Android Apps Image generated by AIDisclosure: This article was drafted by me and refined with the help of AI tools. Every growing Android project eventually spawns a two-headed "God Class." On one side, your Application class becomes a dumping ground for global infrastructure--third-party SDKs, crash reporters, and tracking tools. On the other side, your main entry point (typically the MainViewModel) gets choked with UI-blocking startup logic. It usually looks something like this: The Anti-Pattern: The Two-Headed God Class class MyApplication : Application() { override fun onCreate() { super.onCreate() // The framework dumping ground CrashReportingSDK.getInstance().setCollectionEnabled(true) HeavyUiSDK.initialize(context = this, ...) AnalyticsSDK.initialize(this, "API_KEY") // ... 50 more lines of spaghetti } }class MainViewModel : ViewModel() { init { // The UI-blocking dumping ground updateRemoteConfigs() checkUserSessionToken() processPendingDeepLinks() prefetchHomeFeedData() // ... UI cannot render until this finishes } } Splitting initialization across these two files creates major problems: It breaks the Single Responsibility Principle: The app's entry points are forced to orchestrate the inner workings of every single feature, tightly coupling your modules. It ignores process lifecycles: Application tasks run indiscriminately on every silent background wakeup, while MainViewModel tasks fail to re-trigger when the app returns to the foreground. It destroys testability: Hardcoding SDK initializations directly into your entry points makes it incredibly difficult to write isolated unit tests without complicated mocking setups. It complicates privacy compliance: A centralized dumping ground makes it extremely difficult to dynamically suspend tracking SDKs until user consent under global privacy regulations (such as GDPR, CCPA, and CPRA) is explicitly grant ## jetc.dev Newsletter Issue #328 DevFeed: [jetc.dev Newsletter Issue #328]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-08-25T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [Jetpack Compose](), [modules](), [API]() Tags: [api](), [batching](), [exceptions](), [images](), [jetpack-compose](), [modules](), [newsletter](), [published](), [videos]() ### AI overview Newsletter Issue #328 covers Jetpack Compose development topics, including API modules and composables, lazy-container lifecycle exceptions, recomposition and state-change batching, and selecting and copying text from images and videos. ### Source excerpt API modules and composables! LazyColumn() exceptions! 'Select and copy text' for images and videos! ## Keep Kotlin Multiplatform bindings at the platform boundary DevFeed: [Keep Kotlin Multiplatform bindings at the platform boundary]() Original publisher: [Read original article]() Published: 2026-08-18T00:00:00Z Content type: tutorial Language: en Sources: [Koin - Cloud-Inject.io -Kotzilla]() Topics: [Kotlin Multiplatform](), [Kotlin](), [implementation](), [modules](), [configuration](), [test]() Tags: [configuration](), [implementation](), [kotlin](), [kotlin-multiplatform](), [module](), [multiplatform](), [test](), [verification]() ### AI overview A guide to keeping Kotlin Multiplatform dependency bindings at platform boundaries. It recommends defining small capability interfaces in common code, implementing them in platform source sets, organizing modules around capabilities and product features, and testing both shared contracts and real platform bindings. ### Source excerpt Kotlin Multiplatform makes source-set boundaries visible, but a dependency container can blur them again. A shared module should state a capability such as secure storage, HTTP transport, or local time. The platform source set should supply the implementation. Put contracts where consumers can see them Define the smallest useful interface in common code. Avoid copying a platform API into that interface. A storage contract might expose read, write, and remove; it does not need to expose Android preferences or an Apple keychain type. ## Review a Koin upgrade as a graph change, not a version bump DevFeed: [Review a Koin upgrade as a graph change, not a version bump]() Original publisher: [Read original article]() Published: 2026-08-18T00:00:00Z Content type: tutorial Language: en Sources: [Koin - Cloud-Inject.io -Kotzilla]() Topics: [Dependency injection](), [upgrade](), [modules](), [test](), [Compose]() Tags: [android](), [compose](), [dependency-injection](), [modules](), [test](), [upgrade]() ### AI overview This tutorial explains how to review a Koin dependency-injection upgrade as an architecture change rather than a simple version bump. It recommends recording the existing dependency graph, modules, warnings, startup results, and verification output; upgrading mechanisms separately; checking all startup variants; and maintaining tested rollback procedures. ### Source excerpt Dependency-injection upgrades can change more than API names. Verification behavior, annotation processing, Compose packages, compiler integration, and deprecations can all alter how the graph is built. Treat the upgrade as an architecture change with a defined before-and-after record. Freeze the current graph Before changing versions, save the dependency lock or resolved graph, the list of DI modules, startup smoke-test results, and verification-test output. Record warnings that already exist so a new warning is not confused with old noise. ## Nix-grove: Configuration framework for flake-parts DevFeed: [Nix-grove: Configuration framework for flake-parts]() Original publisher: [Read original article]() Author: bitbloxhub Published: 2026-08-08T18:32:05Z Content type: comparison Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Nix](), [configuration](), [modules](), [Framework]() Tags: [announcements](), [configuration](), [framework](), [modules]() ### AI overview A forum discussion introduces Nix-grove, a configuration framework for flake-parts. It describes using the Nix module system to define typed classes and instances, project them into module systems, and override individual results instead of relying primarily on an import=enable pattern. ### Source excerpt AI USAGE: I used ChatGPT (GPT-5.6-Sol) to assist with design and planning, and Pi with GPT-5.6-Luna via openai-codex to help with implementation github.com GitHub - bitbloxhub/nix-grove: Configuration framework for flake-parts: define... Configuration framework for flake-parts: define typed classes and instances, project them into Nix module systems, and override individual results. Sort of an "alternative" to the Dendritic pattern. Still is about importing a bunch of flake-parts modules, but uses the module system for more, instead of import=enable. 6 posts - 3 participants Read full topic ## Make scalable routing system for your Flutter Apps DevFeed: [Make scalable routing system for your Flutter Apps]() Original publisher: [Read original article]() Author: Kanan Yusubov Published: 2026-07-29T15:25:43Z Content type: tutorial Language: en Sources: [Flutter Community - Medium]() Topics: [Flutter](), [Routing (disambiguation)](), [navigation](), [modules](), [Dependency injection](), [Usability]() Tags: [clean-architecture](), [dependency-injection](), [flutter](), [go-router](), [modular-router](), [modules](), [navigation](), [router](), [routing](), [routing-system](), [usability]() ### AI overview This tutorial describes a scalable, decoupled routing system for Flutter apps. It explains a wrapper built on go_router that adds typed route arguments, native and path parameters, cross-module modularization, nested routes, presentation modes, and type-safe route guards. ### Source excerpt Recently, I've been working on migrating our app's routing system. We previously used auto_route, but eventually realized its tightly coupled nature made it incredibly difficult to scale across independent modules. Furthermore, its heavy reliance on code generation became a bottleneck for our workflow. To resolve this, we decided to architect a clean, scalable, and highly decoupled routing system. Our new solution is a powerful wrapper built on top of go_router. It abstracts away the raw string navigation and supercharges the router with custom features to maximize usability and type safety. In this blog post, I will walk you through the core benefits of this new routing system, covering the following key topics: Unified Routing Protocol (AppRouteInfo) Strictly Typed Route Arguments Native & Path Parameters Support Cross-Module Modularization (AppModuleRouter) Hierarchical Back stack & Sub-Routes (Nested Route Definitions, Decoupled Cross-Module Navigation) Dynamic Presentation Modes (e.g., Native, ModalSheet, NoTransition) Guard Interceptor Mechanism (Type-Safe Redirects, Global Interceptors) Note: This blog will show the general usage and problems it solved. For more detailed code, you can check the following link: https://github.com/thisisyusub/scalable-routing-system-demoArchitectural Structure of Routing System Here is how the demo application is structured to achieve a fully decoupled, scalable routing system: scalable_routing_system_demo (main app): The entry point of the application responsible for wiring up all services, dependency injection, and global route configurations. app_routes: Houses all route definitions, parameters, routing protocols, and models to ensure fully type-safe navigation. This is decoupled from the core routing package to separate app-specific business needs from generic routing mechanics. routing_system (core router): A generic, domain-agnostic router package that has zero knowledge of the app's specific routes. It exclusively provid ## Profunctor Optics DevFeed: [Profunctor Optics]() Original publisher: [Read original article]() Author: Bartosz Milewski Published: 2026-07-19T11:39:02Z Content type: article Language: en Sources: [Bartosz Milewski's Programming Cafe]() Topics: [Haskell](), [Programming language](), [Programming](), [modules]() Tags: [category-theory](), [haskell](), [language](), [lens](), [mapping](), [modules](), [optics](), [profunctors](), [programming-language](), [tambara-modules]() ### AI overview This article explains profunctor optics through Tannakian reconstruction. It presents optics as a category, describes lenses and their composition in Haskell, and introduces Tambara modules as a representation that simplifies optic composition. ### Source excerpt You may think of Tannakian Reconstruction as an example of redundant encoding. It lets you replace a simple hom-set with a much more complex end that is taken over an entire functor category. Why would anyone want to do it? The answer is simple: composition! Morphisms on the left compose according to the rules of [...] ## A Gradle Module Structure for Clear Boundaries, Faster Builds, and Test Coverage DevFeed: [A Gradle Module Structure for Clear Boundaries, Faster Builds, and Test Coverage]() Original publisher: [Read original article]() Author: Jesse Wilson Published: 2026-07-15T13:38:11Z Content type: article Language: en Sources: [Blogs on Ryan Harter]() Topics: [Gradle](), [build times](), [modules](), [test-coverage](), [Android Gradle Plugin](), [Kotlin]() Tags: [android-gradle-plugin](), [build](), [build-times](), [gradle](), [kotlin](), [modules](), [test-coverage]() ### AI overview The article describes a Gradle module convention that separates each feature's public API from its implementation. The author says this structure reduced build times and coupling between features while helping enforce test coverage, with Android Gradle Plugin support making a separate test-fixtures module unnecessary. ### Source excerpt Flattening my Dependency Graph Jesse Wilson Jesse explores a Gradle module structure that he likes. Read now ➡ I liked this not-so-recent post from Jesse Wilson, which outlines a Gradle module convention that prioritizes clear public/private boundaries to support encapsulation and build speed. The approach, adapted from one presented by Ralf Wondratschek, also happens to closely resemble one that I helped institute at Dropbox shortly after I joined four and a half years ago. ## Tambara Equipment DevFeed: [Tambara Equipment]() Original publisher: [Read original article]() Author: Bartosz Milewski Published: 2026-07-11T08:13:34Z Content type: article Language: en Sources: [Bartosz Milewski's Programming Cafe]() Topics: [modules](), [Haskell](), [Code]() Tags: [category-theory](), [code](), [double-categories](), [double-category](), [haskell](), [modules](), [optics](), [proarrow-equipment](), [profunctors](), [structure](), [tambara-modules](), [tannakian-reconstruction](), [theory](), [transformation]() ### AI overview This article explains Tambara modules through category theory and illustrates the concepts with Haskell code. It discusses their relationship to profunctors, monoidal actions, double categories, proarrow equipment, and Tannakian reconstruction. ### Source excerpt I was originally attracted to category theory when trying to understand Haskell optics. I was puzzled by the van Laarhoven's functor representations and Kmett's use of Tambara modules. By playing Tetris with the Yoneda lemma I was able to make some progress, attacking more and more esoteric topics. With a group of researcher and students [...] ## NixOS 26.05 released DevFeed: [NixOS 26.05 released]() Original publisher: [Read original article]() Author: NixOS Published: 2026-05-30T07:00:00Z Content type: release Language: en Sources: [NixOS Announcements]() Topics: [Nix](), [Linux](), [releases](), [Release notes](), [systemd](), [configuration](), [modules](), [deprecated](), [Package manager]() Tags: [2026](), [accessibility](), [configuration](), [deprecated](), [end-of-life](), [gcc](), [linux](), [llvm](), [macos](), [modules](), [nix](), [nixos](), [release](), [release-notes](), [systemd](), [x86-64]() ### AI overview NixOS 26.05, named "Yarara," is publicly available as a new Linux distribution release. The announcement covers package, module, configuration, systemd initrd, platform-support, GNOME, and compiler changes, along with support timelines for NixOS 26.05 and the previous 25.11 release. ### Source excerpt Hey everyone, we are yayayayaka and jopejoe1, the release managers of the newest release of NixOS. We are very proud to announce the public availability of NixOS 26.05 "Yarara". NixOS is a Linux distribution. Its underlying package repository Nixpkgs can also be used on other Linux systems and macOS with the Nix package manager. This release will receive bugfixes and security updates for seven months (up until 2026-12-31). The old release 25.11 "Xantusia" is now officially deprecated and will reach its end-of-life and stop receiving security updates after 2026-06-30. NixOS Release Notes Highlights New Modules Backward Incompatibilities Other Notable Changes Nixpkgs Release Notes Highlights Backward Incompatibilities Other Notable Changes Nixpkgs Library Upgrade Instructions ISO Image Downloads The 26.05 release was made possible due to the efforts of 2842 contributors, who authored 59703 commits since the previous release. Highlights Our vast and routinely maintained set of packages has also been updated. This release of Nixpkgs Added 20442 new packages Updated 20641 existing packages Removed 17532 outdated packages, in an effort to keep the package set maintainable and secure. In addition to packages from Nixpkgs, the NixOS Linux distribution also features composable configuration modules and integration tests for distributed systems. This release of NixOS Added 85 new modules and 1547 configuration options Removed 25 outdated modules and 355 configuration options. systemd stage 1 Stage 1 (a.k.a. initrd) is now based on systemd by default, and the old scripted implementation is deprecated and scheduled for removal in 26.11. Deprecation of x86_64-darwin This will be the last release of Nixpkgs to support x86_64-darwin. Platform support will be maintained and binaries built until Nixpkgs 26.05 goes out of support at the end of 2026. For 26.11, due to Apple's deprecation of the platform and limited build infrastructure and developer time, we will no longer build packa ## Metro DI for Ktor Backend: From a God Object through manual DI to Constructor Injection DevFeed: [Metro DI for Ktor Backend: From a God Object through manual DI to Constructor Injection]() Original publisher: [Read original article]() Author: FunkyMuse Published: 2026-05-15T15:35:00Z Content type: tutorial Language: en Sources: [FunkyMuse]() Topics: [Ktor](), [Back end](), [modules]() Tags: [backend](), [constructor](), [dependencies](), [di](), [gradle](), [kotlin](), [ktor](), [redis](), [server](), [unit-test]() ### AI overview This article describes replacing manual dependency injection in a Ktor backend with Metro. It explains how default constructor parameters and a central BackendComponent can accidentally couple tests to real dependencies such as Redis, while Metro wires constructor parameters at compile time and removes those defaults. ### Source excerpt The Starting Point: a God Object When Rudio was a created a few months ago it used the simplest possible DI: one big object BackendComponent with everything wired manually via by lazy and lateinit var. No framework, no annotations, no ceremony, then i started adding things and manual DI became a tedious and tiring task because everywhere i used default parameters to achieve default constructor... ## Compose Unstyled 2.0 introduces a foundation for building Compose component libraries DevFeed: [Compose Unstyled 2.0 introduces a foundation for building Compose component libraries]() Original publisher: [Read original article]() Author: Alex Styl Published: 2026-05-14T00:00:00Z Content type: release Language: en Sources: [Composables - Concise, no-fluff video tutorials for Android developers]() Topics: [Compose](), [Design system](), [modules](), [Accessibility]() Tags: [accessibility](), [component](), [compose](), [design-system](), [modules](), [release]() ### AI overview Compose Unstyled 2.0 is presented as a foundation for building custom Compose component libraries. The release introduces composable component APIs, redesigned Dropdown and Tooltip APIs, separate modules, and a fully unstyled core with deprecated APIs removed. ### Source excerpt Compose Unstyled 2.0 is a new foundation for building your own Compose component library. ## How AI agents could shift software work from code changes to specifications and module rebuilds DevFeed: [How AI agents could shift software work from code changes to specifications and module rebuilds]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2026-05-04T16:00:00Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [Artificial Intelligence](), [Software Engineering](), [Agent Skills](), [Software](), [Refactoring](), [modules](), [patches]() Tags: [agents](), [ai](), [code](), [module](), [patches](), [refactoring](), [software-engineering]() ### AI overview This opinion article argues that AI agents may act like compilers, turning detailed specifications into software and reducing the need to write implementation code directly. Drawing on examples where the author changed implementations while preserving behavior, it suggests that agents could make rebuilding entire modules more practical than incremental patching and refactoring. ### Source excerpt Linus Torvalds recently said1 AI will be to code what compilers were to assembly -- freeing us from writing it by hand. Around the same time, I talked with Jesse Vincent (creator of one of the most popular agent skills out there -- superpowers). Something he said stuck with me: Specs are going to be the new code. I realize those two ideas snap together a little too neatly. Agents are compilers2 and specs will become code. Software engineering is moving up another level of abstraction and we've seen this play out before. Specs as source ## I saw this first-hand with my tiny USB-C cable checker -- usbi. It started as a shell command over macOS's system_profiler, then became Go when I wanted a proper binary, then Rust because I wanted to practice Rust, and later a .kts version. The code kept changing. The thing I cared about did not: parse the USB tree, identify the attached devices, report the speed, and make bad cables obvious. Podsync, my voice track sync program, followed the same pattern. It started in Python because the audio libraries were there. Then I moved it to Rust because I didn't want to ship a Python runtime or care which Python version happened to be on a machine. Again, the implementation changed. The behavior stayed boringly stable: take a master track and local tracks, find the offset, pad or trim each file, and drop aligned audio into the DAW. Compilers freed us from writing assembly. Agents may free us from writing code because it becomes an artifact the spec produces. The somewhat recent push around detailed exec plans could be an early signal of the looming shift at bigger scale. Rebuilds instead of patches ## Push that thought further. We might get comfortable rebuilding whole modules instead of patching and refactoring them. We preserved the old shape of a system because throwing it away cost too much. Even when you know the module is wrong, you sand it down: extract an interface, migrate one caller at a time, add tests around behavior nobody full ## Modernizing the Command Line: Heroku CLI v11 DevFeed: [Modernizing the Command Line: Heroku CLI v11]() Original publisher: [Read original article]() Author: Eric Black Published: 2026-03-19T22:29:49Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Command-line interface](), [ECMAScript](), [modules](), [migration](), [maintenance](), [Usability]() Tags: [cli](), [command-line](), [heroku](), [javascript](), [legacy](), [maintainability](), [migration](), [modules](), [monorepo](), [news](), [node-js](), [npm](), [performance](), [release](), [upgrade](), [usability]() ### AI overview Heroku CLI v11 is available with a migration to ECMAScript Modules and oclif v4. The release also changes the build system from Yarn to npm, removes the monorepo structure, improves command execution and manifest caching, and adds semantic colors and theme support. ### Source excerpt Heroku CLI v11 is now available. This release represents the most significant architectural overhaul in years, completing our migration to ECMAScript Modules (ESM) and oclif v4. This modernization brings faster performance, a new semantic color system, and aligns the CLI with modern JavaScript standards. While v11 introduces breaking changes to legacy namespaces, the benefits are [...] The post Modernizing the Command Line: Heroku CLI v11 appeared first on Heroku. ## pg\_plan\_advice: Plan Stability and User Planner Control for PostgreSQL? DevFeed: [pg\_plan\_advice: Plan Stability and User Planner Control for PostgreSQL?]() Original publisher: [Read original article]() Author: Robert Haas (noreply@blogger.com) Published: 2026-03-04T17:55:00Z Content type: opinion Language: en Sources: [Robert Haas]() Topics: [PostgreSQL](), [JOIN](), [modules](), [Query (disambiguation)]() Tags: [join](), [modules](), [plan](), [planner](), [postgresql](), [query](), [test]() ### AI overview The article presents a proposed PostgreSQL 19 patch set introducing the pg_plan_advice, pg_collect_advice, and pg_stash_advice contrib modules. It demonstrates how pg_plan_advice can generate plan advice strings, preserve selected planner decisions, or vary advice to produce a different join plan. ### Source excerpt I'm proposing a very ambitious patch set for PostgreSQL 19. Only time will tell whether it ends up in the release, but I can't resist using this space to give you a short demonstration of what it can do. The patch set introduces three new contrib modules, currently called pg_plan_advice, pg_collect_advice, and pg_stash_advice. Read more " ## 7 steps in a Legacy Modernization Project DevFeed: [7 steps in a Legacy Modernization Project]() Original publisher: [Read original article]() Author: Federico Tomassetti Published: 2026-02-25T06:55:00Z Content type: tutorial Language: en Sources: [Federico Tomassetti]() Topics: [Agile](), [Code quality](), [Code](), [modules]() Tags: [automated](), [business-value](), [code-quality](), [legacy-modernization](), [modernization](), [modules](), [project](), [rpg](), [technical]() ### AI overview This tutorial outlines seven steps for modernizing an RPG-based ERP/MRP system: assess the legacy landscape, define a roadmap, secure buy-in and budget, build the right team and partnerships, execute iterative value-driven increments, manage change, and measure and adapt the modernization effort. ### Source excerpt Embarking on an RPG-based ERP/MRP system modernization is undeniably complex. But it's also highly rewarding when aligned with your business's long-term success. By addressing both the technical and strategic facets, you turn an aging system from a liability into a competitive asset. Let's outline the 7 steps in a legacy modernization project: Step 1: Assess [...] The post 7 steps in a Legacy Modernization Project appeared first on Federico Tomassetti. ## Inspecting the Source of Go Modules DevFeed: [Inspecting the Source of Go Modules]() Original publisher: [Read original article]() Author: Filippo Valsorda Published: 2026-02-12T13:48:03Z Content type: article Language: en Sources: [Filippo Valsorda]() Topics: [Go Language](), [modules](), [integrity](), [Security](), [GitHub](), [Code]() Tags: [cryptographic](), [github](), [go](), [integrity](), [modules](), [security](), [tooling](), [transparency-log](), [verification](), [verify]() ### AI overview The article explains how the Go Checksum Database verifies module source and helps protect against altered tags and targeted versions. It argues that viewing code directly on GitHub can bypass this verification, using a malicious BoltDB module incident as an example, and recommends fetching source with Go tooling for review. ### Source excerpt Code hosts like GitHub don't necessarily show the correct source of Go modules. pkg.geomys.dev is a new convenient viewer for module source. ## From Dagger to Metro DevFeed: [From Dagger to Metro]() Original publisher: [Read original article]() Author: Andrius Semionovas Published: 2026-02-12T00:00:00Z Content type: article Language: en Sources: [Vinted]() Topics: [Dependency injection](), [Android](), [migration](), [Kotlin](), [Dagger](), [interoperability](), [Compiler](), [modules](), [Gradle]() Tags: [android](), [compatibility](), [compilation](), [dagger](), [dependency-injection](), [gradle](), [interoperability](), [kotlin](), [migration](), [modules]() ### AI overview Vinted's Android developers describe their migration from Dagger and related dependency-injection tools to Metro. The article covers their large, modular codebase, Anvil's maintenance status and K2 migration pressure, and Metro's interoperability with Dagger, Anvil, and kotlin-inject. ### Source excerpt Metro - modern and kotlin injection framework created by Zac Sweers. And we, Android developers at Vinted, officially and fully migrated to it! It was quite a bumpy ride for our huge codebase. Our story begins... ## IPLD 2025 Review: From Monoliths to Modules DevFeed: [IPLD 2025 Review: From Monoliths to Modules]() Original publisher: [Read original article]() Author: Volker Mische Published: 2026-01-19T00:00:00Z Content type: article Language: en Sources: [IPFS]() Topics: [Rust](), [modules](), [migration](), [IPFS](), [AT Protocol](), [deprecated]() Tags: [deprecated](), [ipfs](), [migration](), [modules](), [object-object](), [protocol](), [rust]() ### AI overview The article reviews progress in the IPLD ecosystem during 2025 and previews work for 2026. It describes the Rust IPLD implementation's migration to separate crates, its deprecation, improved performance for Python DAG-CBOR and Bluesky custom feeds, and a migration path to Serde-based crates. ### Source excerpt The year that brought us modular Rust libraries, faster DAG-CBOR, stable multiformats, and a simpler on-ramp with DASL. ## go.sum Is Not a Lockfile DevFeed: [go.sum Is Not a Lockfile]() Original publisher: [Read original article]() Author: Filippo Valsorda Published: 2026-01-05T20:06:30Z Content type: article Language: en Sources: [Filippo Valsorda]() Topics: [Go Language](), [modules](), [Security](), [supply chain attacks]() Tags: [dependencies](), [go](), [golang](), [modules](), [security](), [supply-chain-attacks]() ### AI overview The article explains that Go's go.sum is a local cache of cryptographic hashes for the Go Checksum Database, not a lockfile and not part of version resolution. It contrasts go.sum with go.mod, which lists the precise dependency versions used to build the main module and its tests. ### Source excerpt In Go, go.mod acts as both manifest and lockfile. There is never a reason to look at go.sum. ## NixOS 25.11 released DevFeed: [NixOS 25.11 released]() Original publisher: [Read original article]() Author: NixOS Published: 2025-11-30T16:00:00Z Content type: release Language: en Sources: [NixOS Announcements]() Topics: [Nix](), [Linux](), [Release notes](), [version](), [configuration](), [modules](), [CMake](), [gcc](), [LLVM]() Tags: [2026](), [bugfixes](), [cmake](), [compilers](), [deprecated](), [end-of-life](), [gcc](), [linux](), [llvm](), [nix](), [nixos](), [nixpkgs](), [release](), [release-notes](), [version]() ### AI overview NixOS 25.11 "Xantusia" is publicly available. The release updates Nixpkgs with new, updated, and removed packages; adds configuration modules and options; updates GNOME to version 49, LLVM to version 21, and CMake to version 4; and provides bugfix and security updates through June 30, 2026. ### Source excerpt Hey everyone, we are jopejoe1 and Leona Maroni, the release managers of the newest release of NixOS. We are very proud to announce the public availability of NixOS 25.11 "Xantusia". NixOS is a Linux distribution. Its underlying package repository Nixpkgs can also be used on other Linux systems and macOS with the Nix package manager. This release will receive bugfixes and security updates for seven months (up until 2026-06-30). The old release 25.05 "Warbler" is now officially deprecated and will reach its end-of-life and stop receiving security updates after 2025-12-31. NixOS Release Notes Highlights New Modules Backward Incompatibilities Other Notable Changes Nixpkgs Release Notes Highlights Backward Incompatibilities Other Notable Changes Nixpkgs Library Upgrade Instructions ISO Image Downloads The 25.11 release was made possible due to the efforts of 2742 contributors, who authored 59430 commits since the previous release. Highlights Our vast and routinely maintained set of packages has also been updated. This release of Nixpkgs Added 7002 new packages Updated 25252 existing packages Removed 6338 outdated packages, in an effort to keep the package set maintainable and secure. In addition to packages from Nixpkgs, the NixOS Linux distribution also features composable configuration modules and integration tests for distributed systems. This release of NixOS Added 107 new modules and 1778 configuration options Removed 41 outdated modules and 807 configuration options. GNOME 49 GNOME has been updated to version 49 "Brescia", which removes X11 session support, introduces a new video player, a new document viewer, a redesigned calendar and more changes. Refer to the release notes for more details. C compilers LLVM has been updated to version 21. GCC remains at version 14. CMake was updated to version 4. Special Thanks We want to personally thank Seth and dish for editorializing the release notes Yohann Boniface for the release logo The NixOS infrastructure team for the ## Python in Visual Studio Code - November 2025 Release DevFeed: [Python in Visual Studio Code - November 2025 Release]() Original publisher: [Read original article]() Author: Luciana Abud Published: 2025-11-13T18:41:50Z Content type: release Language: en Sources: [Microsoft Python Engineering]() Topics: [Python](), [Visual Studio Code](), [GitHub Copilot](), [debug](), [modules]() Tags: [copilot](), [debugger](), [developers](), [features](), [github-copilot](), [improvements](), [modules](), [python](), [release](), [visual-studio-code]() ### AI overview The November 2025 release of the Python extension for Visual Studio Code adds Copilot Hover Summaries support for inserting AI-generated documentation as docstrings, localized hover summaries, a Pylance Code Action for converting wildcard imports to explicit imports, and debugger support for multiple project interpreters through the Python Environments Extension. ### Source excerpt The November 2025 release brings new Pylance features including improvements to Copilot Hover Summaries and a Code Action to convert wildcard imports to explicit imports. Keep on reading to learn more! The post Python in Visual Studio Code - November 2025 Release appeared first on Microsoft for Python Developers Blog. [Next page]()