On Tue, Nov 27, 2018 at 7:54 AM Rafael Bugajewski <raf...@juicycocktail.com> wrote:
> Heya all, > Hello! > 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?). Yes, we're working on this. You can follow the progress in https://issues.apache.org/jira/browse/TAP5-2588, which has Java 9 in its title, even though we do want to have Java 10 and 11 supported too. Of course, you can also join the discussion and even post patches, as someone already did and I'm planning to apply it to the code very soon. Everyone is invited to participate in one way or another! > 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. This has been particularly true to client-side JavaScript. It seems to me that React and similar libraries are slowly taking over the other approaches lately. > And then there are engineers who choose the right tools for the job > without prejudices. > Words of wisdom! > I want to thank the current Tapestry core team for their work. > And we, the Tapestry core team, would like to thank everyone who posted their testimonials here, including the one with criticisms. Yes, we know JavaScript is something which could have been handled in a more friendly way, but that reflects the server-side-focused time it was created. -- Thiago
