Does anyone has experience building an angular or react application consisting on interacting with more than 100 related objects containing all at least 10 fields of different types (string, double, int, dates, times) etc. I am interested on your feedback.
I have worked on smaller react/redux projects with just a few objects and and a hundred of fields. It has been a nightmare debugging. Backend was made using spring restful + hibernate, frontend react/redux. It’s really not easy to debug and maintain. Speed is fine as long as you don’t try to hold too many objects. You need to care of garbage collecting your objects or your browser will explose. You need to merge and version your data… you need DTO, you cannot do big computation on the client, so you still need to do them on the server… I don’t even talk about refactoring… As a matter of fact, client side frameworks are not good at this, they make me think of the beginning of J2EE/EJB with hundred of lines of boilerplate code, interfaces everywhere etc… Most developers I have seen just don’t understand most of the asynchronous issues, concurrent calls. They code javascript because it’s easy and they forget most of the issues you can find in a big project. Frameworks like Ember, Vue, Angular are good to create some more or less complex components, but you still need a server side application to interact with your data and generate your main views. Tapestry is good and it has its use case, it could improve but it’s clearly not obsolete. JS components frameworks are great too and have their use case. In the end it doesn’t really matter, as long as you find the frameworks that fit your needs and your requirements :) <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 à 14:39, Mats Andersson <mats.anders...@ronsoft.se> a écrit : > > Tapestry does a lot of things. It is not easy to cover every aspect with a > good/bad old/new style talking about Tapestry as one thing. Opinions from the > ones actually using it could be useful for anyone reading this list, so here > is my contribution to that. > > I have been using Tapestry in different setups since the beginning of > Tapestry 5. First I found the IOC and the client components useful. Then I > realized the benefits of the genious way the filters works. I really > appreciated the move to JQuery, since I already was using that and it really > made life easier. > > Now if not already done, in my opinion, it is time to separate client and > server parts. Server should provide json through a rest service, Tapestry > works very well for that, for example in combination with Jersey. On the > client side I have found the same good feeling, flow, using Angular as I have > with Tapestry on the server side. They really work well together. So to > conclude, should I recommend anyone to start a new project using Tapestry on > the server side? The main problems I would say is the lack of an updated best > practices and the missing Java 11 support. I am not updated with the latest > on Java 11 support but for my own sake I am not that worried. About the best > practices it is mainly a problem for Tapestry acceptance. When people see > that pages are rendered server side in Tapestry they see a conflict with the > powerful way to build web applications using Angular or similar. What they > don't see is the beautiful backend framework that is so complete that it do > not require continuous updates. Just opinions, but hopefully it will be of > use to someone. > > Skickat från min Xperia™-smartphone från Sony > > ---- Emmanuel Sowah skrev ---- > >> Hi, >> >> Here is a snippet from skills Howard Lewis Ship's listed on his website >> http://howardlewisship.com/: >> >> "*On the front-end, I've used all the major frameworks: jQuery, AngularJS, >> Backbone, ReactJS, ExtJS, Underscore, and more. More importantly, I have >> leveraged whatever tools are available to create responsive and complelling >> user interfaces.*" >> >> As you can see, he is even shy about mentioning Tapestry as a skill. He >> even used Apache Wicket on a client project in the past. You should ask >> yourself, why is this guy not eating his own dog shit? >> >> Learn Angular today! >> >> On Tue, Nov 27, 2018 at 12:47 AM Qbyte Consulting <qbyteconsult...@gmail.com> >> wrote: >> >>> I was recently working on a project with React components connected to >>> controllers in C# to provide the API for the back end. Development is slow >>> and tedious because there’s lots of boilerplate code, although there is the >>> benefit of some component reuse. >>> >>> Looking at the react components reminded me somewhat of the bad old days >>> of JSP, because they build the markup structure inside code rather than >>> have it all in a separate markup template. It’s simply not as good as >>> tapestry components. >>> >>> Sometimes the “new” way is still the old way. >>> >>> Sent from my iPhone >>> >>>> On 27 Nov 2018, at 03:06, Emmanuel Sowah <eso...@gmail.com> wrote: >>>> >>>> Thiago, >>>> >>>> It seems you cannot read English. I was suggesting Angular and Spring >>>> backend services being exposed via Rest to the Angular. It's seems all >>> you >>>> know is Tapestry and nothing else. The world is bigger than Tapestry, >>> boy;-) >>>> >>>> On Mon, Nov 26, 2018 at 8:52 PM Thiago H. de Paula Figueiredo < >>>> thiag...@gmail.com> wrote: >>>> >>>>>> On Mon, Nov 26, 2018 at 6:24 AM Emmanuel Sowah <eso...@gmail.com> >>> wrote: >>>>>> >>>>>> There we go again. Instead of engaging in constructive arguments, you >>>>>> behave like a child with comments like "Don't feed the trolls". >>> Pathetic. >>>>>> >>>>> >>>>> Replacing a mostly-server-side framework with a JavaScript client-side >>>>> library isn't what I'd call a constructive argument. >>>>> >>>>> And we know Emmanuel Sowah is an old, low-quality troll. He used to >>> suggest >>>>> Apache Wicket (which is a nice framework, by the way, but I'm partial to >>>>> Tapestry, of course, hehehe) and is now suggesting Spring? Weird turn of >>>>> events. But yet a low-quality troll. Good ones have good arguments and >>> make >>>>> tough questions. >>>>> >>>>> >>>>>> >>>>>> On Mon, Nov 26, 2018 at 9:21 AM Juicy Cocktail < >>> raf...@juicycocktail.com >>>>>> >>>>>> wrote: >>>>>> >>>>>>> Here is something I throw at you: 🥗🍕 >>>>>>> >>>>>>> Best Regards, >>>>>>> Rafael >>>>>>> >>>>>>> P.S. Don’t feed the trolls. >>>>>>> >>>>>>> >>>>>>>> On Nov 26, 2018, at 9:17 AM, Emmanuel Sowah <eso...@gmail.com> >>>>> wrote: >>>>>>>> >>>>>>>> But is web application framework not an overkill for this small >>>>>>> application >>>>>>>> you are building? Something you could quickly do with Angular in a >>>>> more >>>>>>>> efficient way. >>>>>>>> >>>>>>>> On Mon, Nov 26, 2018 at 9:12 AM Qbyte Consulting < >>>>>>> qbyteconsult...@gmail.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Setting up a tapestry project for building a trivial webapp for back >>>>>>>>> office data entry is still very efficient. >>>>>>>>> >>>>>>>>> Angular is a glorified java script library, not a web application >>>>>>>>> framework. >>>>>>>>> >>>>>>>>> Sent from my iPhone >>>>>>>>> >>>>>>>>>> On 26 Nov 2018, at 14:09, Emmanuel Sowah <eso...@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>> Dude, >>>>>>>>>> >>>>>>>>>> Really setting up tapestry for a new project? Are you out of your >>>>>> mind? >>>>>>>>>> Tapestry is a dying project, even it's founder Howard Lewis Ship >>>>> has >>>>>>>>>> abandoned his ship long ago and jumped onto another modern >>>>> framework. >>>>>>>>>> Pickup Angular or another modern framework for your new project. >>>>>>>>>> Cheers. >>>>>>>>>> >>>>>>>>>> On Mon, Nov 26, 2018 at 6:53 AM Qbyte Consulting < >>>>>>>>> qbyteconsult...@gmail.com> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> I’m trying to setup a bare bones tapestry project in maven 3. >>>>>>>>>>> >>>>>>>>>>> Can anyone point me an example how to do that please? >>>>>>>>>>> >>>>>>>>>>> John >>>>>>>>>>> >>>>>>>>>>> Sent from my iPhone >>>>>>>>>>> >>>>>> --------------------------------------------------------------------- >>>>>>>>>>> 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 >>>>>>>>> >>>>>>>>> >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >>>>>>> For additional commands, e-mail: users-h...@tapestry.apache.org >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Thiago >>>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >>> For additional commands, e-mail: users-h...@tapestry.apache.org >>> >>>
