It's a shade off a hundred minutes in length, but Lullabot Drupal podcast no. 38 is the most fun I've had since the last LugRadio podcast. A contentious litany of Drupal modules that have outlived their usefulness, or soon will, thanks to CCK and Views, I found myself almost punching the air in delight at how many of the more contentious declarations I agreed with. Just days earlier, I had been trying, and failing, to come up with a justification for the continued use for the taxonomy module, so it was gratifying to hear Jeff Eaton declare that in his opinion it's days are numbered. He pointed out that you can do most of what Taxonomy does using CCK text fields, but I'm surprised nobody talked about terms-as-nodes, using node reference fields, which to me seems an obviously good idea that allows you to retain a heirarchical taxonomy structure, "related terms" and what-not in a more flexible manner.
Moshe Weitzman has written a brilliant article about the site he put together for the New York Observer, eschewing the Scheduler, Scheduled Actions, and Workflow modules for a hand-rolled CCK and Views solution. He declares "CCK has arrived, and helps us build sites quickly, and change them easily". Hear, Hear!
On the topic of modules that should be led behind a screen and shot, I've just finished one site, and am painfully progressing through development of another using the Drupal E-Commerce modules, and I have vowed to never do so again. Which means that I either never do another E-Commerce site (which I wouldn't shed any tears over), use another set of modules which are bound to have similar problems due to the difficulty of devising a general solution to problems that are in the real world so very particular, or use CCK and Views. The last of these seems to me almost a viable solution. In theory, e-commerce modules should give you a convenient one-size-fits-all solution, but in practice I'm unlikely to find a customer whose needs can be met by anything out-of-the-box, so I'm either going to hack or extend somebody else's code, or spend the same amount of effort putting something together using CCK and Views. I'm willing to put money on the latter option being more maintainable in the long term.
