React repeats the same sins as JSP by mixing code and presentation. A problem tapestry addressed. Its kind of strange seeing this JSP age issue afflict those “better frameworks”.
I’d also wager a SPA could be developed more quickly in tapestry than with any JS framework plus an API. Then there there’s also the fact that tapestry apps can be developed by any Java developer without a need for much additional JS expertise. Can’t really compare apples and oranges. John Sent from my iPhone > On 19 Jun 2019, at 16:18, Emmanuel Sowah <eso...@gmail.com> wrote: > > Of course it's understandable that they are going to deprecate it. What > kind of creatures are you still stuck to a failed and stone-age framework > like Tapestry? Even the original creator, Howard Lewis Ship, has abandoned > it for better frameworks like React, Angular and Wicket. Guys, wake up and > stop wasting your time. > > On Tue, Jun 18, 2019 at 10:46 PM Nicolas Bouillon <nico...@bouillon.net> > wrote: > >> Hi, >> >> Not sure if many of you are using the Tapestry plugins of IntellJ Ultimate. >> >> I do and it's very handy to navigate fastly between components and for code >> completion in templates. >> >> >> https://blog.jetbrains.com/idea/2019/06/plugin-deprecations-in-intellij-idea-v2019-2/ >> >> Tapestry is my favorite framework, and I haven't found any replacement with >> the killing features such as Live Class Reloading (natively) and excellent >> error reporting. >> >> Keep up the good work. >> >> Nicolas. >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
