Re: [ANNOUNCEMENT] Tapestry 5.4.4

It would be great to see a fresh vision and roadmap for Tapestry going 
forward. Tapestry has many strengths, but has a relatively steep 
learning curve and does not do enough to help new developers get off the 
ground. We have been using Tapestry for a very long time and still find 
it challenging at times, especially when integrating Tapestry with newer 
client-side technologies.

I saw your mention of bootique-tapestry and am curious how that is 
working out? We briefly looked at bootique-tapestry, but decided to 
create a module to integrate with Spring Boot instead. Spring Boot won 
out mostly because of the breadth of what it has to offer and the large 
user community.

There are still a few rough spots in our Spring Boot integration, but 
the effort was very worthwhile. The combination of Gradle + Spring Boot 
+ Tapestry is very powerful and greatly reduces the amount of 
boilerplate needed to create a production ready application. The 
integration with Spring Boot is surprisingly thin and the integration is 
nearly seamless.

Anyone have a sense as to whether the community is interested in 
pursuing a first-class Spring Boot integration?  I would be happy to 
share what we have done if there is real interest in making it a proper 
Tapestry feature. I don't think it would be a huge effort if some of the 
core Tapestry developers were engaged in the process. Having a supported 
integration with Spring Boot might bring much deserved attention and new 
users to Tapestry.

Regards,
David

> Congratulations! Thanks to the core team for your continuous work and the effort you put into maintaining Tapestry.
>
> I think the whole industry goes the way of trying to simplify things (just take a look at the most recent programming languages & frameworks). If we’re talking about modernizing and competing with other frameworks, I would like to see Tapestry reducing the complexity that is currently required to grasp the framework and its various concepts (which are technically great, but sometimes hard to understand if you just start working with Tapestry). I think this will only work by providing old & new APIs at the same time and by making the upgrade path and improvements very clear in the documentation.
>
> Personally I’m also getting into the vibe of smaller services that communicate with each other, instead of this one monolithic giant that tries to be everything, but is nothing in the end. We use bootique-tapestry (and also other Bootique-compatible integrations). I would like to see Tapestry to also go in this direction and improve integration on similar deployment environments.
>
> On the other side, I’m currently pretty happy with the state of Tapestry and with the framework keeping up with modern Java versions.
>
> Best,
> Rafael
>
>
>> On 2018-19-12, at 11:02 AM, Christopher Dodunski <[email protected]> wrote:
>>
>> Good team effort!  It's encouraging to see Tapestry progressing in step
>> with associated technologies: Java 12 is due out in March, and Hibernate
>> currently at version 5.3.3.
>>
>> Tapestry 5 was a leap forward from 4.  Where does the community see
>> Tapestry 6 at on the Java web landscape?  A free and frank conversation -
>> Tapestry's strengths and weaknesses, what attracts others to JSF, Wicket
>> and other competing frameworks, where web frameworks are generally headed,
>> etcetera - ought to help ensure that Tapestry remains relevant beyond
>> 2020.
>>
>> Regards,
>>
>> Chris.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]