OpenShot represents the middle ground of the 3 editors I want to sample, being (I had assumed) the middle ground in terms of functionality, and also resource intensiveness, though this might not be strictly accurate – it was still a distinctive experience. Whilst KdenLive didn’t feel particularly dissimilar from Davinci Resolve or Premiere Pro, and you could migrate fairly comfortably – OpenShot is very different from those three programmes, but seems to be designed with approachability in mind. You can pretty much see, or at least understand where you should be looking, for every major tool or function you could be looking for. I instinctively went looking for a menu tree to find a certain function, then realised what I was looking for was accessible from the on screen options. Everything is very clearly displayed, there are previews for every transition and effect, you aren’t really expected to bring too much to the table. OpenShot is incredibly welcoming in that sense. I also appreciated that sometimes more sophisticated/complicated (depending on your disposition) systems will get in your way trying to help you. There are no such unnecessary automations here, and you are expected to be explicit in your operations. In terms of power, I didn’t feel like it was especially lightweight both in performance of the software, and performance of my battered old Thinkpad. Both served absolutely fine but it didn’t feel like I was running anything particularly lightweight. Where I think the problems ultimately lie, is that it is unique in how approachable it is designed to be, which is great in one sense. However if you needed to transition to a different editor in the future, your transition will not be as smooth as with Kdenlive. So I think its probably best suited to someone who does basic edits a handful of times a year, rather than someone completely new to editing looking for a tool to learn.