> It's just within Rails that namespaces are > frowned upon, and, IMHO, for no good reason (the only semi-logical > reason I can find is: "we can't seem to get 'em right"). Note that I'm > NOT casting any blame here, nor expecting any favors or service; I'm > just rejecting the IMHO baseless proposition to "not use" modules in > favor of, well... in favor of nothing else.
Who says its frowned upon? Michael (core) says that the original report sounds like a bug and asks for a ticket. Thjis (user/contributor) says that he has had problems with modules in the past and are now avoiding them. Neither represent a "Modules Considered Harmful" argument. The notion that "we can't seem to get 'em right" does bug me, though. It's another sign of vendoritis and certainly an implicit form of blame. The simple fact is that most core developers just don't need modules, so they are not being worked on unless quality bug reports come in. And even then, they're probably just going to be fixed to the best of that report. Instead, it'd be great if people who actually needs/wants modules in their applications got a "Friends of Modules" group together, pulled up their sleeves, and started programming to make them solid. This is a commons and we're eager to see your contributions in the core. I see no good reason why modules shouldn't work perfectly, except that "the people who care haven't done the work". Make it happen! ;) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core -~----------~----~----~----~------~----~------~--~---
