Hi Folks Just wanted to do a quick response to Kristian's adventures with DRYML and suggestions for the future.
All of our focus right now is on getting to a 1.0 release, there has been a feature freeze for sometime, and even then some things are sneaking in, so we need to be pretty vigilant about this. So we definitely wont be adding any major DRYML enhancements to core Hobo this side of the 1.0 release. Having said that, of course anyone and everyone is welcome to fork and try out their own experiments. If new development looks like a win, we will of course look at the possibility of merging them back in to Hobo. I'll just add some of my thoughts about where DRYML should go in the future (or rather where I think it shouldn't go) As with any language design, there is a constant and very tricky balancing act between power and flexibility on one hand, and simplicity and learnability on the other. DRYML is already a great deal more sophisticated than most (all?) templating languages, so any ideas that make it still more complex will have to justify themselves very strongly. As I think I mentioned a while back, generating languages other than HTML is specifically not a goal of DRYML. So extensions to the language that add complexity and are mostly relevant to generating other languages are unlikely to be merged in. So if folks want to push the envelope with what DRYML can do, I'm all for it, but just be aware that you might be embarking on an ongoing fork. That's definitely not a bad thing - it's the beauty of open source : ) Cheers Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
