I use gramps fairly extensively for some semi-serious genealogy work and love it. It is extremely flexible, while also trying to remain true to standards such as GEDCOM.
One thing I love is that, as a python programmer, I can script various operations. This prevents some tedium with some things like inputting censuses or making sure images have the correct links to citations, etc.
So even though it is pretty friendly, it's also very power user friendly.
> It is extremely flexible, while also trying to remain true to standards such as GEDCOM.
I'm not overly familiar with gramps, but with GEDCOM, in my experience, it's sort of pick flexible or use the standard, not both.
For example, the GEDCOM has no way of interlinking relationships across generations. That is, someone cannot be both daughter and spouse, at the same time, which unfortunately isn't that rare an occurrence if you go back a few generations. (You can theoretically construct an XREF:INDI: that points to the one individual, but it breaks every parser when the pointer appears in both the descendants, and other relationships).
The Gramps Project introduced a custom XML format for storing & describing data. It doesn't rely on GEDCOM, although it can import/export that GEDCOM as a legacy format.
> You can theoretically construct an XREF:INDI: that points to the one individual, but it breaks every parser when the pointer appears in both the descendants, and other relationships
I read that as a bug in many implementations, not in the standard. Do you agree?
One thing I love is that, as a python programmer, I can script various operations. This prevents some tedium with some things like inputting censuses or making sure images have the correct links to citations, etc.
So even though it is pretty friendly, it's also very power user friendly.