Nepomuk

[Steve Riley]

I suspect some of bloat, and a contributor to the claims that KDE "feels 
slow," has to do with the sheer number of databases. I'm experimenting with 
building a KDE system by hand. So far, three separate databases are installed:

* MySQL for Akonadi
* Sqlite for Quassel
* Virtuoso for Nepomuk

Quassel is hardcoded to depend on Sqlite. Akonadi can be switched to that as 
well, but some docs on KDE.org warn against that, claiming performance will 
suffer. Nepomuk is similarly wedded to Virtuoso through Soprano. Surely there 
has to be a better way.

--Steve


On Sunday 18 December 2011 09:39:28 Lindsay Mathieson wrote:
> 
> A few months back I saw a post on a nepomuk  developers blog re the fact
> that:
> 
> - external interfaces were poorly or not documented and frequently changed
> 
> - return codes/exceptions were undocumented and frequently changed
> 
> - errors went largely unlogged and were ignored
> 
> - logging in general was almost non-existent
> 
> 
> I commented that this was a recipe for disaster - in the large corporate
> projects I worked on it was essential for core services to be well
> documented and *essential* for them to log every error, especially
> unexpected ones. It paid off in spades when you were trying to debug weird
> shit happening on the various remote and obscure setups we had to work
> with.
> 
> Sure you have to keep service specifications flexible, especially in
> development as new requirements/problem emerge, but you also have to be able
> to say  enough is enough and tie it down. And always always document and
> make it transparent.
> 
> My comment was deleted.
> 
> --
> Lindsay
> 
> --
> kubuntu-users mailing list
> kubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-users