Hi, Maybe it's me but I find the way you started this discussion extremely rude and at some point offensive. You jettison in here with random claims of ugliness and slowness and that acitve_record was a better fit. I don't know what you're trying to achieve but you might want to work on how you ask people for help or input in the future.
As far as the PuppetDB API's ugliness go, I can only disagree, As the author of pypuppetdb, puppetb-stencil and Puppetboard and probably the largest consumer of the PuppetDB API, it's been nice to work with. Yes it has a few things that could use improvement but that's mainly because it was designed as an API for machines to get data, not for humans to read. So, what exactly is your problem, how does the JVM worsen this and what is you gripe with the PuppetDB API? I'd like to see some metrics that prove your point about PuppetDB and the JVM. I'd also like to see some real examples of your gripes with the PuppetDB API. I'd also like to hear how PuppetDB complicates your testing? In both cases you need a database, PuppetDB even makes this easier because it can run in-memory. -- Daniele Sluijters -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/a4debfd7-968a-4f3d-ae46-2beed02f0312%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
