I take that you've never actually tried using it on Linux. The free version is pretty much the worst free video editor on Linux.
Both the free and premium versions are heavily crippled with virtually all common encoders and decoders either restricted or totally unavailable.
It also doesn't even start unless you have an Nvidia card and use closed source proprietary drivers. Despite all the users (paid or unpaid) reporting the issues on Intel and AMD, they just ignore them. And even if they fix those issues, H.264/H.265 encoding (premium-only) is only possible with NVENC with no CPU encoding alternative.
Well, is it any better than Adobe's bs h264 encoder which is visibly worse at the same bitrate than any open source solution? What good does it do to include an encoder if it can only do bad quality? (Where does all that subscription money even going, Adobe? Adding more bugs and bad quality code?) We'll have to re-encode everything after the Adobe step anyway... (Also Adobe doesn't support Linux at all of course, so it's hard to compare there already...)
I mentioned two things: (1) the bigger issue, h264 decoder, Cisco already paid royalties for OpenH264 (when linked to their binary) so they simply have no real excuse for not having H264 decoding on Linux (2) lack of CPU encoder on Linux (it's not clear to me why you're bringing up Adobe since it has nothing to do with encoding on Linux), x264 is the gold standard for encoding H.264. NVENC isn't. The x264 binary can be shipped with proprietary products and they also offer a licensing option for linked usage. Similar comparison (NVENC vs x265) goes for H.265.
You are right, I guess they could make a better product. My point was that BM is still the company (maybe even the only one?) that gives most to Linux world, of all the big media software companies. A free version of an editor of the top tier that is Resolve, supported (!) on some version of Linux, is just unheard of.
My other point was to show that other comparable companies are also having issues with encoding output, that this aspect is not always taken seriously for some reason.
And yes, NVENC sucks and AFAIK it is impossible to configure it to produce the same resulting quality (per Mbps) of encoding than what is possible x264/x265, regardless of whether one wants to sacrifice encoding time or not.
Both the free and premium versions are heavily crippled with virtually all common encoders and decoders either restricted or totally unavailable.
It also doesn't even start unless you have an Nvidia card and use closed source proprietary drivers. Despite all the users (paid or unpaid) reporting the issues on Intel and AMD, they just ignore them. And even if they fix those issues, H.264/H.265 encoding (premium-only) is only possible with NVENC with no CPU encoding alternative.