The problem with GWT has always been misconceptions and lack of informations. While the GWT project homepage has improved a lot. it still super difficult to find the right informations.
I remember my first meeting with customers when I said "what about writing this entire thing in Java with GWT ? " The answer was "No way we will use applets here. Are you mad ? " Then I always have to answer Question like "what if there is a problem with the generated JavaScript code ? Can I have a look ? Do we even need to have a look ? " When I said "You want to target web, mobile web, native mobile and desktop from one code base ? GWT is the way to go" They look at me like I m crazy. Other problem is showcases. People are building great products, libraries but it s hard to find it. I mean products like animatron.com should be right at the first page of the GWT project home page. I mean look at the JS community. For every single little thing they do their advertise it like crazy. You almost think Angular JS invented two way databindig :). Off course the argument is always "It s opensouce. Just contribuate it". Miss the days where there was a real developer advocate for GWT at Google (David :) ). On 20 January 2016 at 10:09, Stefan Bylund <[email protected]> wrote: > Google's web crawler (Googlebot) has improved substantially lately when it > comes to crawling dynamic HTML pages generated with JavaScript. It does not > simply crawl the initial HTML page but executes any JavaScript and then > crawls the resulting HTML page. You don't have to do the cumbersome > hashbang (escaped fragments) workaround any more. I have not had any > problems with indexing GWT web apps with Google's web crawler. See this > article for more info: > > > http://searchengineland.com/tested-googlebot-crawls-javascript-heres-learned-220157 > > However, I think that Bing's web crawler still have problems with indexing > dynamic HTML pages generated with JavaScript. But with Google's market > share I don't see that as a problem. > > /Stefan > > > Den onsdag 20 januari 2016 kl. 06:35:30 UTC+1 skrev Adolfo Rodriguez: >> >> Hi, the title is provocative. I wanted to ask 2 questions in the same >> thread. I love GWT, no doubt is the framework that delivers higher >> productivity. But I quit using it 2 years ago because google robots where >> not able to properly index my pages despite I implemented the escaped >> fragment specs >> <https://developers.google.com/webmasters/ajax-crawling/docs/specification>. >> Disappointing. >> >> On the other hand, I would expect much more traction in a Java framework >> than can combine presentation (Bootstrap) with presentation login (any JS >> libraries) and server side. But barely you can see job openings in the >> market demanding GWT. Even, the last message in this list is 40 days old. >> >> So, I want to raise the question: >> >> * what is stopping GWT against other frameworks? Is the problem with >> crawlers? >> >> * what i the current status of crawler, HTML generation and search engine >> robots? >> >> I have a mixed feeling with GWT, I love it... but my experience says that >> I should not use it. >> >> Thanks >> >> >> >> -- > You received this message because you are subscribed to the Google Groups > "GWT Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- Alain Ekambi Co-Founder Ahomé Innovation Technologies http://www.ahome-it.com/ <http://ahome-it.com/> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
