Yeah, it's the same with hibernate, all the Apache portifolio, open source projects and java itself. If there comes no new JSR's, java stalls. However with opensource stuff you have the source available. And that's a guarantee I like.
2010/5/25 James Carman <[email protected]>: > On Tue, May 25, 2010 at 7:25 AM, napple fabble <[email protected]> > wrote: >> That's why it's written as "vendor lockin", not vendor lockin. Perhaps >> framework lockin would have been better. >> >> To put it simply, when I choose JSF or wicket I create a permanent, hard to >> change, binding to that technology. >> >> - with wicket there's no 100% guarantee that the framework will be supported >> after a week, month or a year >> - with JSF there are commercial application servers that guarantee certain >> number of years of support when you buy their product. Whether that support >> is indeed "crappy" or not is up to debate and may vary between different >> products. >> > > With Wicket, you have the source code, so if it comes down to it, you > can support it yourself if something happens and the committers all > decide to go off to do other things. But, there is absolutely *no* > guarantee that someone will be there working on Wicket to do your > bidding (in their free time mind you), you're correct. This isn't > really a Wicket question, this is an open source question. > > --------------------------------------------------------------------- > 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]
