wac is a CLI tool and library for composing WebAssembly components using the WAC language, a declarative superset of WIT. It parses .wac files, resolves package references from the filesystem or a Warg registry, builds a directed acyclic composition graph, and encodes the result into a valid WebAssembly component binary (.wasm). The system is modular, with four core crates: wac-parser (lexer, AST, name resolution), wac-resolver (package resolution with filesystem and registry backends), wac-graph (graph representation and binary encoding), and wac-types (type system, subtype checking, semver-aware type aggregation). The CLI exposes commands such as `plug`, `compose`, `targets`, `parse`, and `resolve`, each targeting a specific composition workflow. The architecture follows a pipeline: WAC source text → lexing/parsing → AST resolution (name binding, type checking) → composition graph construction → binary encoding. The resolver supports both local `.wat`/`.wasm` files and remote packages from a Warg registry (feature-gated). The type system includes full component model types (primitives, records, variants, resources, streams, futures, functions, interfaces, worlds) with async function support and semver-aware compatibility checks. The composition graph handles imports, instantiations, aliases, exports, and argument wiring, and can merge compatible imports from multiple packages. External dependencies include the Bytecode Alliance ecosystem: wit-parser, wasmparser, wit-component, wasm-encoder, wasmprinter, wat, and optionally warg-client and warg-protocol for registry support. The project is actively developed with extensive test coverage, including roundtrip parsing, resolution error cases, graph encoding, and registry integration tests. It is published on crates.io and provides prebuilt binaries for Linux, macOS, and Windows.
The microsoft/WindowsAppSDK-Samples repository is a comprehensive suite of reference applications demonstrating the Windows App SDK (WinAppSDK) ecosystem. It is not a single monolithic application but a collection of independent projects categorized by feature domain, including App Lifecycle, Composition, Input, Notifications, AI/ML, and Islands. The codebase serves as the primary learning resource for developers building Windows desktop applications using WinUI 3, WPF, WinForms, and native C++. It explicitly covers both packaged (MSIX) and unpackaged deployment models, with distinct initialization logic for each (e.g., Bootstrap initialization for unpackaged apps). The repository also includes Visual Studio project templates to scaffold new applications. Architecturally, the repository is organized as a gallery of samples where each project is self-contained but shares common utilities in the SamplesCommon directory. The code demonstrates high craftsmanship in complex areas like Composition animations, Direct2D interop, and ONNX Runtime integration. However, the codebase exhibits significant duplication of boilerplate logic (e.g., MainWindow initialization, Navigation patterns) across dozens of sample projects. Additionally, many C++ samples rely on legacy NuGet management (packages.config) rather than modern PackageReference, indicating a technical debt in the C++ tooling alignment. The repository is actively maintained with recent commits and CI pipelines for various sample categories. It relies heavily on specific Windows App SDK versions and preview APIs (e.g., ElementCompositionPreview), which introduces a risk of drift as the SDK evolves. The presence of both C++/WinRT and raw Win32/C++ samples highlights a transition period in the Windows development stack, requiring developers to navigate mixed paradigms.
pointfreeco/swift-web is a collection of modular Swift libraries for building server-side web applications. It provides a functional approach to routing (ApplicativeRouter using partial isomorphisms and applicative combinators), a type-safe CSS DSL (Css module), an HTTP pipeline middleware system with phantom types for state safety (HttpPipeline), URL form encoding/decoding, HTML rendering integration, and signed cookie support. The architecture is highly modular: each library can be used independently. The codebase demonstrates advanced functional programming patterns from the Point-Free ecosystem, including applicative functors, optics, and monoids. It relies on Apple's SwiftNIO for server I/O and supports both macOS and Linux via Docker. The project is experimental but well-tested with snapshot testing. It is best suited for Swift developers seeking a functional, composable web framework foundation.