I have to disagree with this attitude about time consuming computations. It's about how are we looking at this problem. I agree that client side code shouldn't be just presenter of text data or "eye- candy" animation maker. I'll try to explain why I think that time consuming computations don't belongs to cliend side. As @Uemit said, yes computers are still faster and faster, but you forget to mobile devices which are getting more and more popular in daily use. Last two years are in trend of tablets and smartphones as main work tools, yes they are faster and faster but still, can you imagine that most pages/ apps will do time consuming or high CPU operatoions in browsers? If I said that I hate when my smartphone is drained after end of every day, then most of you will agree with me that you hate it too.
And this is my only reason why I don't recommend to have these kind of alghoritms on cliend side code. You can create highly valuable applications without need of creating they native app clone on smartphones, because your web app is too big or too slow or after 2 hours of using it mobile user will be very upset about battery state. OrNOt: for image processing has Google API very good interface. On 8 lis, 10:19, OrNOt <[email protected]> wrote: > @Palo,G: > Uemit is correct. There are many cases that need client computing and > specific algorithms, for instance, image processing, especially for > those which > need prompt interactivity. You can not always push the data to the > sever to > process and then get the result back to show. In low bandwidth > internet, > that will bring the user to kill himself. > > At least till now, the GWT is commonly used for text-based > applications, say > ,information system. As the HTML5 comes into play, more and more > canvas or > webgl based web applications will be made by J.S.and most of them need > intensive client computing.I believe the IP issue will become more and > more important. > > Actually it is hard for me to understand why J.S., such a poor > language, is becoming so popular. Sun,the stupid giant, made too many > mistakes that let java , so great language, lose his position in > internet era. In some sense, the GWT project is damn ironic,isn't? > > On Nov 8, 12:29 am, Uemit <[email protected]> wrote: > > > > > > > > > @Harpal Grover: > > Actually there might be a solution right now. You can use Native Client > > SDK<http://code.google.com/chrome/nativeclient/>to develop a C++/C > > application which runs in the browser. The application > > will be compiled to a binary and then transmitted to the client/browser > > where it is executed in a sandbox. It is still possible to use > > a Dis-assembler in order to figure out the algorithm however it is much > > harder than obfuscated javascript code. > > However until now NaCl is only supported in Chrome. -- 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.
