reading HLS's blog entry:
http://tapestryjava.blogspot.com.au/2012/10/zeroing-in-on-tapestry-54.html
I was wondering why i didn't understand the code snippets .. were they
pseudo code? no, pseudo code is far more legible...
Reading further, I notice it's CoffeeScript.
I'm keen to hear what the supposed benefits of this shift are, my first
inclination is to think of how this might be a problem for me.
I've had to do some pretty in-depth debugging and patching of tapestry's
javascript in the past (particularly around zones) and at least I can
understand the source code because it is a familiar language...
Replacing the source-code with an entirely new language, which is
probably familiar for < 2% of tapestry sounds like a bit of a speedbump
to me.. especially if - in order to create a monkey-patch of sorts, it
will need to be written and integrated via Coffee?
So does anyone have any insight into how this problem will materialise
in reality? and why is CoffeeScript attactive in the first place?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
