Just wanted to clarify that I'm certainly not expecting any kind of vendor-like treatment, by "we" (as in "we can't seem to get 'em right") I meant the Rails community as a whole, not the core or anything like that; and further, that this was not an assignment of blame, but a rather poor excuse to stay away from namespaces. (As if anyone would avoid use of unicode or i18n just because it's lacking a bit in the implementation?)
I have gotten the impression that namespaced controllers and models are kind of frowned upon within the Rails community as a whole, I guess I projected some of that impression onto Thjis comment. I'd love to fix the namespace issues myself, but sadly my Ruby-fu isn't quite up for that kind of challenge. Ruby is a very powerful language, but that power translates into magic which in turn translates into confusion. Well, to me it does, at least, and certainly when it comes to dabbling with other people's code. Guess it wouldn't hurt to take a look though. Best regards, and thank you, Tomas Jogin On 9/5/06, DHH <[EMAIL PROTECTED]> wrote: > > > 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 -~----------~----~----~----~------~----~------~--~---
