# Drivers Published articles for Drivers. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Removing Drivers For Outdated ARM Platforms Will Lighten The Kernel By ~247k Lines DevFeed: [Removing Drivers For Outdated ARM Platforms Will Lighten The Kernel By ~247k Lines]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-14T13:32:47Z Content type: news Language: en Sources: [Phoronix]() Topics: [Linux](), [Arm](), [Code](), [Git]() Tags: [code](), [desktop-linux](), [developer](), [drivers](), [git](), [kernel](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [platforms](), [source](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview Linux is removing support for obsolete 32-bit ARM platforms and their associated drivers. The changes could delete roughly 247,000 lines of code, likely in Linux 7.5, although the kernel source tree contains nearly 41 million lines overall. ### Source excerpt The Linux kernel is going to see the removal of a number of recently deprecated ARM 32-bit platforms. Following the deprecation in Linux 7.3, removing the old ARM platforms will lighten the kernel by around 55k lines of code. But removing now unused drivers only relevant to those platforms will mean roughly a quarter million lines of code can be removed from the kernel source tree... ## Linux 7.3-rc3 Released: "Another Fairly Large RC" DevFeed: [Linux 7.3-rc3 Released: "Another Fairly Large RC"]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-13T22:00:23Z Content type: news Language: en Sources: [Phoronix]() Topics: [Linux](), [Large Language Model](), [LLMs]() Tags: [desktop-linux](), [drivers](), [filesystem](), [gpu](), [kernel](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [llms](), [networking](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [release](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview Linux 7.3-rc3 is described as a relatively large release candidate, with substantial filesystem, driver, networking, and core-kernel fixes. The update includes an EROFS change disabling LZ4 rolling decompression because of potential data corruption, along with fixes affecting XFS, the SMB client, netfs, AFS, btrfs, sound drivers, GPU drivers, and several architectures. ### Source excerpt Out today is the third weekly release candidate of Linux 7.3 as this next kernel version works its way toward a stable release in the second half of October... ## Prominent Mesa Developer Now Working For Arm On PanVK & Panfrost Code DevFeed: [Prominent Mesa Developer Now Working For Arm On PanVK & Panfrost Code]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-11T12:55:26Z Content type: news Language: en Sources: [Phoronix]() Topics: [Arm](), [Code](), [3D graphics](), [Hardware](), [Open Source]() Tags: [3d](), [3d-graphics](), [arm](), [code](), [desktop-linux](), [developer](), [driver](), [drivers](), [graphics](), [hardware](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [ubuntu-benchmarks](), [ubuntu-hardware](), [vulkan]() ### AI overview Erik Faye-Lund has joined Arm after eight years at Collabora and will continue contributing to the upstream PanVK Vulkan driver and Panfrost Gallium3D driver for Arm Mali graphics. He also aims to improve Arm's collaboration with upstream projects. ### Source excerpt Erik Faye-Lund who has contributed to the Mesa 3D graphics driver stack working on areas like Zink and most notably the PanVK Vulkan and Panfrost Gallium3D drivers forr Arm Mali hardware is now working directly for Arm... ## How to calculate DevOps platform total cost of ownership DevFeed: [How to calculate DevOps platform total cost of ownership]() Original publisher: [Read original article]() Author: GitLab Published: 2026-09-11T00:00:00Z Content type: tutorial Language: en Sources: [GitLab]() Topics: [CI/CD]() Tags: [ai](), [ci-cd](), [complexity](), [compute](), [cost](), [devops](), [devsecops](), [devsecops-platform](), [drivers](), [how-to](), [infrastructure](), [integration](), [model](), [platform](), [reduce](), [software-delivery](), [tools]() ### AI overview A guide to modeling the total cost of ownership of a DevOps platform, including subscriptions, CI/CD compute, AI usage, infrastructure, tools, and internal labor. ### Source excerpt There's nothing like budget pressure to put your DevOps platform under a microscope. But subscription fees and license costs only tell one part of the story. The total cost of ownership (TCO) for a DevOps platform also includes variable costs like CI/CD compute and AI usage, along with the infrastructure, tools, and employee time required to keep software delivery moving. That wider view matters when you're tasked with defending platform spend or comparing options with a head of finance. Designing a useful TCO model can: Make those costs transparent for stakeholders Shine a light on the reasoning (or lack thereof) behind each cost Identify areas to reduce spend without negatively impacting software delivery What total cost of ownership really includes The core challenge of calculating TCO is that DevOps platforms package and price capabilities differently. For example, one platform may bundle CI/CD or AI capabilities into a per-seat subscription, while another could price usage separately. A third may appear less expensive upfront but require additional tools and ongoing integration work. That's why list prices or pricing tiers alone won't give you a useful comparison. Start with the capabilities and workloads your organization actually needs, then calculate what it takes to support them on each platform. Use the same scope and time period for every option -- often one year -- and define which teams, applications, environments, and delivery stages are included. Separate recurring costs from one-time expenses and external spend from internal labor, so finance can audit the assumptions and forecast future years. A useful TCO model, therefore, answers two questions: What does it cost to meet our requirements today? Which variables will cause that cost to rise or fall as our usage changes? The cost categories that drive your bill Most DevOps platform costs fit into the following categories: Cost categoryWhat it includesMain cost driverPlatform accessPaid seats, role-based ## Ubuntu 24.04.5 LTS Released With Linux 7.0 HWE Stack DevFeed: [Ubuntu 24.04.5 LTS Released With Linux 7.0 HWE Stack]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-10T17:49:03Z Content type: news Language: en Sources: [Phoronix]() Topics: [Ubuntu](), [Linux](), [Deployment](), [GPU](), [Hardware]() Tags: [deployment](), [desktop-linux](), [drivers](), [gpu](), [graphics](), [hardware](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [lts](), [open-source-graphics](), [packages](), [phoronix](), [phoronix-test-suite](), [release](), [ubuntu](), [ubuntu-benchmarks](), [ubuntu-hardware](), [updates]() ### AI overview Ubuntu 24.04.5 LTS is a new point release that includes recent stable updates and a hardware enablement stack based on Linux 7.0, Mesa 26.0 graphics drivers, and related packages. The update is intended to simplify initial installation on new systems and improve support for newer hardware. ### Source excerpt For those continuing to make use of the Ubuntu 24.04 Long Term Support "LTS" series, Ubuntu 24.04.5 LTS is out today as the newest point release... ## A sample use of the winstart.bat file in Windows 95 DevFeed: [A sample use of the winstart.bat file in Windows 95]() Original publisher: [Read original article]() Author: Raymond Chen Published: 2026-09-08T14:00:00Z Content type: article Language: en Sources: [Raymond Chen]() Topics: [Windows](), [Batch file]() Tags: [architecture](), [display](), [driver](), [drivers](), [graphics](), [history](), [multitasking](), [old-new-thing](), [post](), [windows]() ### AI overview The article explains a sample use of winstart.bat in Windows 95: starting the TIGA Communications Driver so 16-bit Windows can use high-resolution graphics modes. It notes that MS-DOS programs could not use TIGA modes and that multitasking TIGA graphics across Windows and MS-DOS sessions was unsupported. ### Source excerpt For a driver that needs high resolution mode only in Windows. The post A sample use of the winstart.bat file in Windows 95 appeared first on The Old New Thing. ## GSoC 2026 Final Report | Modernizing Haiku's Bluetooth Stack: HID Profile Implementation DevFeed: [GSoC 2026 Final Report | Modernizing Haiku's Bluetooth Stack: HID Profile Implementation]() Original publisher: [Read original article]() Author: mohammedrattia Published: 2026-09-06T12:00:24Z Content type: article Language: en Sources: [Haiku Project]() Topics: [Bluetooth](), [implementation]() Tags: [bluetooth](), [drivers](), [gsoc](), [gsoc2026](), [haiku](), [hid](), [implementation](), [input](), [report](), [software]() ### AI overview This final GSoC 2026 report describes work to improve Haiku's Bluetooth stack and implement the HID profile. It reports that Bluetooth mice and keyboards are functioning and that the core stack is ready for additional profiles, while noting that Low Energy Bluetooth remains unimplemented and further work is needed. ### Source excerpt Hello! Finally, GSoC is done for me. This is the final report for my project. The project was focused on improving the Bluetooth stack and making it useful. Hopefully, the Bluetooth stack is now in a much better state than before GSoC 2026. It still needs much work to be fully developed. However, currently Bluetooth mice and keyboards are functioning. In addition, the core of the stack is ready for implementing other profiles. This report will include the following: Project Overview What I Did Future Work Conclusion Project Overview The State of Bluetooth on Haiku Before GSoC 2026 Although the Bluetooth stack was outdated (based on version 2.0 and 2.1 of Bluetooth) before GSoC, it contained many core components that helped us focus less on starting from scratch and more on making the already built stack useful. However, that's true only for BR/EDR (Basic Rate / Enhanced Data Rate) Bluetooth, not Low Energy Bluetooth, which isn't implemented yet in Haiku. The BR/EDR Bluetooth core stack is divided into several core modules that provide services for the Bluetooth profiles, which in turn provide services to users like human interface devices, audio, file transfer, etc. Some of those core modules and their state in Haiku are: L2CAP: Functional, but needed some fixes. HCI (Host Controller Interface): Functional, but on an old Bluetooth version, as stated above. Transfer Layer (h2generic): Functional, but required further extension to cover vendor-specific devices. Preferences Application: Functional, but it lacked some features, such as changing the Bluetooth friendly name, canceling inquiry and pairing, and adding devices to a block list. Security Manager: Not complete; it's blended into the Bluetooth Server, and most of its functions were missing. Service Discovery Protocol (SDP): Not implemented. The state mentioned above meant the Bluetooth stack couldn't yet offer much practical functionality to users, because none of the Bluetooth profiles were implemented. In addi ## The hidden work of modernizing Malwarebytes DevFeed: [The hidden work of modernizing Malwarebytes]() Original publisher: [Read original article]() Author: Anna Tukhtarova Published: 2026-09-04T17:15:42Z Content type: article Language: en Sources: [Malwarebytes]() Topics: [.NET](), [migration](), [Endpoint Security & XDR](), [Operating system]() Tags: [diagnostics](), [drivers](), [endpoint-security](), [engineering](), [inside-malwarebytes](), [migration](), [modernization](), [net](), [security]() ### AI overview The article explains Malwarebytes' migration of its managed Windows components to .NET 10 and why runtime and dependency upgrades require security-feature-level rigor in endpoint software. ### Source excerpt Why disciplined dependency modernization is one of the highest-leverage engineering investments a security product can make. ## Kubernetes v1.37: DRA Updates DevFeed: [Kubernetes v1.37: DRA Updates]() Original publisher: [Read original article]() Author: Kashish Verma Published: 2026-09-03T18:30:00Z Content type: release Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [releases]() Tags: [api](), [devices](), [drivers](), [kubernetes](), [release](), [resource](), [updates]() ### AI overview Kubernetes 1.37 updates Dynamic Resource Allocation, including GA support for extended resources, device status reporting, stable device taints and tolerations, and a standardized NUMA-node device attribute. ### Source excerpt Kubernetes 1.37 is here and Dynamic Resource Allocation (DRA) keeps pushing past where it started! This release brings DRA Extended Resource support to GA, a milestone the team has been building toward for three straight releases. Several more features graduate to Beta or GA. A fresh batch of alpha features rounds out the release. I'll dive into what's new for DRA in Kubernetes 1.37! What's stable in 1.37 DRA Extended Resource support has graduated to GA. This is the mechanism that lets DRA drivers satisfy requests made through the traditional extended resource API, think example.com/gpu in a Pod spec, without requiring a separate device plugin alongside the DRA driver. An extended resource name can be set directly on a DeviceClass, and Pods requesting it get matched to a device through DRA with no ResourceClaim needed on the workload's part. It's been on a steady path since KEP acceptance in 1.34. Alpha landed in 1.35, Beta in 1.36, and now it's Stable. For cluster operators, this is what makes DRA adoption gradual. Existing workloads written against extended resources keep working unmodified while the backend allocation logic moves over to DRA. ResourceClaims status with possible standardized network interface data adds a devices field to ResourceClaim .status, letting DRA drivers report per-device status, including, for network devices, the interface name, MAC address, and IP addresses. This gives users and controllers visibility into device state that was previously invisible once a device was configured in a Pod, and makes it possible to build things like network services that rely on a device's reported IPs. DRA: device taints and tolerations is now Stable; DRA drivers can mark devices as tainted so they're skipped for new Pod scheduling, and cluster admins can apply the same taints cluster-wide via a DeviceTaintRule, without reconfiguring drivers. Pods already using a tainted device can be evicted automatically, unless their ResourceClaim explicitly tolerates ## Troubleshoot AWS Advanced JDBC Wrapper configuration for Aurora Global Database write forwarding DevFeed: [Troubleshoot AWS Advanced JDBC Wrapper configuration for Aurora Global Database write forwarding]() Original publisher: [Read original article]() Author: Hema Saminathan Published: 2026-09-03T16:26:20Z Content type: tutorial Language: en Sources: [AWS Database Blog]() Topics: [configuration](), [Database](), [MySQL](), [Latency]() Tags: [advanced-300](), [amazon-aurora](), [aws](), [drivers](), [global](), [latency](), [mysql](), [postgresql](), [technical-how-to]() ### AI overview A configuration troubleshooting guide for the AWS Advanced JDBC Wrapper with Aurora Global Database write forwarding. It explains Region-specific settings for primary and secondary Regions, including MySQL-specific write-forwarding behavior. ### Source excerpt Configuring the AWS Advanced JDBC Wrapper for Amazon Aurora Global Database with write forwarding requires Region-specific settings, and misconfiguration causes latency spikes and connection failures. This post walks through the correct dialect, plugins, host patterns, and write forwarding settings for the primary and secondary Regions. ## A Self-Baked Async FFI Framework for Rust C# Interop DevFeed: [A Self-Baked Async FFI Framework for Rust C# Interop]() Original publisher: [Read original article]() Author: Cynthia Dunlop Published: 2026-08-31T13:00:34Z Content type: article Language: en Sources: [ScyllaDB]() Topics: [Rust](), [Tokio](), [.NET](), [C#](), [scylladb](), [For the Love of Code]() Tags: [c-sharp](), [drivers](), [engineering](), [hackathon](), [interop](), [rust](), [scylladb]() ### AI overview The article describes ScyllaDB's effort to build a Rust-based driver architecture with thin language-binding layers, focusing on a C# driver. It explains the motivation for creating a custom asynchronous FFI framework to connect Rust's Tokio runtime with .NET's async runtime over the C ABI, after existing binding-generation tools proved insufficient for Rust-C# async interoperation. ### Source excerpt How we got tokio and .NET's async runtime talking to each other, over the C ABI ## Building a New Rust Driver for ScyllaDB's DynamoDB API - with 58% More Throughput DevFeed: [Building a New Rust Driver for ScyllaDB's DynamoDB API - with 58% More Throughput]() Original publisher: [Read original article]() Author: Cynthia Dunlop Published: 2026-08-27T13:10:38Z Content type: article Language: en Sources: [ScyllaDB]() Topics: [SDKs](), [networking]() Tags: [alternator-for-dynamodb](), [api](), [benchmarking](), [drivers](), [engineering](), [optimization](), [performance](), [routing](), [rust]() ### AI overview The article describes a dedicated Rust driver for ScyllaDB Alternator that load-balances DynamoDB-style requests across cluster nodes. It also covers extending the Latte benchmarking tool for the DynamoDB API and reports approximately 58% higher throughput than the AWS SDK driver on a three-node cluster. ### Source excerpt How our new Rust driver load-balances DynamoDB-style requests across a ScyllaDB cluster, and how we extended Latte to measure its performance ## XCP-ng 8.3 LTS: Refreshed Installation ISOs DevFeed: [XCP-ng 8.3 LTS: Refreshed Installation ISOs]() Original publisher: [Read original article]() Author: Gaël Duperrey Published: 2026-08-14T08:09:13Z Content type: release Language: en Sources: [XCP-ng Blog]() Topics: [Server](), [Hardware](), [networking](), [Disk image]() Tags: [amd](), [drivers](), [hardware](), [improvements](), [installation](), [iso](), [linux](), [lts](), [networking](), [numa](), [performance](), [release](), [security](), [server](), [storage](), [update](), [updates]() ### AI overview XCP-ng 8.3 LTS has refreshed installation ISOs containing updates released since the previous installer, installer improvements, enhanced hardware support, and other fixes. The article notes that existing up-to-date hosts already include these changes. ### Source excerpt Refreshed ISOs for XCP-ng 8.3 LTS featuring the latest security updates, improvements, and QCOW2 support. ## ESP-BSP Generator helps create custom-board BSP components from Espressif development kits DevFeed: [ESP-BSP Generator helps create custom-board BSP components from Espressif development kits]() Original publisher: [Read original article]() Author: John Lee Published: 2026-06-30T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Espressif](), [ESP-IDF](), [Hardware](), [Web](), [Development](), [ESP32-C3](), [ESP32-S3](), [m5stack]() Tags: [apis](), [blog](), [bsp](), [configuration](), [dependency](), [devkit](), [drivers](), [esp-bsp](), [esp-idf](), [esp32](), [esp32-c3](), [espressif](), [hardware](), [m5stack](), [web]() ### AI overview The ESP-BSP Generator is a web tool that helps developers create an ESP-IDF BSP component for a custom board. Users can start from an esp-bsp development kit, customize hardware details such as pins and features, and download a reusable BSP component. ### Source excerpt Start from an esp-bsp dev kit, customize pins and features in a web form, and download a production-style BSP component for your custom PCB - same APIs, less manual work. ## FishMonger's arsenal upgraded: SprySOCKS for Windows DevFeed: [FishMonger's arsenal upgraded: SprySOCKS for Windows]() Original publisher: [Read original article]() Author: ESET Research Published: 2026-06-16T08:54:04Z Content type: article Language: en Sources: [WeLiveSecurity]() Topics: [backdoor](), [Processes](), [telemetry]() Tags: [analysis](), [apt](), [backdoor](), [china](), [communication](), [drivers](), [eset-research](), [government](), [kernel](), [linux](), [malware](), [process](), [processes](), [telemetry](), [virustotal](), [windows]() ### AI overview ESET reports two previously undocumented Windows variants of the SprySOCKS backdoor attributed to FishMonger. The variants use TCP, UDP, and WebSocket communications; WIN_DRV uses a kernel driver to conceal artifacts and redirect specially crafted TCP traffic. ### Source excerpt ESET researchers have discovered SprySOCKS for Windows, FishMonger's backdoor weaponizing a kernel driver for advanced stealthiness ## Developing a Zephyr IoT app with AI DevFeed: [Developing a Zephyr IoT app with AI]() Original publisher: [Read original article]() Author: John Lee Published: 2026-06-15T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [AI Agent](), [Embedded Software Dev](), [Internet of things](), [Artificial Intelligence](), [cursor](), [Testing](), [C](), [Git](), [Open Source](), [real-time]() Tags: [agent](), [ai](), [ai-agent](), [blog](), [code](), [coding](), [cursor](), [development](), [drivers](), [embedded](), [esp](), [esp-idf](), [espressif](), [experiment](), [firmware](), [git](), [how-to](), [iot](), [llm](), [m5stack](), [testing](), [workflow](), [zephyr]() ### AI overview This article describes applying an AI-agent workflow to develop a Zephyr-based IoT application on the ESP DualKey kit from M5Stack. It emphasizes specifications, project boundaries, Git discipline, testing, and bench validation while moving the implementation from ESP-IDF and Rust to Zephyr C. ### Source excerpt Still on improving our AI-based, embedded software workflow, this article applies the same AI-agent discipline to Zephyr. Using the same ESP Dualkey kit from M5Stack, specs, integration rules, plan->execute->commit->test, reusable modules, journals, and Git - without redefining the product. ## Neon for Agent Platforms: A Companion Skill for the AI Agent Program DevFeed: [Neon for Agent Platforms: A Companion Skill for the AI Agent Program]() Original publisher: [Read original article]() Author: Savannah Longoria Published: 2026-05-22T09:00:00Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [AI Bots]() Tags: [agent](), [agent-skill](), [agents](), [ai](), [ai-agent](), [api](), [api-keys](), [app](), [auth](), [compute](), [customer](), [database](), [databases](), [dev](), [development](), [docs](), [drivers](), [integration](), [mcp](), [postgres](), [product]() ### AI overview Neon introduces a companion skill for agent platforms that manage database fleets. It covers multi-organization provisioning, project transfers, branch-based environments and checkpoints, consumption tracking, and runnable TypeScript samples. ### Source excerpt We've been working on neon-for-agent-platforms, a companion skill that complements our existing neon-postgres skill. The existing skill covers auth, drivers, branching, the Data API, MCP, and core Postgres-on-Neon guidance. Agent platforms have a different problem though: they don't just use one database, they provision and operate fleets of them. ## Kubernetes v1.36: More Drivers, New Features, and the Next Era of DRA DevFeed: [Kubernetes v1.36: More Drivers, New Features, and the Next Era of DRA]() Original publisher: [Read original article]() Author: The DRA team Published: 2026-05-07T18:35:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [Hardware](), [systems](), [networking](), [Availability]() Tags: [availability](), [drivers](), [feature](), [hardware](), [infrastructure](), [kubernetes](), [release](), [resource](), [resources](), [systems](), [v1]() ### AI overview Kubernetes v1.36 advances Dynamic Resource Allocation (DRA) with feature graduations, broader driver support, and improved handling of hardware and native resources. The article covers prioritized device requests, extended resource compatibility, partitionable devices, and support for sharing specialized hardware across workloads. ### Source excerpt Dynamic Resource Allocation (DRA) has fundamentally changed how platform administrators handle hardware accelerators and specialized resources in Kubernetes. In the v1.36 release, DRA continues to mature, bringing a wave of feature graduations, critical usability improvements, and new capabilities that extend the flexibility of DRA to native resources like memory and CPU, and support for ResourceClaims in PodGroups. Driver availability continues to expand. Beyond specialized compute accelerators, the ecosystem includes support for networking and other hardware types, reflecting a move toward a more robust, hardware-agnostic infrastructure. Whether you are managing massive fleets of GPUs, need better handling of failures, or simply looking for better ways to define resource fallback options, the upgrades to DRA in 1.36 have something for you. Let's dive into the new features and graduations! Feature graduations The community has been hard at work stabilizing core DRA concepts. In Kubernetes 1.36, several highly anticipated features have graduated to Beta and Stable. Prioritized list (stable) Hardware heterogeneity is a reality in most clusters. With the Prioritized list feature, you can confidently define fallback preferences when requesting devices. Instead of hardcoding a request for a specific device model, you can specify an ordered list of preferences (e.g., "Give me an H100, but if none are available, fall back to an A100"). The scheduler will evaluate these requests in order, drastically improving scheduling flexibility and cluster utilization. Extended resource support (beta) As DRA becomes the standard for resource allocation, bridging the gap with legacy systems is crucial. The DRA Extended resource feature allows users to request resources via traditional extended resources on a Pod. This allows for a gradual transition to DRA, meaning cluster operators can migrate clusters to DRA but let application developers adopt the ResourceClaim API on their own sche ## Uber uses OpenAI to help people earn smarter and book faster DevFeed: [Uber uses OpenAI to help people earn smarter and book faster]() Original publisher: [Read original article]() Published: 2026-05-06T00:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [AI, ML & Data Engineering](), [Language models]() Tags: [ai](), [drivers](), [language-models](), [machine-learning](), [openai](), [voice]() ### AI overview Uber describes using OpenAI models for AI assistants and voice features that help drivers assess earning opportunities and help riders book faster. Its Uber Assistant converts marketplace data such as earnings trends and heatmaps into actionable insights and supports plain-language follow-up questions. ### Source excerpt Uber uses OpenAI to power AI assistants and voice features that help drivers earn smarter and riders book faster across a global real-time marketplace. ## Beyond A/B Testing: Using Surrogacy and Region-Splits to Measure Long-Term Effects in Marketplaces DevFeed: [Beyond A/B Testing: Using Surrogacy and Region-Splits to Measure Long-Term Effects in Marketplaces]() Original publisher: [Read original article]() Author: Iraklikhorguani Published: 2026-03-25T13:56:39Z Content type: article Language: en Sources: [Lyft Engineering - Medium]() Topics: [A/B Testing](), [App](), [Optimization]() Tags: [a-b-testing](), [app](), [cost](), [drivers](), [driving](), [growth](), [optimization](), [payments](), [pricing](), [resources](), [revenue](), [testing]() ### AI overview Lyft describes why standard A/B tests may not capture the long-term and market-mediated effects of pricing, payments, and incentive decisions in its multi-sided marketplace. The article introduces surrogacy and region splits as approaches for measuring those effects. ### Source excerpt Image generated with Gemini 3 Pro (Google), 2026. Written by Amber Wang and Yoonji Kim at Lyft. Background Whenever you use the Lyft app, there is a complex balancing act happening behind the scenes. Various levers are used to keep the marketplace running smoothly; Base prices and coupons for riders affect demand, while driver pay and bonuses impact the level of available supply. Since every change to prices and payments impacts Lyft's costs and revenue, they lead to key optimization problems, such as: How should we allocate budget between driver incentives and rider incentives? How do we invest resources to achieve x% rides growth, and how much does it cost in terms of short term profit? These are the questions the Foundational Models team at Lyft tries to answer in a systematic way. A key ingredient is understanding the effects of different types of investments -- for instance, what will happen if we increase the total budget for driver incentives by x%? What will happen if we increase the rider price of all rides by y%? It's worth noting that the long term effects of such decisions tend to dominate the short term effects: we may earn more short term profit from a ride if we charge riders more and pay drivers less, but lose riders and drivers in the long run. Estimating the long term effects of resource allocation decisions is challenging in a multi-sided marketplace such as Lyft. Because these decisions tend to be consequential, their effects go beyond first order effects on directly affected users. For example, if we increase driver incentive spending by x% in week 1, drivers will drive more in week 1 (short term effect), and may return to drive a bit more in the following weeks (direct long term effects). But this is not the full picture: in week 1, when there is a positive increase in driver hours as the result of more incentives, riders will enjoy better experiences (e.g. less surge pricing, shorter wait times) and may want to return to Lyft in the future. How ## Fixing black screens after suspend on Ubuntu 25.10 with NVIDIA 580 drivers DevFeed: [Fixing black screens after suspend on Ubuntu 25.10 with NVIDIA 580 drivers]() Original publisher: [Read original article]() Author: Ivan Morgillo Published: 2025-12-11T09:18:40Z Content type: tutorial Language: en Sources: [Ivan Morgillo]() Topics: [Nvidia](), [Ubuntu](), [boot](), [Kernel](), [xfce]() Tags: [black-screen](), [config](), [driver-fix](), [drivers](), [grub](), [kernel](), [linux](), [nvidia](), [suspend](), [ubuntu](), [updates](), [xfce]() ### AI overview This tutorial describes a black screen occurring when an Ubuntu system resumes from suspend with NVIDIA drivers. For Ubuntu 25.10 and NVIDIA 580 drivers, it reports that disabling NVIDIA DRM modesetting in the GRUB configuration resolved the issue and preserved the XFCE session after wake-up. ### Source excerpt Every now and then I update Ubuntu, sip my coffee, install all-the-things... and everything looks fine. Until I suspend. Because of course the moment the PC suspends, NVIDIA decides to have an existential crisis. I start the machine again and black screen. GODDAMMIT! This happened again today, and because Future Me will not remember any [...] ## Introducing Elephantshark, a tool to monitor Postgres network traffic DevFeed: [Introducing Elephantshark, a tool to monitor Postgres network traffic]() Original publisher: [Read original article]() Author: George MacKerron Published: 2025-09-24T16:33:15Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Databases](), [Logging](), [Parsing](), [Open Source](), [Ruby](), [Command-line interface]() Tags: [drivers](), [github](), [logging](), [logs](), [monitor](), [network](), [open-source](), [parsing](), [postgres](), [protocol](), [ruby](), [ssl](), [terminal](), [tls](), [tool]() ### AI overview Elephantshark is an open-source Ruby script from Neon for monitoring, understanding, and troubleshooting Postgres network traffic. It sits between communicating parties, forwards Postgres-protocol messages, parses and logs them, and can decrypt and re-encrypt SSL/TLS connections so traffic can be inspected or captured for Wireshark. ### Source excerpt Elephantshark helps you monitor, understand and troubleshoot Postgres network traffic: that's Postgres servers, clients, drivers and ORMs talking to Postgres servers, proxies and poolers. Elephantshark sits between the two parties in a Postgres-protocol exchange, forwarding messa... ## Firestore with MongoDB compatibility is now generally available DevFeed: [Firestore with MongoDB compatibility is now generally available]() Original publisher: [Read original article]() Author: Morgan Chen; Tyler Crowe; Minh Nguyen Published: 2025-08-26T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firestore](), [MongoDB](), [Firebase](), [Databases](), [Cloud]() Tags: [announcement](), [api](), [availability](), [cloud](), [code](), [data](), [database](), [drivers](), [enterprise](), [firebase](), [firebase-cli](), [firebase-console](), [firestore](), [launch](), [mongodb](), [release]() ### AI overview Firestore with MongoDB compatibility has reached general availability in Firebase through the Firestore Enterprise edition. It supports existing MongoDB application code, drivers, libraries, and tools, along with expanded query capabilities, data types, indexes, and performance improvements. ### Source excerpt Announcing the general availability release of Firestore with MongoDB compatibility ## New SDKs for Python and SQLAlchemy DevFeed: [New SDKs for Python and SQLAlchemy]() Original publisher: [Read original article]() Author: Levy Albuquerque Published: 2025-06-10T00:00:00Z Content type: release Language: en Sources: [Turso Blog]() Topics: [SDKs](), [migration]() Tags: [aws](), [database](), [drivers](), [fly-io](), [github](), [libsql](), [migration](), [python](), [sdks](), [sqlalchemy](), [turso]() ### AI overview Turso announces official Python SDKs for libsql and SQLAlchemy. Users should upgrade before older websocket-based drivers stop working after the stated migration deadline. ### Source excerpt Turso ships new official Python SDKs: 'libsql' and 'sqlalchemy-libsql'. Upgrade before June 18 when older websocket-based drivers stop working on AWS. [Next page]()