Client side is the entire point that makes this project novel and awesome. It's obvious that the target use case is quick access to an editor in browser for easy video creation.

if i built this and an employer asked me why my project wasn't competitive with leading open source video editing software, i would probably cut the interview short. the vast majority of developers build stuff like this to learn and challenge themselves (which op basically says in the description), only a small fraction are attempting to build a viable product. i'd expect the interviewer to understand this dynamic and not grill me on the target audience for my toy project

If you are building any kind of tutorial/user content site, this could be quite a benefit for users + moderators.

Only if the prospective employer was confused and thought they were hiring a business exec rather than a developer.

That's not how things work: when you are hiring a software engineer/developer, you are not looking for someone to produce code by the spec (a "codemonkey"), but to question any assumptions and demands before commiting to them.

I wouldn't expect a "business exec" to worry about download/upload speeds (though I'd note that the claim here is that it's all locally running, so inefficient memory usage is likely a bigger deal), so a good software developer would partner on defining the roadmap.

The vast majority of software and businesses are replicative.

If you only hire devs working on unique businesses or those with a sound business case you won't find many. They'll probably be too busy running successful businesses.

Who said anything about "unique businesses"?

A developer that simply (and only) blindly builds what they are told is rarely a part of a successful team. This translates to technical implementation plans too, but I am highlighting that if you want to get hired, you should showcase how you balance opposing priorities, requirements and time.

And once you do, you'll be judged on them.

> I get that it's all client-side, but that is not an advantage to people working with video files, which are often large, and upload speeds are often the biggest bottleneck.

This comment seems strange to me, can you explain it better?

I would guess that for most video editing, source files will generally be either on some form of local storage, or will hosted with a cloud storage provider. Unless your server side editor is also providing your storage, I don't see how this is a benefit. Source files will generally be significantly largers so waiting on uploading material till after you have the finished result seems better for slow connections.