tag:blogger.com,1999:blog-3895474834344383709.post6831661523045308640..comments2024-02-18T00:38:41.871-08:00Comments on GWT Sushi: Initial Thoughts on Vaadin : Not so much a GWT complement more of a replacement.Anonymoushttp://www.blogger.com/profile/17596228613938166964noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-3895474834344383709.post-71513969645355513452010-08-30T01:48:09.055-07:002010-08-30T01:48:09.055-07:00Nice article, good comment input. What are the opt...Nice article, good comment input. What are the options for a big business application?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3895474834344383709.post-88021335379185870932010-08-18T08:58:18.045-07:002010-08-18T08:58:18.045-07:00I would agree with your thoughts on Vaadin; I'...I would agree with your thoughts on Vaadin; I've only recently come across it myself and thought I should have a look because I'm in the process of selecting a framework for a major GWT project.<br /><br />For a small application without many users, I can see the rapid development benefits. However, I'm looking to build a network management application that may eventually have 100s of simultaneous users and they'll want real-time event notification (read comet, websockets etc.).<br /><br />Vaadin is pretty nifty, but you'd have to be sure that it's the right tool for the job.<br /><br />Cheers!Peter Stronghttps://www.blogger.com/profile/03210939832680333973noreply@blogger.comtag:blogger.com,1999:blog-3895474834344383709.post-2800512150681305142010-08-07T12:59:02.993-07:002010-08-07T12:59:02.993-07:00On speed of deployment versus application performa...On speed of deployment versus application performance:<br /><br />Performance is always an important issue when designing any type of IT application. Its position in the priority list is different depending on the application type. After working for a variety of business which utilise bespoke in-house IT software, their main concern is always on how fast the software can be developed. The need to have an application perform well is secondary to that, unless it becomes a problem. Vaadin is an ideal solution in this arena, its speed of development is impressive. In the greater software development world with applications like Gmail, Hotmail and Salesforce, performance is one of the highest priorities because these applications will get many thousands of users, and performance should be incorporated to the very core of every design decision. <br /><br />I guess we are saying similar things and I agree that there is a minimum level of performance that is required in any software application. Our choice of framework is based on how the application is to be used and I would be wary about choosing a server-centric framework over one which only contacts the server when it needs to. <br /><br />Thanks for your comment and the interest in the article.<br /><br />Gene<br /><br /><br />Therefore my conclusion that Vaadin is useful in the bespoke softwareAnonymoushttps://www.blogger.com/profile/17596228613938166964noreply@blogger.comtag:blogger.com,1999:blog-3895474834344383709.post-61608593502761504202010-08-07T12:09:27.589-07:002010-08-07T12:09:27.589-07:00You said:
"In business, typically the speed ...You said: <br />"In business, typically the speed of development and deployment is more important than how well your application performs. The function of the application may never reach more than 100 users, so the load on the application will never be high."<br /><br />I have to disagree. Speed of development and deployment is important but the importance of the performance of your application exceeds that. The customer is paying for an application which is bound to certain SLA requirements.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3895474834344383709.post-75142862938958643582010-08-06T19:45:58.464-07:002010-08-06T19:45:58.464-07:00IMO, Vaadin uses GWT for two things: component dev...IMO, Vaadin uses GWT for two things: component development and marketing purpose.<br /><br />Vaadin has its own lifecycle that means it is hard to use GWT made by other vendors, such as SmartGWT and ExtGWT.<br /><br />The worst is there is no way to write any client code that GWT really aims for and good at. From their demo, the only think an application developer can do is to send JavaScript codes to the client and the JavaScript code has no way to access any component (due to GWT name mangling adn lifecycle difference)<br /><br />All application code runs at the server. Unless you want to write a component, there is no connection to GWT at all.Markhttp://markus.usnoreply@blogger.comtag:blogger.com,1999:blog-3895474834344383709.post-31798524887821614362010-08-04T06:11:26.938-07:002010-08-04T06:11:26.938-07:00The relation between Vaadin and GWT is: 1) Vaadin ...The relation between Vaadin and GWT is: 1) Vaadin uses GWT internally to implement rendering, 2) Vaadin can be extended - new re-usable widgets can be implemented - with GWT.<br /><br />GWT and Vaadin optimizes different things: GWT tries to minimize server-load by moving as much as possible to client, Vaadin tries to minimize development time by keeping most of the code in the server. For most cases server-side programming gives good performance, but for some situations (animations, interactive graphs, ..) client-side programming is needed - in those situations one must implement a new widget to Vaadin. Fortunately this is really easy.<br /><br />Scalability of Vaadin's server-side model depends on application. It is typical to be able to handle tens of thoudands concurrent users per server. Depending on your application, this might translate to millions of daily users - per server.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3895474834344383709.post-78133906951001736292010-08-04T03:43:59.000-07:002010-08-04T03:43:59.000-07:00I share your thoughts. I've never seen Vaadin ...I share your thoughts. I've never seen Vaadin as a GWT library, but I agree that writing code in Vaadin is really pleasant, nevertheless it is much slower than pure GWT.<br /><br />I've just tried Vaadin to write some code, not to create a production application, but I'm afraid that creation of custom components (in GWT) is needed to fix cases where performance is not enough.Luciano Vernaschihttp://www.cromoteca.com/noreply@blogger.comtag:blogger.com,1999:blog-3895474834344383709.post-70151941837938083322010-08-03T10:47:13.595-07:002010-08-03T10:47:13.595-07:00I think you got it right. Vaadin is a server-side ...I think you got it right. Vaadin is a server-side component framework focusing on speed of development while GWT is used on client-side to render the rich user experience. It is good idea to make all new Vaadin component as a standlalone GWT widgets too - to benefit both frameworks. For a scalability analysis see: http://vaadin.com/blog/-/blogs/server-side-ria-scalabilitySamihttp://vaadin.com/saminoreply@blogger.com