As often with proprietary source code, it may include some third-party code or libraries that they have no right to redistribute, for example.
To "free" a repository, you must first audit the code for 3rd-party code and check the legal status of this code, and you may need to replace it with a free replacement, and find a license compatible with all the code. That may represent a significant effort, with associated costs...
But if it was taken by a third party, Opera aren't distributing anything, are they?
They probably have to do their due diligence to get it back or they are held liable. Who knows though.
"They" are not even "they" anymore. At this point, Opera is pretty much just a brand name making a mockery of the former program.
CEO is still the same. Presto developers have been laid off.
I don't know, its hard to describe how much Opera-when-they-still-made-their-rendering-engine-inhouse is or is not Opera-using-webkit-and-bought-by-Chinese.
Well, it's subjective of course, maybe I should have said "the things I liked about Opera". Those "dry" configuration dialogs that always seemed to go that extra mile, for example. I doubt Vivaldi is ever going to reach that level again, and their other offerings aren't even trying.
And how much is Opera TV, which is yet another company.
It's not being used in the desktop browser anymore, but some consumer electronics project still under maintenance are, and so is Opera mini.
You'd have to make completely sure there is no 3rd-party code in there you don't have a license for to redistribute. So usually, especially for old codebases, it's not that easy to simply open-source them, mostly for legal reasons.
They are still using it.
That the fork will outcompete current Blink-based Opera?
they would risk competitor using 1/4 memory, loading instantly, and with zero UI latency(load 40 tabs in anything Chromelike and then try fullscreening YT video- takes almost one second).