Announcement

Collapse
No announcement yet.

Qt 5.9.5 Doubles Qt Quick Performance On 64-bit ARM, 18x JavaScript Improvement

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

  • #11
    Originally posted by caligula View Post

    Ok that's true, but many modern toolkits use a non-native high level language as the glue layer. JVM langauges, .NET languages, Lua, Python, Perl, PHP, JS, Erlang, ...
    In an ideal world you'll use as little glue as possible, but in cases like that (for example, PHP) often what they'll do is cache the compiled scripts after the first run. For example, PHP nowadays will cache opcodes. While not 100% native or ideal, it's good enough for most usage.

    The real problem starting to leak in to modern computing is that a lot of novice developers are using scripts and foregoing compiled "native" languages. You're also getting these wrapped HTML5 "applications" which are primarily written in markup and script, almost treating native components as the glue. They can get these really pretty interfaces going fairly quickly and easily, but the moment you open a task manager you find Chromium processes eating your system alive... Blargh.

    Comment


    • #12
      Originally posted by Kver View Post
      The real problem starting to leak in to modern computing is that a lot of novice developers are using scripts and foregoing compiled "native" languages.
      Nailed it!

      Comment


      • #13
        Originally posted by carewolf View Post

        Well QML has been designed to integrate with C++, so any computational heavy stuff is done using C++, and any graphics is done with OpenGL, which leaves just a bit of glue.

        The problem is if people integrate bigger JS frameworks and tries to use that in QML, then it needs more performance, but it is technically using QML wrong.
        I have seen many examples using more QML than C++ code. My expectation has been that QML would only have the definition of the UI elements and bindings to C++ for all the interaction handling. However, that is not the case. JS is predominant is most examples I have seen and many don't contain C++ classes at all.

        Comment


        • #14
          Originally posted by Kver View Post

          In an ideal world you'll use as little glue as possible, .....

          The real problem starting to leak in to modern computing is that a lot of novice developers are using scripts and foregoing compiled "native" languages..
          In an ideal world Javascript would just be faster and you won't have to use it as little as possible.

          The real problem is that many "native" languages are actually quite terrible to program in. Go is an exception with an easy learning curve but it has a large overhead for calling C so that makes it unusable for this domain.

          Comment


          • #15
            Originally posted by msotirov View Post
            In an ideal world Javascript would just be faster and you won't have to use it as little as possible.
            In an ideal world there wouldn't be anything as horrible as Javascript. :/

            Comment

            Working...
            X