Subdomain routing with Rails
s2.diffuse.it
s2.diffuse.it
Also, they need some sort of solution to the monkey patching problem. Perhaps emacs-style hooks.
It's hard to call something an "enterprise solution" when it's a bunch of code cut-n-paste from blogs, mixed in with possibly-conflicting modifications to the core.
Instead of using the code you find on the blogs as copy and paste modules to add functionality to your software use it as an example of how to use a certain technique then implement that technique in your software.
Lego applications rarely end up being what the consumer actually wants despite having all the required functionality because general solutions are hard to map to specific requirements.
Here's a good example of a Catalyst plugin, so you can see how straightforward it is: http://search.cpan.org/~jrockway/Catalyst-Plugin-Unicode-0.8...
FWIW, Catalyst plugins have a lot of problems, but they have also proven useful to people trying to extend the framework. 99% of the time, people can get a maintainable chunk of code into their application without having to monkey patch or change the core. That is a Good Thing, but we can do better :)
Catalyst 5.8 will use Moose roles for plugins, so the safety problems of mixins should go away. The next problem to solve is how to reuse cross-sections of applications (models, views, controllers, templates, etc.) in a clean manner. I'm experimenting with Bread::Board (IoC) in a new framework called Kiiteh. If Kiiteh pans out, it will be Catalyst 5.9.
It doesn't seem fair that the person who took the time to a) explore this problem, b) create a solution, c) describe their solution (with code) should also have to d) create a plugin/gem.
Conceivably, the time they saved you could be devoted to creating the plugin and adding some polish.
The upshot of this is that I've contributed many patches to GNOME, but none to Rails. If I come up with something useful, I'll blog about it so others can see, and then let it go. The entry barrier to get it in Rails is just too high.
I suppose I could make it a plugin, but a lot of these things seem like they should really be in Rails itself, so trying to factor them out to be a usable plugin is just a different kind of pain.
For Catalyst, we have the same policy. Send us some random patch with no tests or docs and there's no way it will ever see core. However, we are very successful at getting people to resubmit with docs and tests. But usually, the patch to core doesn't need to be a patch to core, it can be Some Other Module.