After reading posts after posts that Tapestry is outdated - how is it outdated?
The last year I have used ReactJS/JSX/TypeScript/es2015/node, SCCS in a
multimodule setup in Tapestry. I am using Tapestry Resteasy or just Tapestry
Ajax() or Zone.deferredZoneUpdate() to nice error messages.
Can
Good grief, not this again.
Tapestry is a great choice where the developer has java skills (it works quite
well with Scala too) and doesn’t want to spend hundreds of hours gaining
proficiency in a java script framework (that change every few years) and where
there isn’t budget or requirements
13 years dude 13 years
On Thu, 4 Jul 2019, 11:05 am Emmanuel Sowah, wrote:
> Lance,
>
> I am not hating Tapestry, I am only a messenger preaching the good news
> that the world has moved on and left behind antiquated frameworks like
> Tapestry. Even the founder, Howard Lewis Ship, the
Technologies such as Tapestry are not more deprecated than Wicket neither
worst. Wicked has its benefits, but also quite a lot of weakness. Wicket is
very verbose and annoying to refactor, I can’t see any advantage of Wicket over
Tapestry.
Regarding new technologies, there are plenty of new
Emmanuel:
Do you seriously NOT realize what is going on here? YOU were the first
person to start calling people names. YOU are the one using "ad
hominem" arguments about Tapestry users. YOU are the one crying "Mom,
he hit me back first!"
I actually AGREE with you that it's past time to
You don't have to tell us that, we know there is a world out there! I have
tried Wicket - it is very good, but found Tapestry better for my needs. I am
using ReactJS with Tapestry. It works very well. Tapestry is rock solid and I
hope it will live forever!
S-E
Lance,
I am not hating Tapestry, I am only a messenger preaching the good news
that the world has moved on and left behind antiquated frameworks like
Tapestry. Even the founder, Howard Lewis Ship, the captain of this Tapestry
ship, has long left this sinking ship. He is now using other better and
lol. Same here.
> On 3 Jul 2019, at 4:34 pm, Massimo Lusetti wrote:
>
> Thanks Lance, you made my day.
>
> On Tue, Jul 2, 2019 at 11:04 PM Lance Java
> wrote:
>
>> Emmanuel Sowah - I think you deserve some form of long service award.
>> You've been hating on Tapestry for over 13 years now.
Thanks Lance, you made my day.
On Tue, Jul 2, 2019 at 11:04 PM Lance Java
wrote:
> Emmanuel Sowah - I think you deserve some form of long service award.
> You've been hating on Tapestry for over 13 years now. Way to hold a grudge
> dude!
>
> https://wiki.apache.org/tapestry/Tapestry5Trolls
>
>
Emmanuel Sowah - I think you deserve some form of long service award.
You've been hating on Tapestry for over 13 years now. Way to hold a grudge
dude!
https://wiki.apache.org/tapestry/Tapestry5Trolls
On Wed, 19 Jun 2019, 10:18 am Emmanuel Sowah, wrote:
> Of course it's understandable that they
-Original Message-
From: Qbyte Consulting
Sent: torsdag 20. juni 2019 03:02
To: Tapestry users
Subject: Re: Jetbrains considers to deprecate Tapestry plugin in IntelliJ 2019.3
React repeats the same sins as JSP by mixing code and presentation. A problem
tapestry addressed. Its kind of strange
Well John, that historic argument of missing code and presentation was
probably oversold as bad then just to push a new thing unto us. Having used
these modern frameworks in large scale projects, that has never been an
issue. Facebook is using these frameworks too for their global app. Should
that
React repeats the same sins as JSP by mixing code and presentation. A problem
tapestry addressed. Its kind of strange seeing this JSP age issue afflict those
“better frameworks”.
I’d also wager a SPA could be developed more quickly in tapestry than with any
JS framework plus an API. Then there
We're called "professionals", who are trying to maintain older, large,
applications that were built before Angular etc existed, while we
simultaneously migrate them into smaller pieces that will work with
modern frameworks.
So if you've got nothing useful to say, get the hell off my lawn,
Hi,
To be fair Tapestry support as implemented in the plugin was and is still
very limited and sometimes even misleading, and there's definitely room for
improvements.
But it's still the best we have.
In case you didn't notice, the plugin has been open sourced few months ago:
Of course it's understandable that they are going to deprecate it. What
kind of creatures are you still stuck to a failed and stone-age framework
like Tapestry? Even the original creator, Howard Lewis Ship, has abandoned
it for better frameworks like React, Angular and Wicket. Guys, wake up and
If you visit the link, there is a contact form. I sent a contact urging the
continued support of the plugin.
-Original Message-
From: Rafael Bugajewski
Sent: Tuesday, June 18, 2019 5:01 PM
To: Tapestry users
Subject: Re: Jetbrains considers to deprecate Tapestry plugin in IntelliJ
I use the plugin. That’s some sad news :(
Best,
Rafael
> On Jun 18, 2019, at 10:45 PM, Nicolas Bouillon wrote:
>
> Hi,
>
> Not sure if many of you are using the Tapestry plugins of IntellJ Ultimate.
>
> I do and it's very handy to navigate fastly between components and for code
> completion
Hi,
Not sure if many of you are using the Tapestry plugins of IntellJ Ultimate.
I do and it's very handy to navigate fastly between components and for code
completion in templates.
https://blog.jetbrains.com/idea/2019/06/plugin-deprecations-in-intellij-idea-v2019-2/
Tapestry is my favorite
19 matches
Mail list logo
