<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet title="XSL formatting" type="text/xsl" href="https://www.vuntz.net/journal/feed/rss2/xslt" ?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>mon journal - par Vincent - Letter from Akademy      - Comments</title>
    <link>https://www.vuntz.net/journal/</link>
    <atom:link href="https://www.vuntz.net/journal/feed/rss2/comments/485" rel="self" type="application/rss+xml" />
    <description>mon journal - par Vincent</description>
    <language>en</language>
    <pubDate>Mon, 09 Feb 2026 20:56:34 +0000</pubDate>
    <copyright></copyright>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <generator>Dotclear</generator>
                        <item>
          <title>Letter from Akademy - Vincent</title>
          <link>https://www.vuntz.net/journal/post/2008/08/10/485-letter-from-akademy#c2392</link>
          <guid isPermaLink="false">urn:md5:8cf655dacea68855e48ff5648ac896b0</guid>
          <pubDate>Tue, 12 Aug 2008 12:44:04 +0000</pubDate>
          <dc:creator>Vincent</dc:creator>
          <description>&lt;p&gt;T.J.: your question probably need a proper reply, which needs quite some time. Unforunately, I don't have that time right now. But the basic answer is that it's not going to happen for various reasons. The jump to GTK+ 3 will be minor for application developers (even with the API/ABI breaks), while switching to Qt would be a huge task that would take years. There are also other things to consider like licensing (we like LGPL for our platform, and Qt is GPL), just to give one example among many others.&lt;br /&gt;
&lt;br /&gt;
Anonymous: I didn't especially notice differences during Akademy. I probably wasn't clear: what I noticed what was similar -- I already knew about (most of) our differences.&lt;/p&gt;</description>
        </item>
                              <item>
          <title>Letter from Akademy - Anonymous</title>
          <link>https://www.vuntz.net/journal/post/2008/08/10/485-letter-from-akademy#c2391</link>
          <guid isPermaLink="false">urn:md5:3459f7df970a3d8a8dd65f06b6be2e32</guid>
          <pubDate>Mon, 11 Aug 2008 13:29:22 +0000</pubDate>
          <dc:creator>Anonymous</dc:creator>
          <description>&lt;p&gt;&amp;gt; there are certainly big differences between our two communities&lt;br /&gt;
&lt;br /&gt;
Which did you notice at the conferences?&lt;/p&gt;</description>
        </item>
                              <item>
          <title>Letter from Akademy - T. J. Brumfield</title>
          <link>https://www.vuntz.net/journal/post/2008/08/10/485-letter-from-akademy#c2390</link>
          <guid isPermaLink="false">urn:md5:62e8a6667b54fbebd85454f8de6569ce</guid>
          <pubDate>Sun, 10 Aug 2008 23:07:14 +0000</pubDate>
          <dc:creator>T. J. Brumfield</dc:creator>
          <description>&lt;p&gt;I'm curious what you think about Mark Shuttleworth's comments about Gnome possibly being built on top of QT in the future.  QT ships with a Clearlooks engine, and from what I continually here, QT themes are easier to develop.  In theory, one could write a QT app to look and operate exactly like existing Gnome apps.&lt;br /&gt;
&lt;br /&gt;
If the Gnome community is at a point where there is serious discussion about breaking ABIs/APIs and looking towards the long-term future, if ever there was a time to talk about such a concept, wouldn't it be now?&lt;br /&gt;
&lt;br /&gt;
I think there are some amazing potential advantages.  All apps would look the same and integrate into either desktop.  Theming would be easier.  It would cut down on some redundant projects that aim to make the same app in the GTK and QT worlds.  Instead of writing a new GTK 3 from the ground up, you could start focusing on Gnome libs almost immediately with an existing toolkit that would provide most of what you need immediately, and a toolkit that offers some very good performance.&lt;/p&gt;</description>
        </item>
            </channel>
</rss>
