Hi Lothar On Tue, Sep 16, 2008 at 2:27 PM, Lothar Kimmeringer <[EMAIL PROTECTED]> wrote: > >> Oh boy, you lost me. I'm not sure your point, but dynamic languages >> have the ability to test the server side in a runtime environment. > > Maybe we should talk about the word "test" here. Do you mean > trying out something and see a result without the need of > compiling and deploying something, than we have different > understandings of that. When I speak of testing I mean something > like JUnit (http://www.junit.org/).
Nope, we are talking the same language. I use unit testing and system testing. >> I think the only difference is that dynamic languages don't compile. >> Granted, that prevents some bugs, but not all bugs. > > To find the other bugs, test-frameworks help a lot and if > you change something half a year later breaking already > functioning code, the test-case shows you that. And I think > that the developing of testcases for the server-side of a > GWT-project when using the GWT-RPC-mechanism is easier > than other mechanisms like normal servlets. I can't comment on your comparison of GWT-RPC-mechanism and 'normal servlets', but I use a couple of different frameworks that full server side testing is very straightforward. So, I'm just not seeing that there is a great advantage in testing-efficiency between server X and server J. But, I could be missing something. -- 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 [email protected] 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 -~----------~----~----~----~------~----~------~--~---
