I am mostly concerned to being tied to a specific library implementation.We have first hand experience with tapestry situation pre 5.4. (Prototype,script aculo)
In the other hand, removing the abstraction layer will indeed make our client side support much better and robust. Since we are doing this conversation would it not be better to ditch jquery,prototype etc in favour of vanilla.js? More and more people are in favour of vanilla.js http://developers.slashdot.org/story/15/04/27/1754230/javascript-devs-is-it-still-worth-learning-jquery http://thednp.github.io/bootstrap.native/ http://gomakethings.com/ditching-jquery-for-vanilla-js/ On Fri, May 8, 2015 at 11:36 PM, Howard Lewis Ship <hls...@gmail.com> wrote: > so this is very late in the game but I was just wondering how much better > tapestries client-side support could be if it just simply standardized on > jQuery and gave up on the abstraction layer. Thoughts? > > -- > Howard M. Lewis Ship > > Creator of Apache Tapestry > > The source for Tapestry training, mentoring and support. Contact me to > learn how I can get you up and productive in Tapestry fast! > > (971) 678-5210 > http://howardlewisship.com > @hlship >
