Announcement

Collapse
No announcement yet.

Rekonq 2.0 KDE Web-Browser Brings New Features

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Just to mention, JS has no multithreading support and trying to run scripts concurrently is going to get you bucketloads of deadlock or way too much overhead trying to put locks on every variable. Also, most web pages are limited to loading by the download rate, not the rendering speed. Performance in technologies like webgl and html5 is based more on how the underlying tools are implemented below the programming on a page (albeit, you can easily make a page run like barf).

    Comment


    • #17
      Originally posted by zanny View Post
      Just to mention, JS has no multithreading support and trying to run scripts concurrently is going to get you bucketloads of deadlock or way too much overhead trying to put locks on every variable. Also, most web pages are limited to loading by the download rate, not the rendering speed. Performance in technologies like webgl and html5 is based more on how the underlying tools are implemented below the programming on a page (albeit, you can easily make a page run like barf).
      Newer javascript implementations do support creating worker threads. You have to program that explicitly, of course, since the runtime assumes a single-threaded environment by default.

      I think webkit 2 was supposed to introduce a lot of threading support, wasn't it? Has Safari switched over to the new API yet? I don't think any of the other browsers using webkit have.

      Comment


      • #18
        Originally posted by Xeno View Post
        Multi-threaded rendering iirc is webkit2 feature, so we have to wait for qt5-based release.
        Qt-4.8.4 uses QtWebkit-2.2. Qt5 updated to 2.3, which brings that multithreaded rendering (and MANY fixes). There were discussions about a seperate QtWebkit-package, that could bring 2.3 to Qt-4.8*, but I never read about it again.
        That would be a great option for Qt5, too, because WebKit is the critical part for security of the browser, so it really should get updates whenever there was a security issue. Currently QtWebkit only get's updates with Qt-updates, which is only one in several months.

        Comment


        • #19
          Originally posted by schmalzler View Post
          Qt-4.8.4 uses QtWebkit-2.2. Qt5 updated to 2.3, which brings that multithreaded rendering (and MANY fixes).
          QtWebKit 2.2 does not use WebKit2. At some point there was the suggestion to rebrand QtWebKit to WebKit-Qt to make a clearer distinction between WebKit-Qt 2.2 and WebKit2-Qt 1.x but the suggestion was completely ignored by the relevant people (no idea whether on purpose or accidentally).

          Comment


          • #20
            Reqonq is on version 2.0?

            I remember last using it on version 0.8
            It's amazing how time flies!

            Comment


            • #21
              Originally posted by schmalzler View Post
              Qt-4.8.4 uses QtWebkit-2.2. Qt5 updated to 2.3, which brings that multithreaded rendering (and MANY fixes). There were discussions about a seperate QtWebkit-package, that could bring 2.3 to Qt-4.8*, but I never read about it again.
              That would be a great option for Qt5, too, because WebKit is the critical part for security of the browser, so it really should get updates whenever there was a security issue. Currently QtWebkit only get's updates with Qt-updates, which is only one in several months.
              Qt 5 has QtWebKit 3.0 I believe, QtWebKit 2.3 is specifically for Qt 4.8, but I haven't packaged it yet (was waiting for Qt 5.0 to release so it can follow the same branch), but you can get it as a git checkout.

              Comment

              Working...
              X