title: Console application with signals, threads and network, Qt or POCO
body: <p>I have to develop a console application interacting with a Qt Gui via IPC. I already have a good experience with the Qt framework, I am completely new to POCO. I also need a good SQLite wrapper.</p>
  
  <p>What are the pros and cons of Qt vs Poco for my case ?</p>
  
  <p>So far, I've listed:</p>
  
  <p>Qt pros:</p>
  
  <ul>
  <li>very good documentation</li>
  <li>active community</li>
  <li>in my case, experience</li>
  <li>easy to use</li>
  <li>cross platform</li>
  <li>SQLite wrapper is nice</li>
  <li>Easy threading via signals and slots (no need of mutexes)</li>
  </ul>
  
  <p>Qt cons:</p>
  
  <ul>
  <li>lack of integration with standard C++, everything works with Qt objects (QString, etc.)</li>
  <li>Meta object compiler (MOC)</li>
  <li>New developer must learn the Qt framework to code</li>
  <li>Stick to GCC 4.2.1 on Mac instead of the latest clang shipped from now on with Mac</li>
  <li>Must inherit from QObject to use signals, threads, etc.</li>
  </ul>
  
  <p>Poco pros:</p>
  
  <ul>
  <li>easy to use ?</li>
  <li>faster for networking (Http in my case) ?</li>
  <li>No need of MOC</li>
  <li>builds with Clang seamlessly ?</li>
  <li>cross-platform</li>
  <li>easy threading ?</li>
  </ul>
  
  <p>Poco cons:</p>
  
  <ul>
  <li>lack of documentation !</li>
  <li>small community</li>
  <li>?</li>
  </ul>
  
  <p>I hope Qt5 will be usable with clang, llvm on mac ?</p>
  
  <p>I would very much appreciate your insight about this. </p>
  
  <p>Thanks.</p>