bmolzen wrote
I'm curious to know how many people are using each solution, and why.
I'm trying to figure out which is really going to work better for me. I'm an intermediate level developer now building modules for my own site. I'm not at the point where I'll be releasing modules to the public yet, but I still need a good solution in which I'll be hitting that "Build" button quite often, and then hopefully without having to package up PA's, be able to move my code to my production box (in my home network).
Without spending a couple weeks on each environment, I was hoping to get some community feedback which they prefer, and for what reasons. It seems each has their merits....
Right now, I'm leaning towards the DNN solution, but only because I know going forward there will always be some type of support for it.
Thanks in advance....
I know I am a little bit biased here but... I would definetly advise you to start of with my approach. Simply because I've met too many users who had given up after working with the default approach because it's too slow and too bulky.
However... one thing that the core team approach has and mine doesn't is official support (as you've mentioned it; and although I do support my users... simply said... the core team has is bigger than me). From the other side, my approach is so generic and so simple once you master it that any support for it is not needed... most of the users who contact me are first timers, after we get over the little bumps in their knowledge... they are really happy.
Having said this... did you try developing a simple module with both techniques.... I advise you to try it first with the core team method, and then try out mine... it could will show you the real difference in both methods.