<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>oever</author><text>C++ and Rust are very different. A direct binding is near impossible. This project takes a pragmatic approach: the GUI part is QML&amp;#x2F;Qt and the logic part is Rust. The separation is quite strict. The demo application showcases more of the features than the blog does. Notably, the mapping between the Qt data models and the Rust code is something that makes development effective. This will be emphasized in the upcoming FOSDEM presentation.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;fosdem.org&amp;#x2F;2018&amp;#x2F;schedule&amp;#x2F;event&amp;#x2F;rust_qt_binding_generator&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;fosdem.org&amp;#x2F;2018&amp;#x2F;schedule&amp;#x2F;event&amp;#x2F;rust_qt_binding_gener...&lt;/a&gt;</text><parent_chain><item><author>d33</author><text>Is it just me or it feels way too ugly? Multiple opaque layers of abstraction plus Rust kind of feels shoehorned when it&amp;#x27;s called from C++. Something tells me it&amp;#x27;s terribly difficult to write, debug and deploy. I don&amp;#x27;t exactly see the benefit of adding Rust here.</text></item></parent_chain></comment><story><title>Rust and QML: a timely example</title><url>https://www.vandenoever.info/blog/2017/09/10/time_for_rust_and_qml.html</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>derefr</author><text>&amp;gt; I don&amp;#x27;t exactly see the benefit of adding Rust here.&lt;p&gt;From that perspective, there isn&amp;#x27;t any. Dyed-in-the-wool &amp;quot;QT app-devs&amp;quot;, if there is such a category (KDE devs?) already have access to Rust libraries, in the same way they have access to most stuff in weird compiled languages: you wrap the library in a C ABI and call that. It&amp;#x27;s a well-understood process in QT land.&lt;p&gt;I think this project is more an effort to give Rust projects access to a native graphics toolkit (that happens to be QT) for adding a GUI to a previously CLI application. I could see, for example, the Parity Ethereum client (written in Rust) getting a native system-tray&amp;#x2F;notification-area widget written in QT.</text><parent_chain><item><author>d33</author><text>Is it just me or it feels way too ugly? Multiple opaque layers of abstraction plus Rust kind of feels shoehorned when it&amp;#x27;s called from C++. Something tells me it&amp;#x27;s terribly difficult to write, debug and deploy. I don&amp;#x27;t exactly see the benefit of adding Rust here.</text></item></parent_chain></comment><story><title>Rust and QML: a timely example</title><url>https://www.vandenoever.info/blog/2017/09/10/time_for_rust_and_qml.html</url></story>