On Tue, Sep 16, 2008 at 1:41 PM, John <[EMAIL PROTECTED]> wrote: > > Thanks for the suggestions everyone. Definitely some things to think > about in them. > > I probably should have explained that I am looking at things more from > an architecture design view. I am not likely going to do very much > coding on this myself, but I don't want to end up with the ball of mud > that can be JavaScript, which is likely without GWT - probably an > assumption but based on a lot of feedback from people with some > experience in large JavaScript projects that have multiple developers > involved. > > I realise that in principle pretty much any language could be used > server side and GWT could still be used, but it seems initially at > least that a lot of the benefit of a single language with a single IDE > would be lost doing that. The other probable advantage to Java + GWT > over say Django + GWT is that a developer with the skills to work on > the back end could also work on the front end and vice versa. In my > mind there is a fairly large difference between a Java expert and > someone that "knows some Java" in the same way that there is a > difference between a Django expert and someone that "knows some > Django" in terms of efficiency of code as well as development and > debugging time. Hence I am wary of getting someone to code the back > end in Django as well as the front end in Java (GWT). > > The question I suppose really comes down to how much simpler it would > be keeping things all in Java v. splitting it between two languages?
I think it really depends on the existing skills within your company. The main thing to remember is that GWT is really a compiler that generates client side javascript. Web 2.0 brought js to the client. Web 2.5 (as I call it) brings Rich Internet Applications. However, when developing a website, the basic skills are still required, HTML, CSS, RSS, browser protocols, http headers, and the list goes on. Using GWT today is similar to using JS two years ago. The web developer worked in whatever language they were using, and, Oh, by the way, to get these cool new features, I have to learn and use javascript. It is similar today. If you are building web apps with framework X and want the new coolness offered by GWT, then, well you brush up on your Java and code away. You probably don't want to say, ah, gosh, I need to change my whole framework cause this cool client side technology is using Java. I never heard that argument from anyone using javascript with Web 2.0, and I'm sure it could have been made for extJS. But as I say, I never saw that promoted. My point, which is from the non Java camp, is that I code about 100 lines of Java client code for every 1 line of server side code. While I have not coded a Java server, I have not heard anyone mention that java server code is so minuscule that you really don't even need to include it in your decision making. If you have java server talent in house and it won't slow down development, I say use it. But sometimes I think Java is like a drug and it's users get caught up in it and don't see the costs it forces on them. I used to code C++ years ago, and I have dabbled with Java over the last 15 years. But, GWT is the first time I have used Java in anger. It has a simple C style syntax and is straightforward, albeit cumbersome, to code in. The real hurdle for people new to this technology, is not due to GWT or Java, but is the asynchronous even-based coding style. That takes people some time to adjust too. I have read that Swing programmers adapt readily to GWT, so you you may want to consider swing experience if you are hiring. Bottom line, move forward from your strengths, don't change whole frameworks expecting to obtain the holy grail of synergy, because I don't see anyone claiming those benefits, let alone achieving them. $0.02 Cheers -- Jim Freeze --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
