Urgent.News

What's breaking now, across thousands of outlets.

Tech

OBS Studio 33.0 Finally Pays Down Two Years of Technical Debt

The headline feature in OBS Studio 33.0 is not a feature at all. It is a two-year-old dependency finally getting replaced, a folder structure getting torn up, and a list of older software versions getting cut loose. That is the real story: the free streaming software most of the internet's broadcasters run is spending its next major version paying down debt it quietly built up rather than chasing…

OBS Studio 33.0's primary focus is on addressing technical debt accumulated over the past two years rather than introducing new features. This major update, which reached Release Candidate 1 on October 9, 2026, replaces a two-year-old browser engine, reorganizes plugin directories, and removes support for older FFmpeg and Qt versions.

The most noticeable change is the upgrade from CEF 127 to CEF 150, which brings the embedded Chromium browser engine up to date, closing a two-year gap in the underlying code. This change is primarily a backend update, meaning most users will likely not notice any difference. However, it does mean that browser sources may experience issues due to unpatched rendering-engine bugs or missing web-standard support.

Additionally, OBS is moving third-party plugins to new core and third-party directories, which could potentially break setups relying on specific plugins. While this update is primarily for developers and power users, it's important for anyone using OBS to confirm plugin compatibility before upgrading, especially those relying on third-party tools, overlays, or Linux builds.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Deploy a Hono backend on AWS Lambda without an adapter layer

A Hono app may already have a normal HTTP server, routes, middleware, and database calls. Moving that app to Lambda used to mean adapting the request lifecycle or adding a bridge layer.

  • Deploy Hono backend on AWS Lambda Web Functions without adapter layer.
  • Node.js HTTP server listens on port, using AWSLAMBDAHTTPENDPOINT.
  • Evaluate app's startup behavior, authentication, regions, and cost impact before deployment.

More from Wednesday 14 October →