specification VS vidcutter

Here's a discussion with more comparisons: https://github.com/serverlessworkflow/specification/issues/2...

Once you have defined the workflow on a diagram, a JSON, following the Serverless workflow specification, is stored in KuFlow. With this specification, we can use all the great tools/libs that are developed.

Among workflow languages out there, we choose Serverless Workflow. It's a vendor-neutral, open-source and community-driven workflow ecosystem. The workflow definition can be written in JSON or YAML format. And then there are SDKs available in various programming languanges, like Java, Go, TypeScript, .NET, Python.

This example happens to be from Google, but you can compare similar config-driven syntaxes from Argo, Amazon, and Airflow. The bottom line is you ultimately find yourself hand-writing the Abstract Syntax Tree of something you can read much better in code anyway:

Check out losslesscut, vidcutter and avidemux.

Try out vidcutter, based on the popular media player mpv.

I use it to trim all my game clips. It also supports displaying HDR videos properly, something I'm not aware if similar programs like VidCutter have.

https://github.com/ozmartian/vidcutter give this a try, use it under Windows 11 as well as Arch Linux and works fine in both cases, the other option is Avidemux but for simple cutting and joining, this app is faster and easier to work with.