NetBeans 6 delivers great updates to the Matisse GUI builder. Spend a few minutes with Roman Strobl and get an expert briefing on what's new and what has changed. (sponsored)
In this, the third and final installation of Andres' Introduction to Groovy series, you learn about how Groovy handles variable numbers of arguments, named parameters, currying, and more about Groovy operators. Including, some new operators.
Swing Fuse (actually just Fuse), is a framework designed to make it easier to create your own custom desktop components. In this article, Daniel Spiewak shows you how to get started and provides sample source code you can download.
Willam Louth shows how he uses JXInsight Probes to investigate probable performance issues with code bases that he is not familiar with. He also highlights possible pitfalls in creating a benchmark, as well as in the analysis of results.
Back on July 14th, Kevin Taylor asked in
this post
on About.com, about which Web frameworks people were using. Wicket was not even in the list of popular frameworks that he gave to start the discussion.
Today
, Kevin reports some interesting results. The most recommended framework by readers who responded is Wicket.
I think page based frameworks are the future and at the moment there are not many of them. I have looked at JSF and well.. it feels quite complex. Tapestry is nice, but is very complex in the beginning. Wicket feels just right..
The company I work for is planning to migrate to wicket (or another pagebased/componentbased webframework). But Wicket has the most chance at the moment because it is not complex.. and java developers are back in control.
Not to sound like my late grandfather, but there are too many web frameworks these days. It seems every month someone is touting their web framework as the next big thing. A handful of people blog about it and it's suddenly considered a success.
By the time a corporate entity decides to standardize on a framework it seems it's obsolete or considered too complex.
don`t you get tired of yourself? I do get tired of you. Give some good arguments or don`t reply. You are wasting my (and your) time with such stupid remarks.
"But there are too many web frameworks these days?"
Are you saying just because there is a glut of so-so web frameworks, that developers should stop inovating? And I also gather by your statement that we should slow down a bit so corporations can "catch up"? Puuuuuuleasssse!!! The day I tailor my development strategies to placate corporations is the day I hang up my IDE forever.
If something is to complex, it should be replaced by something simpler and more elegant. From what I can tell, Wicket fits the bill quite nicely.
I don't mean to be combative, but the "sit on our laurels" attitude you proffer just didn't sit well with me.
Most of the frameworks you refer to are also 'late'. If you look at the impressive list on the
Wicket website
, you will have to look hard to find a framework that is alive, has a userbase of more than 100 and is still under active development.
The world is not waiting for yet another model2/web MVC/operation oriented framework. Struts, WebWork, and Spring MVC fit that bill perfectly.
The future of web development lies with component based, stateful frameworks, such as JSF, Tapestry, Echo(2) and Wicket.
To answer to Michael's question... Wicket is highly recommendable. All people I've met (online/offline) speak highly of Wicket. All blog items are positive, except for those of Matt Raible, which are neutral. His entries are not based on actually working with Wicket, but more on what he considers important for his blog readers (number of job opportunities, and most importantly the availability of a book).
I find it very telling for the design and usability of Wicket that a professor is
using the framework
to teach students how to program web applications.
And I think that those users wanted to share their opinion (Kevin Taylor specifically asked for that). I guess they are apparently more vocal than users from other frameworks.
However, I think that a lot of people are using Wicket in trial projects to see what it is all about, and several people are already building business applications with it, I know I have and am.
We think that Wicket can become a great success, and are working hard to do so. Work has been started on writing a good reference manual (like those of Hibernate and Spring). This will solve a lot of questions arising on our mailinglists. I've posted the
work in progress
to my blog.
Innovation shouldn't and will not stop, but does it require you to start over every time? There is a lot of duplicated effort out there right now.
Most developers work for corporations of some sort. To constantly spend time learning webframe works is counter-productive. It also makes hiring developer talent slightly more challenging. Struts yesterday, tapestry today what will it be tomorrow?
Wicket: Reality? or Just Good Guerilla PR
At 11:37 AM on Aug 18, 2005, Michael Urban wrote:
Fresh Jobs for Developers Post a job opportunity
Today , Kevin reports some interesting results. The most recommended framework by readers who responded is Wicket.
Is this reality? Or just good guerilla PR?
71 replies so far (
Post your own)
Re: Wicket: Reality? or Just Good Guerilla PR
realityRe: Wicket: Reality? or Just Good Guerilla PR
I think page based frameworks are the future and at the moment there are not many of them. I have looked at JSF and well.. it feels quite complex. Tapestry is nice, but is very complex in the beginning. Wicket feels just right..The company I work for is planning to migrate to wicket (or another pagebased/componentbased webframework). But Wicket has the most chance at the moment because it is not complex.. and java developers are back in control.
Re: Wicket: Reality? or Just Good Guerilla PR
> I think page based frameworks are the future and at> the moment
How wrong can you get ????
Re: Wicket: Reality? or Just Good Guerilla PR
thats what I call a destructive statement. What exactly are you trying to say??Christian
Re: Wicket: Reality? or Just Good Guerilla PR
Not to sound like my late grandfather, but there are too many web frameworks these days. It seems every month someone is touting their web framework as the next big thing. A handful of people blog about it and it's suddenly considered a success.By the time a corporate entity decides to standardize on a framework it seems it's obsolete or considered too complex.
It's great for book publishers though!
Re: Wicket: Reality? or Just Good Guerilla PR
http://raibledesigns.com/page/rd?entry=wicket_is_the_most_widelyDon`t you get tired of yourself?
don`t you get tired of yourself? I do get tired of you. Give some good arguments or don`t reply. You are wasting my (and your) time with such stupid remarks.Re: Don`t you get tired of yourself?
Serge has a severe personality disorder that is exacerbated by the fact that he has no influence and nobody takes him seriouslyRe: Wicket: Reality? or Just Good Guerilla PR
"But there are too many web frameworks these days?"Are you saying just because there is a glut of so-so web frameworks, that developers should stop inovating? And I also gather by your statement that we should slow down a bit so corporations can "catch up"? Puuuuuuleasssse!!! The day I tailor my development strategies to placate corporations is the day I hang up my IDE forever.
If something is to complex, it should be replaced by something simpler and more elegant. From what I can tell, Wicket fits the bill quite nicely.
I don't mean to be combative, but the "sit on our laurels" attitude you proffer just didn't sit well with me.
-Scott
Re: Wicket: Reality? or Just Good Guerilla PR
Not to sound like my late grandfather, but there are too many web frameworks these days.Was your late grandfather really worried about too many web frameworks? j/k
In any case, what is your proposal - pass a law that nobody can develop another framework?
Maybe you should start programming in Ruby where there is just "one true" framework
Re: Wicket: Reality? or Just Good Guerilla PR
Most of the frameworks you refer to are also 'late'. If you look at the impressive list on the Wicket website , you will have to look hard to find a framework that is alive, has a userbase of more than 100 and is still under active development.The world is not waiting for yet another model2/web MVC/operation oriented framework. Struts, WebWork, and Spring MVC fit that bill perfectly.
The future of web development lies with component based, stateful frameworks, such as JSF, Tapestry, Echo(2) and Wicket.
Wicket Brings World Peace, Ends World Hunger!
To answer to Michael's question... Wicket is highly recommendable. All people I've met (online/offline) speak highly of Wicket. All blog items are positive, except for those of Matt Raible, which are neutral. His entries are not based on actually working with Wicket, but more on what he considers important for his blog readers (number of job opportunities, and most importantly the availability of a book).I find it very telling for the design and usability of Wicket that a professor is using the framework to teach students how to program web applications.
And I think that those users wanted to share their opinion (Kevin Taylor specifically asked for that). I guess they are apparently more vocal than users from other frameworks.
However, I think that a lot of people are using Wicket in trial projects to see what it is all about, and several people are already building business applications with it, I know I have and am.
We think that Wicket can become a great success, and are working hard to do so. Work has been started on writing a good reference manual (like those of Hibernate and Spring). This will solve a lot of questions arising on our mailinglists. I've posted the work in progress to my blog.
Re: Wicket: Reality? or Just Good Guerilla PR
Reply:http://www.jroller.com/page/dashorst?entry=wicket_most_widely_used_framework
Re: Wicket: Reality? or Just Good Guerilla PR
Innovation shouldn't and will not stop, but does it require you to start over every time? There is a lot of duplicated effort out there right now.Most developers work for corporations of some sort. To constantly spend time learning webframe works is counter-productive. It also makes hiring developer talent slightly more challenging. Struts yesterday, tapestry today what will it be tomorrow?