For nitpicking like that let me do some counter-nitpicking: please write 'Open Source (OSI)', 'Open Source (TM)' or at least capitalize it as 'Open Source' so that people know where you're coming from. The commonly used 'open source' just means 'the source is in the open'. Let's not allow organizations to hijack commonly used words.

You are absolutely right. I just changed the license to ELv2.

You are right. Thanks for the insights! I just changed the license to ELv2.

Great question! I actually have built a poc that is not released yet. It's on the roadmap. It requires some tooling for the devs building these plugins like a CLI for building the WASM binaries, bundling, manifests, etc.

The current poc still has significant performance overhead, and that overhead grows as the plugin system becomes more powerful. If plugins are only allowed to apply a WGSL shader, the performance impact is almost negligible. But features that require broader access to timeline data, such as time shifts, speed ramps, or full timeline transformations, become much more expensive and make zero-copy architectures harder to reason about.

I added CONTRIBUTING.md. I also took a look at OpenFX. My current view is that supporting OFX in the browser would be hard, since the standard and its existing tooling are not designed around wgpu or browser execution. Tooscut would likely need its own plugin model rather than adopting OFX as is.

That said, I would be very interested in hearing your thoughts if you are open to contributing or discussing what a practical plugin system should look like in this environment. Please file a GitHub issue if you can

Different use case. "Runs everywhere instantly" beats "installs + config" for a lot of workflows.

In my experience getting it to run on my Intel gpu on Linux was not trivial. And when I did I discovered it doesn't support standard video formats making it a complete non starter.

Kdenlive is much better imho for basic edits

+1 for Davinci Resolve. I used the free version for years (Windows and Mac versions) before finally picking up a copy of Studio which is still very reasonably priced and is a flat fee.

Browser editing makes sense for review links, shared projects, and zero-install onboarding, but if the job is just cutting footage fast on one machine then a desktop app will smoke it and the compatibility mess buys you nothing. The browser sandbox is a decent distribution hack, yet once you stack WebGPU, WASM, codecs, file access, and browser-specific bugs on top of each other, you are rebuilding a worse native stack with extra failure modes and pretending that counts as progress. Resolve exists.

Resolve requiring an account to download is what turned me away when I needed to do a quick edit the other day. Oracle much?

> And I really have to ask why we think the browser is the place to run this.

This is a big barrier if you want cross-compatibility and making Linux usable for everyday people. My whole interface is a terminal and a browser. I could use/pay for something like this in the same way I use figma. I don't need an app and when I open my iPad I can access whatever I was working on.

The browser should have been the place to run all of this from the very start; but Apple/Google decided to create walled gardens for their systems.

I stopped trusting resolve after they decided to paywall reactor. Putting a paywall on plugins that users contribute for free is just shitty.