On 10/20/15, 4:06 PM, "Harbs" <harbs.li...@gmail.com> wrote:
>You should know that I’ve spent the last few weeks (or longer) struggling >with an AngularJS application. My opinion of AngularJS is that it’s >broken by design. > >Comparing the organization and clarity of a FlexJS application to an >AngularJS application is literally night and day. > >I was able to crack open the MapSearch example and understand exactly >what is going on in under a minute. > >I’m really excited about getting started on building something real with >FlexJS. > >I have two semi-concerns though: >1) Why is the js of these relatively simple examples so big? Is it >missing a minifying stage of Google Compiler? Yes, we’re not currently minifying much at all. I am going to try to re-enable it as an option. >2) How does debugging work? Assuming you are targeting only JS, is it >necessary to debug in the compiled JS in the browser or is it possible to >debug in the source code somehow using code mapping? > Well, my vision for FlexJS was that folks would build a SWF and debug the SWF since, IMO, there are better debugging tools in Flash Builder, and the Flash runtime will catch errors that the JS runtime will not. There would still be times when you have to debug the JS and if the error reproduces in the bin/js-debug version then you can use whatever JS debugger you want. If the error only reproduces in the bin/js-release version, then yes, you have to try debugging with the source maps. I’ve found debugging the js-release version to be painful even with source maps, especially when minification is on. -Alex
