Given the parameters that you describe for your app, I'd definitely go with 4.1. The only reason I wouldn't is if you knew you were going to be building a very large app that was going to use a significant percentage of the API, since in that case, you might struggle keeping up with changes. But all the baseline tapestry functionality works 98% of the time and I imagine that the API in the core is already pretty stable. Bugs may come and go, but at least you shouldn't be rewriting entire functions to match some new interface. And 4.1 is unquestionably superior to tap + tacos for ajax functionality (although tacos has some nice components that haven't been ported yet. But they should be pretty simple to do yourself, shoudl the need arise).
--sam On 12/5/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Thanks! My app is launched in 4.0 right now, but the next version will probably be launched January 31st, so that was part of the reason I was aching to go for 4.1 since there's still 2 months to go for bug fixes, etc... Though I suppose we *should* schedule Christmas somewhere in there ;) Greg -----Original Message----- From: news [mailto:[EMAIL PROTECTED] Behalf Of Ron Piterman Sent: Tuesday, December 05, 2006 1:23 PM To: users@tapestry.apache.org Subject: Re: 4.1 Stability (Hi Jesse! :P) If you need ajax, you can't go around 4.1 - if you don't, 4.0 has some advantages (as far as I can see) - such as much smaller javascript footprint for form validation, and stability - However, Jesse does a great work in fixing bugs in 4.1 very fast, I go to sleep in Europe and Jesse fixes the bugs at day time in the states, so the next morning a new version is out - thats amazing ! It is not so easy to recommend anything in active development for production - I can just say - I am working on a project which should go in production on Jan 1st and am using 4.1 --- Cheers, Ron Cyrille37 wrote: > > Hi Jesse, > > You think we have to use the 4.1 vs. 4.0. > For example I'm learning Tapestry for a project which will really start > in january. > Will you tell me to use the 4.1 ? > > thanks > cyrille > > Jesse Kuhnert a écrit : >> I think it would reckless of me to recommend anything that may or may >> not affect anyone's job/career.. >> >> That being said - if it were me - yeah I'd totally go for it. >> >> It's probably been a mistake to wait so long for 4.1.1 to come out >> anyways. Probably I'll just fix this validation message issue and >> release it. >> >> On 12/5/06, [EMAIL PROTECTED] >> <[EMAIL PROTECTED]> wrote: >>> Okay, I know Jesse is probably fed up with these types of questions! >>> And we've gone over it before, about 4.1, 5.0, roadmaps, etc, a >>> couple weeks ago. >>> >>> The 4.1 "snapshot" that's out right now, for a relatively simple app >>> - no custom components, hivemind services, Java 1.4 so no >>> annotations, and maybe a sprinkle of DOJO stuff (hence the reason to >>> switch to 4.1!!) - would moving from 4.0 to 4.1 be a horrible idea? >>> >>> I skimmed over a lot of the open issues on JIRA and none seem too >>> severe, or too widespread to some of the "proven" core of tapestry. >>> Our application is for our internal staff (a dozen or so), and since >>> it's relatively small, is usually decently tested for bugs. So it's >>> not like I'm re-writing Amazon.com or something with Tap4.1 and will >>> lose billions of dollars over a bug.. >>> >>> 4.1 looks really nice, and it would be great to jump in, rather then >>> do it in 4.0 and then re-do it in 4.1 in 6 months. That said, go for >>> it? All comments apprieciated! >>> >>> Thanks, >>> Greg > > > > --------------------------------------------------------------------- > 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
