For years, building interactive widgets in Python notebooks meant wrestling with toolchains, platform quirks, and a mountain of JavaScript machinery. Most developers took one look and backed away slowly. Trevor Manz decided that barrier did not need to exist. His idea was simple: give Python users just enough JavaScript to unlock the web’s interactivity, without dragging along the rest of the web ecosystem. That idea became anywidget, and it is quickly becoming the quiet connective tissue of modern interactive computing. Today we dig into how it works, why it has taken off, and how it might change the way we explore data.

Episode sponsors

Seer: AI Debugging, Code TALKPYTHON
PyCharm, code STRONGER PYTHON
Talk Python Courses

Links from the show

Download audio: https://talkpython.fm/episodes/download/530/anywidget-jupyter-widgets-made-easy.mp3

Building a Frontend Before the API is Ready: Without Brittle Fixtures

Welcome to F# Weekly,

A roundup of F# content from this past week:

News

• .NET 10 Networking Improvements – .NET Blog
• Microsoft Learn MCP Server Elevates Development – .NET Blog
• Implementing Cross-Platform In-App Billing in .NET MAUI Applications – .NET Blog
• Making Windows Terminal awesome with GitHub Copilot CLI – Microsoft for Developers
• Join us for AI Dev Days – December 10-11 – Microsoft for Developers
• Aspire Integrations, Batteries Included | Aspire Blog
• Streamlining your Git workflow with Visual Studio 2026 – Visual Studio Blog

Excited to announce SharpIDE – A Modern, Cross-Platform IDE for .NET!I'm thrilled to share my latest open-source project, just in time for .NET 10: SharpIDE, a brand new IDE for .NET, built with .NET and Godot! Check it out on GitHub: github.com/MattParkerDe……

— Matt Parker (@mattparker.dev) 2025-11-11T23:24:13.521Z

Videos

• Type Inference: Write Less Code, Catch More Bugs.
• Excel: The World’s Most Successful Functional Programming Platform by Houston Haynes
• Advent of code 2025 in F# – day 07
• Advent of code 2025 in F# – day 08
• TinyExcel 7.1 – Technical dimensions of spreadsheets
• TinyExcel 7.2 – Architecture and F# events
• TinyExcel 7.3 – Code structure and step-by-step guide
• ASP.NET Community Standup – Build agentic UI with AG-UI and Blazor
• On .NET Live – On .NET Live | Patterns in Messaging Systems
• .NET Day on Agentic Modernization

Let's build a Programming Language – together!The goal? Combine the developer experience of Python with the safety of TypeScript.In Episode 0: Syntax + Type Inference http://www.youtube.com/watch?v=fSRT…#TypeInference #TypeScript #CSharp #FSharp #Rust #Haskell

— SchlenkR (@schlenkr.bsky.social) 2025-12-13T08:58:15.904Z

Blogs & FsAdvent

• Implementing my own bookmark manager – Jozsef Uri
• F# in Production: What I Know After Four Years – Ben Copeland
• Comprehensive Guide to SRTP Gymnastics – Millennium
• I like my F# code type annotation-free – Urs Enzler
• Adding Goal Seek to Quipu (and helping Santa with it!) – Mathias Brandewinder
• Tagless Final in F# – John Azariah
  • Tagless Final in F# – Part 1: Froggy Tree House
  • Tagless Final in F# – Part 2: Maps, Branches, and Choices
  • Tagless Final in F# – Part 3: Goals, Threats, and Getting Stuck
  • Tagless Final in F# – Part 3: Goals, Threats, and Getting Stuck
  • Tagless Final in F# – Part 5: Verifying the Elevator
  • Tagless Final in F# – Part 6: The Power of Tagless-Final: Code as Model
• Making of A Programming Language – Making of A Programming Language
• Baker: A Key Ingredient to Firefly | SpeakEZ Technologies
• Show Notes: The World’s Most Successful FP Platform | SpeakEZ Technologies

F# vNext

• mutable on any binding · Issue #1457 · fsharp/fslang-suggestions
• [WIP]: MethodImplOption.Async support by TheAngryByrd · Pull Request #19065 · dotnet/fsharp

Highlighted projects

• speakeztech/Firefly: A compiler that brings F#’s elegance and precision to systems programming through MLIR and various backends
• cariandrum22/Xanthos: Type-safe F# wrapper for the JRA-VAN JV-Link COM API, providing functional access to Japanese horse racing data.
• mrtz-j/Saturn.OpenTelemetry: A OpenTelemetry Extension for Saturn

New Releases

• Akka.FSharp 1.5.57
• FSharp.Azure.Quantum 1.3.2
• FCQRS.Model 5.0.1
• Xanthos 0.1.0
• CloudflareFS.Management 0.1.0
• CloudflareFS.Runtime 0.1.0
• Feliz.Template 5.0.0
• Hedgehog 2.0.0
• Hedgehog.Xunit.v3 2.0.0
• FSharp.Core 10.0.101
• FSharp.Compiler.Service 43.10.101
• Fantomas.FCS 8.0.0-alpha-001
• Paket 10.0.0-alpha011

Hm… Serena #fsharp

— Sergey Tihon (@sergeytihon.com) 2025-12-08T22:13:13.971Z

That’s all for now. Have a great week.

If you want to help keep F# Weekly going, click here to jazz me with Coffee!

Steven J. Vaughan-Nichols files this report from Tokyo: At the invitation-only Linux Kernel Maintainers Summit here, the top Linux maintainers decided, as Jonathan Corbet, Linux kernel developer, put it, "The consensus among the assembled developers is that Rust in the kernel is no longer experimental — it is now a core part of the kernel and is here to stay. So the 'experimental' tag will be coming off." As Linux kernel maintainer Steven Rosted told me, "There was zero pushback." This has been a long time coming. This shift caps five years of sometimes-fierce debate over whether the memory-safe language belonged alongside C at the heart of the world's most widely deployed open source operating system... It all began when Alex Gaynor and Geoffrey Thomas at the 2019 Linux Security Summit said that about two-thirds of Linux kernel vulnerabilities come from memory safety issues. Rust, in theory, could avoid these by using Rust's inherently safer application programming interfaces (API)... In those early days, the plan was not to rewrite Linux in Rust; it still isn't, but to adopt it selectively where it can provide the most security benefit without destabilizing mature C code. In short, new drivers, subsystems, and helper libraries would be the first targets... Despite the fuss, more and more programs were ported to Rust. By April 2025, the Linux kernel contained about 34 million lines of C code, with only 25 thousand lines written in Rust. At the same time, more and more drivers and higher-level utilities were being written in Rust. For instance, the Debian Linux distro developers announced that going forward, Rust would be a required dependency in its foundational Advanced Package Tool (APT). This change doesn't mean everyone will need to use Rust. C is not going anywhere. Still, as several maintainers told me, they expect to see many more drivers being written in Rust. In particular, Rust looks especially attractive for "leaf" drivers (network, storage, NVMe, etc.), where the Rust-for-Linux bindings expose safe wrappers over kernel C APIs. Nevertheless, for would-be kernel and systems programmers, Rust's new status in Linux hints at a career path that blends deep understanding of C with fluency in Rust's safety guarantees. This combination may define the next generation of low-level development work.

Read more of this story at Slashdot.

---