Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GWT just got a new look

gwtproject.org

Post reply on HN
Print view View original

61–70 of 70 posts

Re: GWT just got a new look

#61

Post by RossM »

taejo wrote: post #31
mradmin wrote: post #25

GWT pronounced «gwit» Seriously? First I've heard this is how you pronounce it. And how does one pronounce gwit? I think I'll continue to call it: G.W.T.

Yes, seriously (at least that's what I heard people at Google calling it). How many different ways could you pronounce "gwit"? (If you really don't get it, it's like "quit" but with a voiced consonant at the beginning).

I was seeing it as gee-wit. jwit also comes to mind.

Not that I have any stake in it, but the most confusing thing to me is that it doesn't mention the words "Google Web Toolkit" until the Tutorial page. It's an abbreviation; one that describes the product quite well (a toolkit for web apps, built by Google). Silly to bury it.

Re: GWT just got a new look

#62

Post by amelius »

killing_time wrote: post #56
amelius wrote: post #50

Earlier quoted context omitted.

Thanks for that link. I did a bit of reading, and found this [1]. > These are the main bottlenecks when scaling Meteor, and they introduce two main issues: 1. The polling and comparing logic takes a lot of CPU power and network I/O. 2. After a write operation, there is no way to propagate changes to other Meteor instances in real-time. Changes will only be noticed the next time Meteor polls (~10 seconds). This seems…

Specifically about this issue, see the section about the MongoDB oplog further down in the article. This removes the polling interval/overhead, so should significantly improve performance and responsiveness.

Ok. It indeed seems to be the case that the polling delay can be eliminated. But I'm wondering, if db-changes are written to the client directly, is it still possible to apply security rules to that? Evidently, I don't want all my db-changes to be written to all clients, and, preferably, a security-filter should be able to determine which clients receive which updates.

Re: GWT just got a new look

#63

Post by florian-f »

zamalek wrote: post #3

Gah! Again! People not explaining what something is on the landing page! > GWT is used by many products at Google, including Google AdWords and Google Wallet. It's open source, completely free, and used by thousands of enthusiastic developers around the world. Any amount of things fit that description. Beer? Air? Clicking "Learn about GWT" gets you this: > GWT is a development toolkit for building and optimizing comp…

I will let them now, or maybe create a pull request :D By the way, the site is here: https://github.com/gwtproject/gwt-site

Re: GWT just got a new look

#64

Post by florian-f »

prohor wrote: post #21
zamalek wrote: post #3

Gah! Again! People not explaining what something is on the landing page! > GWT is used by many products at Google, including Google AdWords and Google Wallet. It's open source, completely free, and used by thousands of enthusiastic developers around the world. Any amount of things fit that description. Beer? Air? Clicking "Learn about GWT" gets you this: > GWT is a development toolkit for building and optimizing comp…

I wonder though, why they don't mention the latest Google Inbox, which is also done in GWT.

It was updated very recently, after not being touched for quite a long time. I'm sure they will keep making it better over the next weeks.

Re: GWT just got a new look

#65

Post by florian-f »

needusername wrote: post #58

This http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsCom... seems to indicate that GWT still supports only Java 1.5. Is this true or simply outdated documentation?

No, currently it's 1.7 (with gwt2.7.0) and soon (when gwt 3.0.0 is released) it will support java 8.

Parts of the page are still rather outdated and haven't really been touched since 2010/ 2012.

This is why it's so great that the site got a new look now, it indicates that things are moving again and I'm sure the outdated parts are going to be removed soon.

Re: GWT just got a new look

#66

Post by florian-f »

JensRantil wrote: post #35

I'm surprised GWT is still used out there. It's slow as hell to compile and JS libraries are so much better and more response nowadays.

It's not exactly been bleeding edge the past few years. Now with the 2.7 release and the 3.0 release (which is hopefully coming very soon) it's receiving a major revival.

One of the most important new features are javascript interopt, which enables you to write libraries in java and let other people use it like any other js library. In the other direction, you can easily use javascript (libraries) in java. That means it's possible to just use modern stuff like polymer from within gwt without much of a hassle.

Re: GWT just got a new look

#67

Post by prohor »

polskibus wrote: post #48
prohor wrote: post #26

Earlier quoted context omitted.

First difference is that ASP.NET is running on the server side. GWT is fully compiled to JavaScript and runs in browser. The server doesn't even need to be Java, can be even plain web server without server side code. With GWT you typically develop one-page web applications. As of doing everything in code - not necessary. As of now GWT has UiBinder - it is a kind of template or DOM + widgets, where you then bind code…

Thanks for clarification. Does GWT assist in storing component state on the server?

No, not at all. There is no concept of a component on the server side in GWT. For GWT server is like a second tier, similar as you would write in JavaScript. Though, GWT gives you few ways to communicate with server:

1. RPC, which is in a way similar to RMI. It supports polymorphism, so you can get an interface in response and GWT will create correct implementation. Java is required on server.

2. RequestFactory, which is more focused on data transfer than implementation. It also allows to transfer data model, which in server is not compatible with GWT. Sends only delta of changes when sending back to server. Also requires Java on server.

3. REST. It is not maybe advertised that mutch, but GWT can work with any REST endpoint. It has built in JSON (de)serialization with AutoBeans; or you could also use Overlay types. There also some third party libraries for REST. This time server can be anything, just to return JSON.

But if you really want to have sibling component on the server side, then there is Vaadin - a framework built on top of GWT which has server-side components which synchronize with client-side counterparts. But then, all handlers are on server, rather than client as with GWT.

Re: GWT just got a new look

#68

Post by prohor »

prohor wrote: post #30
jamies888888 wrote: post #6

I've never knowingly seen GWT used in practice. Does anyone have any examples of (semi) notable websites utilising it?

Some other lists: - http://trends.builtwith.com/websitelist/Google-Web-Toolkit - but this might be seriously underestimated, as they are not able to detect services accessible after login, where GWT is mostly used. - http://ars-codia.raphaelbauer.com/2011/12/why-google-web-too... Other that I'm aware of: - https://www.cloudorado.com/ - https://ruxit.com/ - their service once you log in - http://gogrid.com/ - again af…

Two more that I recalled:

- Angry Birds web version

- web mail at http://wp.pl (one of the major mail services in Poland)

Re: GWT just got a new look

#69

Post by killing_time »

amelius wrote: post #62
killing_time wrote: post #56

Earlier quoted context omitted.

Specifically about this issue, see the section about the MongoDB oplog further down in the article. This removes the polling interval/overhead, so should significantly improve performance and responsiveness.

Ok. It indeed seems to be the case that the polling delay can be eliminated. But I'm wondering, if db-changes are written to the client directly, is it still possible to apply security rules to that? Evidently, I don't want all my db-changes to be written to all clients, and, preferably, a security-filter should be able to determine which clients receive which updates.

Yeah - the very earliest preview versions of Meteor had this obvious gap where reads and writes were basically a free for all. However, it's changed a lot since then. As a development crutch the aptly-named 'insecure' package is installed by default (which maintains the free for all), but you're expected to remove it and able to apply fine-grained control to which clients can C/R/U/D which data.

These two steps of the Meteor tutorial probably describe it best: https://www.meteor.com/try/10 https://www.meteor.com/try/11

Re: GWT just got a new look

#70

Post by jzaruba »

kosinus wrote: post #32
zamalek wrote: post #3

Gah! Again! People not explaining what something is on the landing page! > GWT is used by many products at Google, including Google AdWords and Google Wallet. It's open source, completely free, and used by thousands of enthusiastic developers around the world. Any amount of things fit that description. Beer? Air? Clicking "Learn about GWT" gets you this: > GWT is a development toolkit for building and optimizing comp…

Not even that is enough. My train of thought was: "This is the Java thing, right?" But I wasn't sure, and it's not mentioned anywhere in the opening paragraph of that page either. Java is not mentioned until "The GWT SDK contains the Java API libraries, compiler, and development server."

That might be on purpose. Way too many people (even seasoned Java pros) tend to dismiss GWT based on the WRONG assumption that "GWT runs on Java". Not mentioning Java in the very first sentence might by an attempt to avoid this seemingly minor yet critically important misconception.
Post reply on HN