Marnen Laibow-Koser wrote: > * You seemed to be saying that we should use this pattern because Cocoa > does. My respose was that yes, that's possible, but it's also possible > that Cocoa made a mistake. I make no judgement on which is the case; I > merely wanted to point out the other possibility. As far as Obj-C being > weird, well...I think it is. That doesn't mean I dislike it; in fact, I > think it's kind of neat. But a C-Smalltalk hybrid is like > garlic-flavored ice cream: even if you like the way it tastes, it's > still conceptually odd. :)
Actually, I'm not saying that at all. This all got started by my saying that I like this pattern that I've seen used in other places. If you look back at earlier posts, I also said that view helpers are a fine substitute in the context of Rails. I tend to draw on experience from across all the languages and frameworks I've used. I think they all have something to teach us, whether we necessarily like everything about them or not. In regards to the C-Smalltalk hybrid nature of Obj-C: I believe that grew out of both a need and a want. The designers of the language were obviously fans of Smalltalk (or at least certain aspects of it), but also had a need to be directly compatible with the huge amount of C code that operating systems and services were written in. Not every language can be purely "green-field" like Ruby, or even Java. Even today there is still a huge amount of pure C code running most modern operating systems. When you are writing applications running directly on top of that code, a hybrid like ObJ-C is a great solution. It provides a clean object-oriented model, that can still be intermixed with all that legacy C code. P.S. I sorry if my prior post sounded harsh. I was simply trying to make a point. I know that you're a great developer, I follow your posts and agree with the vast majority of your replies. I just think we need to be careful of falling into the "elitists" trap thinking that "our" way is the "only" way. I love Ruby and Rails, but that doesn't mean that I'm going to forget the lessons I've learned from other solutions, or disregard them because they're different. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en -~----------~----~----~----~------~----~------~--~---
