[Interest] Qt5, XCB and X11

[Roger Leigh]

On Tue, Jul 15, 2014 at 10:07:18AM +0000, Rutledge Shawn wrote:
> 
> On 12 Jul 2014, at 3:03 PM, Till Oliver Knoll wrote:
> 
> > Am 11.07.2014 um 20:52 schrieb Andreas Pakulat <apaku at gmx.de>:
> > 
> >> ...
> >> 
> >> Its true that it makes it harder, but it also means having to carry around more duplicated code. Recently had to add Qt5 libs for a dozen example apps we ship and that was not quite that easy to get up and running (without also shipping a dozen copies of Qt5 which frankly is a bit too much).
> > 
> > Yes, that's the downside of BYOL ("Bring Your Own Libraries") ;) And as I wrote earlier, kind of defeats the idea of "shared libraries" (in the best case the "application" consists of several binaries which share some libs among each orher).
> > 
> > But with spinning hard disks the size of terrabytes and SSDs the size of.... Hey! Wait a minute! ;)
> 
> But you probably don't have terabytes of RAM, and cache is limited too, and maybe the libraries still get loaded multiple times when you run multiple applications if they are actually different versions (or maybe even if they aren't).  I was thinking the solution to both problems might be some sort of deduplication by hashing, both in storage and in memory.  It could be done at a block level or at the level of individual functions.  It's probably a research project somewhere...

I had some thoughts about this a while back and wrote them up here:

http://nagini.codelibre.net/~rleigh/writing/hashlink.pdf

but lacked the time to actually start implementing it.  The above was
one of the use cases I wrote about briefly.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux    http://people.debian.org/~rleigh/
 `. `'   schroot and sbuild  http://alioth.debian.org/projects/buildd-tools
   `-    GPG Public Key      F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800