Hello all, 2008/12/6 Lawrence Oluyede <[EMAIL PROTECTED]>: > > On Sat, Dec 6, 2008 at 2:36 PM, Jorge Vargas <[EMAIL PROTECTED]> wrote: >> That said I really think a JS wrapper in JS is better than a JS >> wrapper in python or whatever language for that matter. Any DSL which >> is pretty much what all the libraries have become is way better than >> having a half baked parser/compiler/runtime to generate code from >> language A into language B > > I strongly agree. This is one huge case of leaky abstractions in my opinion. > By the way, John Resig (jQuery's author) has a take on this: > <http://ejohn.org/blog/javascript-language-abstractions/> Thanks for that interesting link, it was a read which triggered some thoughts.
I've seen the latest pyjamas announcement on freshmeat, looked at it and thought: Oh, this looks nice, maybe give it a try. Up to now, I haven't come around to do so, but I definitely will at least take a bit of time and look what it can to and can't. The thing which really triggered my thoughts was a statement in one of the comments: "How would an Assembler or C developer have looked at code generators 10 - 20 years ago?" And that is a comparison that feels somehow fitting. Yes, of course are solutions you write in ASM or C 10-20 times faster than anything written in an interpreted language. Yes, they are smaller and more elegant. But why are the demands of the market for ASM or C developers decreasing now, and if you look at job adverts, most jobs are for a higher level language... Because it is just a lot more productive writing code in Python or Ruby or even Java, than doing it in plain C or even Assembler. Yes, with some good libraries, you can speed up the development process in C quite a bit, but it still isn't as fast as going with a language like Python in the first place (at least that is what my experience suggests). Still, there are things which are absolutely viable to implement in C, and either use them as a library, or just glue them together in a higher language.... And if you translate that onto a JS code generator, I think that that might be a route we possibly will see: Prototype and develop your stuff in one of the higher level abstraction tools (like GWT or pyjamas), and only handtune or handwrite the real critial stuff in direct JS. It might work *shrug* But, as I said, I haven't yet really played around with any of those toolkits, but I definitely want to give it a try :) Jens --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
