Hi everyone, I am using tapestry since 10 years, on web apps that have 100’000+ lines of codes. It works well, of course it has it’s drawbacks like any framework, but it’s way better than many other frameworks I have tested (JSF, Wicket, Struts, Spring MVC). Building apps with 100% of react is a nightmare, and usually not worth it, it’s good for apps that have a very straightforward use case, for business apps back office with multiple form, and input data, react or vue or any component based js framework has no advantages. React is useful in very specific user experience to achieve specific tasks (google adwords or google analytics) but even adwords or analytics are full of bugs, they hang the browser, you have to refresh the page. We are talking of apps made by 100 of engineers.
The biggest drawback now is that tapestry has it’s own js implementation (based on various js library such as jquery). I know it’s theoretically compatible with any other js framework (as long as you implement the tapestry js interface, this what i have done to make it work with dojo instead of jquery), but it expose too much javascript. It should have a way to only expose json objects for validation or events handling etc.. Nowadays I use webpack for all my javascript, css processing, I also use typescript most of the time. Thus making webpack fit in tapestry is a bit of pain, you have to remove all javascript included in every component, then add into webpack all the tapestry dependencies etc… I think this would be a great area to improve, but it’s clearly not easy. But I believe webpack is the future. I have thought of building typescript + webpack with rhino, but it’s way to heavy :( Best regards, Numa The way to go: Tapestry, Spring, Hibernate, React functional or Vue <http://www.dfacto.ch/> Numa Schmeder www.dfacto.ch <http://www.dfacto.ch/> n...@dfacto.ch <mailto:n...@dfacto.ch> | M +41 79 538 30 01 DIGITAL STRATEGY | DESIGN | DEVELOPMENT > Le 27 nov. 2018 à 10:54, Rafael Bugajewski <raf...@juicycocktail.com> a écrit > : > > Heya all, > > I’m in a similar situation. I started my first Tapestry project 14 months ago > and did a pretty sophisticated research in advance. I haven’t regretted it > yet, and the only worries I had, were about new Java releases compatibility. > But this is something that is already in progress as far as I know (as a side > note: Do anybody know the status of this?). I also love how Tapestry handles > things with its convention first approach. It’s a very mature framework, so > of course it took a little bit of time to understand how all the components > work together, but once you grasp it, you gain a massive productivity > increase. We’re just a small team, so this is very important. I don’t care > about the framework as much, as I care about fast releases (that’s what > frameworks are for in the end). > > Tapestry just fits perfectly into this mentality. > > I guess there are coders who always jump on the new hype train. They buy the > new hyped out hammer that’s just a little bit more shiny than the previous > one. Everything looks to them like nails in the end. And then there are > engineers who choose the right tools for the job without prejudices. > > I want to thank the current Tapestry core team for their work. > > Best, > Rafael > > >> On 2018-27-11, at 05:16 AM, Christopher Dodunski >> <chrisfromtapes...@christopher.net.nz> wrote: >> >> Hi all, >> >> I only started with Tapestry, seriously, around 18 months ago. Tapestry >> may not be the latest fashion, but I love its convention over >> configuration approach, use of POJOs, and the myriad other elegant >> features that keep web application development fun and rewarding. >> >> I guess technical elegance and fun never goes out of fashion, huh? :-) >> >> Chris. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org >
