Toby Parent wrote: > I find myself agreeing. If one depends on the framework to generate > one's Javascript, one doesn't learn Javascript, which is sort of the > point of this question. I'm using Prototype in CakePHP, but I like the > fact that, while options are available to front-end my javascript, I can > simply learn the stuff.
Once we "learn JavaScript", then we need to write it as flexibly and platform-neutraly as possible. I would rather bottle all the cross-platform stuff up and call into it, than rewrite all the if(ie) stuff, all the time. That, in turn, requires obscenely complex object models in JavaScript. They deserve to be written once and called many times. This exact discussion was once held, 30 years ago, regarding Assembler and C. You had to know Assembler to code C, and you used C to avoid Assembler by any means necessary. C handled porting the machine code to other CPUs. Yet there were still people claiming that you should still write more Assembler, to learn it, to prove you can, when it's convenient, when you know what to write, etc. Sure those reasons still exist. But your default choice, in that situation, should always be C-first. -- Phlip http://www.greencheese.us/ZeekLand <-- NOT a blog!!! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" 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-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
