<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jeena</author><text>And if we want to compare the syntax then this would be the QML equivalent:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  import QtQuick 2.9  
  import QtQuick.Controls 1.3  
  
  ApplicationWindow {  
    title: &amp;quot;Example&amp;quot;  
    visible: true  
    width: 300  
    height: 300

    Button {  
        text: &amp;quot;Button&amp;quot;  
        anchors.centerIn: parent  
        onClicked: console.log(&amp;#x27;Hello&amp;#x27;)  
    }  
  }&lt;/code&gt;&lt;/pre&gt;</text><parent_chain><item><author>WaltPurvis</author><text>&amp;gt;You can create a GUI using something like Qt, but the code to make it is messy and unorganized.&lt;p&gt;It doesn&amp;#x27;t serve the author well to make this comparison. Saying it&amp;#x27;s less messy to manage Proton&amp;#x2F;React source code files and the associated Node&amp;#x2F;JS&amp;#x2F;etc infrastructure is an extremely dubious claim. One of the things I like best about Qt is how non-messy Qt development is. Most everything (source files, resources, etc.) lives in a well-organized project that is easily managed using the Qt Creator IDE. The project structure is well-documented and standardized.&lt;p&gt;It&amp;#x27;s also quite strange to compare React code to code using the Python binding for Qt. That&amp;#x27;s not how most Qt apps are written. Most Qt apps these days use QML, which is based on regular old JavaScript. Besides being a more accurate representation of the way Qt development is normally done, it would also be more interesting to compare one JavaScript-based framework to another. (Although I recommend not making the comparison at all, since I don&amp;#x27;t believe a fair comparison would favor Proton.)</text></item></parent_chain></comment><story><title>Proton Native – React Native for the desktop</title><url>https://proton-native.js.org/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>stuffedBelly</author><text>I&amp;#x27;ve used Qt developing various data-heavy apps for financial research at work and agree that making this comparison is rather inappropriate. For people who are not familiar with JSX this is not any better than the Qt syntax. This would be an alternative to Qt, but before I see a full-fledging app developed with great performance&amp;#x2F;memory metrics using this, I am not convinced enough to put it in my framework stack.</text><parent_chain><item><author>WaltPurvis</author><text>&amp;gt;You can create a GUI using something like Qt, but the code to make it is messy and unorganized.&lt;p&gt;It doesn&amp;#x27;t serve the author well to make this comparison. Saying it&amp;#x27;s less messy to manage Proton&amp;#x2F;React source code files and the associated Node&amp;#x2F;JS&amp;#x2F;etc infrastructure is an extremely dubious claim. One of the things I like best about Qt is how non-messy Qt development is. Most everything (source files, resources, etc.) lives in a well-organized project that is easily managed using the Qt Creator IDE. The project structure is well-documented and standardized.&lt;p&gt;It&amp;#x27;s also quite strange to compare React code to code using the Python binding for Qt. That&amp;#x27;s not how most Qt apps are written. Most Qt apps these days use QML, which is based on regular old JavaScript. Besides being a more accurate representation of the way Qt development is normally done, it would also be more interesting to compare one JavaScript-based framework to another. (Although I recommend not making the comparison at all, since I don&amp;#x27;t believe a fair comparison would favor Proton.)</text></item></parent_chain></comment><story><title>Proton Native – React Native for the desktop</title><url>https://proton-native.js.org/</url></story>