Linked by Thom Holwerda on Wed 13th Feb 2013 13:21 UTC
Thread beginning with comment 552392
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: Opera doesn't want to be populair
by telns on Wed 13th Feb 2013 22:58
in reply to "RE[5]: Opera doesn't want to be populair"
Umm... I have. I have done some custom [proof-of-concept] type projects using the Qt5WebKit codebase.
I like it just fine. But that doesn't mean that it will provide 100% of what Presto provides in a convenient way.
I would say exactly the same thing in reverse if someone were trying to take the Presto engine--which I am sure is also a good code base--and stick it into a long-term WebKit project.
Edited 2013-02-13 22:59 UTC
RE[7]: Opera doesn't want to be populair
by cdude on Thu 14th Feb 2013 15:32
in reply to "RE[6]: Opera doesn't want to be populair"





Member since:
2008-09-21
If there is demand for a certain feature they can and will add it. They have now even more forces to do so since lesser work on the rendering-engine is needed. If there is no demand then indeed, that feature may gone.
If you had a look at WebKit code and development you wouldn't argue about 10 inches deep layers nobody can touch. That's not reality. This isn't IE :-)
Edited 2013-02-13 21:52 UTC