What does debugging hibernate/hazelcast have to do anything with debugging the frontend (GWT) part ?
Yes, debugging in SDM has it's pain points but apart from Dart (which has its own Chrome version Dartium) every transpiled/compiled languages relies on source maps and the browser's DevTools, so you can be sure that this will become better and better. Apart from that Chrome Dev Tools provide many pretty cool features to debug client side apps ranging from detecting memory leaks to performance flame charts, etc. Also being able to directly manipulate the generated HTML in the dev tools is quite powerful. On Tuesday, March 3, 2015 at 9:49:47 AM UTC+1, Liam Stewart wrote: > > Debugging javascript is a king size pain in the arse if you live and > breath Java, super dev mode is still nowhere near good enough to *really* use > when you have a lot going on and you need to step through and evaluate line > by line the state of the application at runtime, this becomes particularly > important if you are delving deeply into hibernate and hazelcast > environment like we do. > > I was tasked with evaluating IntelliJ as a viable alternative after we > went to GWT.create this year, I used it for a morning and wasn't impressed > with what I saw... it is painfully obvious you are debugging javascript as > the values you want are hidden down inside elements and the debugger simply > won't play ball at times, having to put in a debugger API call if you > actually do really want it to stop is ridiculous... > > I've attached an image of how I feel google has responded to the issue of > dev mode - if they really cared about the developers they would have just > released a dev version of chrome or something for us, not dropped us in it > with a super dev mode that 'will definitely be good, honest, promise... at > some time in the infinite future'. > > Grumble. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
