First of all, to become a standard it must be something really good. And if Wicket fulfills this requirement, I’m pretty sure it does. Secondly, becoming a graduated project helps a lot – look what happened with Struts few years a go. But, the most important thing that must happen to turn Wicket into a standard is to continue spreading the word about it and keeping it the way it is.
The most interested in this is us, the community. And just like it happened with Struts and Hibernate, frameworks that were supported by the community, we – Wicket users – must do our part.
So, to become a standard depends mostly on us. And I think we’re already doing a good job at this.

Well, for those wicketeers on Windows, the only thing I can think of to say to them is: it doesn’t matter if your operational system sucks when your web framework rocks! :-D

And I totally agree with you. This is an important thing to say: it’s hard to find an obsticale while developing with Wicket (despites those problems with Generics… that were already resolved!)

Cheers

And hehe I wonder how many of the Wicketeers are on windows, not many I think?

When the webframework you use becomes a support instead of an obsticale, the world suddenly becomes a nice and funny place to be, so I agree in your last comments:)