Hi, I'm an active user (and contributor to) PETSc and I wanted to ask a few questions on what you listed as Cons (always looking to improve the user experience
)Con - Not much of a users manual:We do have what we consider a good user's manual -- http://www.mcs.anl.gov/petsc/petsc-curr ... manual.pdf
. Do you think it can/needs to be improved? If so, how? We are always looking for constructive criticism.Con - Basic vector/matrix math is almost at the level of BLAS calls:It's true that Vec/Mat operations are not as easy as v = 1.0, etc. To some extent this is dictated by the distributed/high-performance nature of the library. And while I wouldn't characterize them as "at the level of BLAS", we are always looking to make the user experience easier.One step in that direction are (what we think as) very nice Python bindings to petsc: http://code.google.com/p/petsc4py/These
make many (not all) vector operations easier.Con - Primilary designed for high performance computing (clusters, etc)This is true, but I routinely run PETSc-based applications on my laptop. In fact, this is where most of my codes run :-)Furthermore, we are actively developing GPU and multithreading support.Con - Huge libraryThat may be so, but with diskspace being cheap these days, this isn't much of an impediment. We support shared libraries, dynamic loading and the splitting of our library into small components to alleviate the loading issue,should it arise.Con - Compilation on Windows is extremely difficult or impossibleActually, compilation on Windows, while can be hard, is far from extremely difficult, IMHO. We have many Windows users and provide essentially round-the-clock free and fast support email@example.comThis
is not intended as a criticism, but rather as an attempt at dialog with a potential user :-)Cheers,Dmitry.