On Monday, January 5, 2015 5:57:35 PM UTC+1, jcbollinger wrote: > > > > On Friday, January 2, 2015 3:49:25 AM UTC-6, Alessandro Franceschi wrote: >> >> Hi all, >> with some hardly hidden pride and excitement I'd like to announce the >> first release of Tiny Puppet <https://github.com/example42/puppet-tp> >> ("Yet Another Puppet Abstraction Layer"), a Puppet module that allows easy, >> quick and coherent management of virtually any application. >> >> > > I remember when you first introduced the Tiny Puppet idea to the group. > I'm amused now that at the time, in the context of the broader discussion, > you wrote "Sometimes I wonder if a totally data driven approach is > something that is always the right choice." It doesn't look like TP is > *totally* data-driven, but it sure takes a big leap in that direction. > In any event, TP looks great. It seems, in part, the natural evolution of > the module standards ideas: if one accepts the proposition that most low- > (and some not-so-low-)level modules should have standardized form, then not > only should we not need multiple modules to manage the same component, we > shouldn't really need multiple standardized modules, either. Why write all > that boilerplate? Automating that sort of thing is what computers are for. >
Exactly. Given the difficulties in gathering people around naming standards, which for modules mean basically standard interfaces to their functionalities, and considering the fact that I value the principle of consistency and coherency in a modules ecosystem I considered this approach as my only possibility to achieve it without writing (again) a lot of modules based on a common structure. It took me some years (I remember a discussion, made several years ago with Teyo Tyree, about the opportunity to reduce all the boilerplate around modules with similar structure) but somehow only now this goal has been achieved. Honestly this could have happened way before, as there's nothing in Tiny Puppet that could not have been done a few years ago, but I suppose things have their own maturation times. > In fact, there are good reasons for modules -- or at least classes -- > wrapped around TP resources, but it certainly looks like TP will do a great > job of minimizing all the boilerplate, which I guess was a primary > objective. > > Well done! > Thank you! Honestly I'm quite proud to listen such words from you :-) Al > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/0668e5af-a7bf-4203-b17a-fd444ca0581c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.