The Disk and LocalDisk services have a new method mkdirIfNotExists to creates directories. This is useful when using the local file system to ensure that a directory exists before saving files. Otherwise, an error can be thrown when it does not. On cloud storage services such as S3, directories are created automatically when saving files so this method does nothing.
Well, I've been playing with a new tool that's been gaining a ton of steam, and honestly? I don't think I'm going back. It's called UV, and it comes from Astral, the same team behind the super-popular linter, ruff. The goal here is ambitious. UV wants to be the single tool that replaces pip, venv, pip-tools, and even pipx. It's an installer, an environment manager, and a tool runner all rolled into one. And because it's written in Rust, it's ridiculously fast.
The release of Apache Grails 7.0.0 delivers bug fixes and notable changes such as: the ability to disable Micronaut auto configuration through the Grails plugin; improved reproducibility with implementations of Grails Object Relational Mapper (GORM) services; and a temporary removal of the GORM for Neo4J. Grails 7.0 requires a minimal version of JDK 17 (with testing validated up to JDK 21) and compliance with Spring Boot 3.5 and Jakarta EE 10.
Building a UI in Python usually means choosing between "quick and limited" or "powerful and painful." What if you could write modern, component-based web apps in pure Python and still keep full control? NiceGUI, pronounced "Nice Guy" sits on FastAPI with a Vue/Quasar front end, gives you real components, live updates over websockets, and it's running in production at Zauberzeug, a German robotic company. On this episode, I'm talking with NiceGUI's creators, Rodja Trappe and Falko Schindler, about how it works, where it shines,
Nitro.js is a JavaScript-based HTTP server. It builds on state-of-the-art components, focusing on performance, convention, and deployment. As a JavaScript developer, you want to know about Nitro because it's built from the ground up for modern, full-stack web development. It brings together a wealth of good ideas and is becoming a go-to server option. Nitro is deployment-aware, designed to make it easy to deploy your code to a variety of production platforms, from Node to serverless and edge computing hosts like Vercel or CloudFlare.
Reactive programming is an important coding style that evolved from the functional programming world. Reactive code is ideal for processing and connecting realtime streaming data. You can use reactive programming to compose streams into pipelines that cleanly model complex logic with non-blocking operations. Java has excellent reactive support, and one of the most popular reactive Java frameworks is Spring WebFlux.
The hype around the introduction of React Server Components (RSC) was undeniable. For the uninitiated, RSCs are a new way to build React apps that render components on the server, keeping code and data-fetching logic away from the client. The promise was appealing: a unified approach to server and client rendering, unmatched performance, and simpler data fetching, enough to convince many of us that this was the next best thing after cheese.
Solid.js takes a unique approach to reactive state management that has broadly influenced other reactive front-end JavaScript frameworks. It provides a compact set of reactive primitives built on signals, rather than state, and leverages those to support higher-order functionality. With a clean core design built for speed and a full set of enterprise features, Solid charted an impressive 90% developer satisfaction in the January 2025 State of JavaScript survey. Let's get started with Solid.js.
If you've worked with Tailwind CSS, chances are you've used daisyUI. As one of the most popular Tailwind component libraries, it's valued for its sensible defaults, wide component set, and flexibility that feels native to Tailwind. Now, with the release of Tailwind CSS 4, the ecosystem is evolving - and daisyUI is keeping pace. Version 5 is more than an update: it's a complete rewrite built to be smaller, faster, and more customizable.
At Caktus, many of our projects use pip-tools for dependency management. Following Tobias' post How to Migrate your Python & Django Projects to uv, we were looking to migrate other projects to uv, but the path seemed less clear with existing pip-tools setups. Our requirements are often spread across multiple files, like this: $ find requirements/ -type f requirements/test/test.in requirements/test/test.txt requirements/deploy/deploy.txt requirements/deploy/deploy.in requirements/dev/dev.txt requirements/dev/dev.in requirements/base/base.in requirements/base/base.txt
