SShortSingh.
Back to feed

Fitz UI components now compile to both server-side HTML and client-side WebAssembly

0
·1 views

The Fitz framework has achieved isomorphic UI rendering, allowing all 38 companion UI components written in its .fitzv format to target both server-side rendering and client-side WebAssembly without rewriting code. A single .fitzv file can be compiled via two backends: the classic SSR path that produces HTML strings for LiveViews, and a new wasm-client target that builds real DOM using web-sys in the browser. Three key technical barriers were resolved along the way, including raw HTML injection, list-driven component data passing, and helper-body list construction. Previously, a parallel hand-written client version was maintained separately for the component gallery, but that duplication has now been eliminated. The live gallery currently runs 22 companion components compiled to WebAssembly, with Pager and ConfirmDialog also fully functional client-side after gaining support for fall-through event forwarding.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Guide outlines how to build security-audited AI chat interfaces in TypeScript

A technical guide published on DEV Community details how frontend engineers can build production-grade AI chat applications in TypeScript that meet enterprise security standards. The article addresses growing threats such as prompt injection attacks, PII leakage, and supply chain vulnerabilities, which have raised the security bar for AI-facing interfaces in 2024. It walks through a full development lifecycle using Vercel's assistant-ui library alongside a Next.js backend-for-frontend proxy, ensuring LLM API keys are never exposed directly to the browser. Key steps covered include strict TypeScript configuration, dependency hygiene with pnpm, context sanitization, PII redaction, and automated security scanning. The guide targets compliance with frameworks such as OWASP Top 10 for AI, SOC 2, and ISO 27001.

0
ProgrammingDEV Community ·

Obsidian Emerges as a Go-To Local Knowledge Base for AI Agents in 2026

Obsidian, a local markdown-based note-taking app, is gaining traction in 2026 as a personal knowledge management tool that integrates directly with AI agents like Claude Code. The app stores notes as plain Markdown files on the user's device, requires no cloud dependency, and has been free for commercial use since early 2025, making it attractive for privacy-sensitive workflows. AI plugins such as Smart Connections use Retrieval-Augmented Generation to let users query their entire note vault, while tools like Ollama enable fully offline AI interaction without data leaving the device. In January 2026, Obsidian CEO Steph Ango published the MIT-licensed 'obsidian-skills' repository on GitHub, which teaches AI agents to understand Obsidian's formatting conventions and quickly accumulated over 13,000 stars. A related open-source plugin, claude-obsidian, builds on this foundation by automatically generating linked wiki pages per source and maintaining context across sessions, reflecting a broader shift toward AI-augmented personal knowledge bases.

0
ProgrammingDEV Community ·

WebAssembly Explained: Real-World Uses, Limits, and When to Skip It

WebAssembly (WASM) is a binary instruction format that serves as a compilation target for languages like C, Rust, and Go, allowing code to run in browsers at near-native speeds. It outperforms JavaScript for compute-heavy tasks such as numerical processing, cryptography, and media encoding, but offers no advantage for DOM manipulation or tasks already optimized by JavaScript's JIT compiler. Practical applications include running FFmpeg for in-browser video processing, executing SQLite databases locally, and encoding modern image formats like AVIF using codec libraries not yet natively supported by browsers. However, WASM comes with trade-offs: frequent calls across the JS/WASM boundary add overhead, large file sizes (FFmpeg's core weighs around 30MB) require careful lazy loading and caching strategies, and enabling multithreading demands specific HTTP security headers that can break third-party scripts. Developers are advised to treat WASM as a targeted tool for specific performance bottlenecks rather than a universal replacement for JavaScript.

0
ProgrammingDEV Community ·

Backstage Evolves Into AI Hub for Developers, Used by 3,400+ Organisations

At KubeCon + CloudNativeCon Europe in Amsterdam in March 2026, the Backstage developer portal community held its fifth BackstageCon, highlighting the platform's significant evolution since Spotify open-sourced it in 2020. Originally built at Spotify in 2016 to manage hundreds of microservices, Backstage is now a CNCF incubation project used by over 3,400 organisations serving more than two million developers, commanding an estimated 89 percent share of the developer portal market. The platform's biggest shift in 2026 is its deep integration with AI, including Model Context Protocol (MCP) server support that allows AI coding agents like Claude Code and Cursor to directly access the Software Catalog, Templates, and documentation. A new catalog entity type called AiResource, introduced in v1.54, makes AI models and agents first-class citizens within the portal. Spotify reported that its internal AI Knowledge Assistant, connected via MCP, cut developers' time spent on answerable routine requests by 47 percent, underscoring the practical productivity gains of the AI-integrated approach.