Well exclamation points aside, I think my base concept is I just
wanted to get a compiler ready to output whatever mashup we prescribe.
I understand fully what you are saying, the end product is javascript
and how we get there is all implementation details that for me as it
stands are not a blocking force for what I have started developing.
That said, the design is completely composition based, so we can swap
out about 4 different layers at any time to test different approaches.
Eriks point I think was he is trying to write some of the js side that
isn't for the time being going to be cross compiled. But as I see it,
I don't think there will be a reason to hand write a lot because we
could even create a custom emitter that knows how to spit out our core
js framework. Which then could be just one more abstraction layer.
Mike
Quoting Kevin Newman <capta...@unfocus.com>:
I understood Frank's approach as vanilla-js (ES5) - eg, no dependencies.
JS is JS though - you can write Backbone.j models in Typescript,
wrap jQuery based views in coffee script, and lay everything out
using mustache with some Jangaroo games mixed in just for giggles.
At the end of the day it's all just javascript.
Kevin N.
On 12/14/12 6:17 AM, Michael Schmalle wrote:
I say stick with goog, if Frank wants to use something else he can.
If in the future we find a better way, I will PERSONALLY help
change every freaking line of code Erik. Just focus on goog!
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
