How does Pivot compare to the Google Widget Toolkit (GWT)?
While GWT allows developers to use the Java language to write web-based applications, the runtime enviroment for a GWT application is the browser itself, not a JVM. This has a number of drawbacks: • The compiled code executes as interpreted JavaScript, not bytecode. While browser vendors have made great strides recently in improving JavaScript performance, there are still many layers between the application code and the actual runtime environment. There are far fewer layers in a Pivot application – this results in less code to execute and translates to better overall performance. • The only language features and APIs available are those that can be supported by the browser and have been ported to GWT by Google. For example, there is no support for multi-threading, network, or I/O operations. Pivot applications have access to the full feature set of the Java Virtual Machine, including all standard Java libraries and APIs as well as any third-party libraries. • All presentation must be d
Related Questions
- Are Page Speeds recommendations more applicable to applications developed with the Google Web Toolkit (GWT) rather than with handwritten JavaScript code?
- Can I access a chart from an application written with the Google Web Toolkit (GWT) compiler?
- How does Pivot compare to the Google Widget Toolkit (GWT)?
