Hi Giulio,
I think Ben's reply was actually quite thorough and good-faith — he
explained the real constraints the project faces, outlined concrete
ideas for improvement, and even invited further contributions.
Summarizing it as "fork or die" doesn't do it justice.
That said, your frustration is understandable, and the points you raised
about the developer experience are welcome. (The aggressive/sarcastic
tone isn't, though.) The javax/jakarta migration was painful for
everyone, and Spring Boot-style bootstrapping — just adding a dependency
and having things work — is what many find convenient.
We're a small team of volunteers, and we genuinely can't do everything —
but that also means contributions from people who have just gone through
the pain of modernizing old code are especially valuable. You clearly
have a good understanding of what's missing. You could contribute back
to the community by taking "ownership" of tapestry-boot. Happy to
include a reference to it on the Tapestry website.
The door is open.
Cheers
Volker
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
