Re: Debugging AngularJS
Was working on a SPA project last year, built in VS, and all client debugging was done using Chrome developer tools. On Aug 8, 2015 4:15 PM, "Greg Keogh" wrote: > Folks, back to business ... I've done a crash course on AngularJS and I'm > writing a client-side demo app that talks to a Web API REST service. It's > working okay and growing, but I'm using the crude technique of just editing > the html and js files in Visual Studio 2015 without a project. Since VS is > just acting as a glorified editor I can't debug and any tiny stupid errors > in the files just causes everything to stop without reason. > > Are there others here who are writing this sort of client-side app and > have a way of getting a VS debugging experience? What's your technique? > > *Greg K* >
Re: Debugging AngularJS
> > Was working on a SPA project last year, built in VS, and all client > debugging was done using Chrome developer tools. > What about the editing experience, what did you use for that? -- *Greg*
Re: Debugging AngularJS
We were using VS 2013, which want too bad with JS intellisense, etc. Compile time checking would help, but I think that's only available for TypeScript. On Aug 8, 2015 5:29 PM, "Greg Keogh" wrote: > Was working on a SPA project last year, built in VS, and all client >> debugging was done using Chrome developer tools. >> > What about the editing experience, what did you use for that? -- *Greg* >
Re: Debugging AngularJS
> > We were using VS 2013, which want too bad with JS intellisense, etc. > Compile time checking would help, but I think that's only available for > TypeScript. > Okay, err, overall this isn't sounding great to me. I don't even have Chrome installed (I reckon it's a virus) and I see others are also using it for development. I have also found the VS2015 JS intellisense to be flakey and misleading. Does the JS development experience have to be so retarded? Surely others here must have some way of being as productive as we can be writing strongly typed languages in a good IDE?! This is the future of software development for web client apps is it? JavaScript is the typeless assembly-like script that is wrapped by libraries like jQuery to try and make it more digestible and round down the host incompatibilities, which is then wrapped by further libraries to create the illusion of binding and asynchrony. In previous decades I wrote reasonably serious "apps" in scripting languages like CLIST and Visual REXX, but there was an insanity point beyond which the limits of the language stonewalled you and you wasted time and you had to be mature enough to decide to move to a "serious" language and development environment. Sadly, in the 21st century, the scripting language (JavaScript) has become a cancerous growth that won't die after almost 20 years, it's been pushed to ludicrous levels of abstraction insanity, and the one great hope that could have killed it (Silverlight) was buried without a funeral. Oh well, back to writing JavaScript and html in Notepad (lucky I don't have to use punched cards). *Greg K*
Re: Debugging AngularJS
Quick Google search shows many JavaScript editors. As for the abstraction of JavaScript, there's always VanillaJS ( http://vanilla-js.com/). Vanilla JS is a fast, lightweight, cross-platform framework for building incredible, powerful JavaScript applications. As for JS being the future, I agree MS dropped the ball big time with Silverlight. On Aug 8, 2015 6:49 PM, "Greg Keogh" wrote: > We were using VS 2013, which want too bad with JS intellisense, etc. >> Compile time checking would help, but I think that's only available for >> TypeScript. >> > Okay, err, overall this isn't sounding great to me. I don't even have > Chrome installed (I reckon it's a virus) and I see others are also using it > for development. I have also found the VS2015 JS intellisense to be flakey > and misleading. Does the JS development experience have to be so retarded? > Surely others here must have some way of being as productive as we can be > writing strongly typed languages in a good IDE?! > > This is the future of software development for web client apps is it? > JavaScript is the typeless assembly-like script that is wrapped by > libraries like jQuery to try and make it more digestible and round down the > host incompatibilities, which is then wrapped by further libraries to > create the illusion of binding and asynchrony. In previous decades I wrote > reasonably serious "apps" in scripting languages like CLIST and Visual > REXX, but there was an insanity point beyond which the limits of the > language stonewalled you and you wasted time and you had to be mature > enough to decide to move to a "serious" language and development > environment. Sadly, in the 21st century, the scripting language > (JavaScript) has become a cancerous growth that won't die after almost 20 > years, it's been pushed to ludicrous levels of abstraction insanity, and > the one great hope that could have killed it (Silverlight) was buried > without a funeral. > > Oh well, back to writing JavaScript and html in Notepad (lucky I don't > have to use punched cards). > > *Greg K* >
Re: Debugging AngularJS
Greg, you could use VSCode, but I've not tried it out to see. Sublime might be a good JS editor. You realise that VS2015 is now in beta, and you are their main tester. They have sneakily put you on the team without your knowledge. Once you have found all of the bugs they will fix those, and release it for real. ;) And you thought Google was evil. On Sat, 8 Aug 2015 at 17:07 Grant Molloy wrote: > Quick Google search shows many JavaScript editors. > As for the abstraction of JavaScript, there's always VanillaJS ( > http://vanilla-js.com/). > > Vanilla JS is a fast, lightweight, cross-platform framework for building > incredible, powerful JavaScript applications. > > As for JS being the future, I agree MS dropped the ball big time with > Silverlight. > On Aug 8, 2015 6:49 PM, "Greg Keogh" wrote: > >> We were using VS 2013, which want too bad with JS intellisense, etc. >>> Compile time checking would help, but I think that's only available for >>> TypeScript. >>> >> Okay, err, overall this isn't sounding great to me. I don't even have >> Chrome installed (I reckon it's a virus) and I see others are also using it >> for development. I have also found the VS2015 JS intellisense to be flakey >> and misleading. Does the JS development experience have to be so retarded? >> Surely others here must have some way of being as productive as we can be >> writing strongly typed languages in a good IDE?! >> >> This is the future of software development for web client apps is it? >> JavaScript is the typeless assembly-like script that is wrapped by >> libraries like jQuery to try and make it more digestible and round down the >> host incompatibilities, which is then wrapped by further libraries to >> create the illusion of binding and asynchrony. In previous decades I wrote >> reasonably serious "apps" in scripting languages like CLIST and Visual >> REXX, but there was an insanity point beyond which the limits of the >> language stonewalled you and you wasted time and you had to be mature >> enough to decide to move to a "serious" language and development >> environment. Sadly, in the 21st century, the scripting language >> (JavaScript) has become a cancerous growth that won't die after almost 20 >> years, it's been pushed to ludicrous levels of abstraction insanity, and >> the one great hope that could have killed it (Silverlight) was buried >> without a funeral. >> >> Oh well, back to writing JavaScript and html in Notepad (lucky I don't >> have to use punched cards). >> >> *Greg K* >> >
Re: Debugging AngularJS
Why is Chrome a virus? I'd like to know so I can stop using it if necessary On Saturday, 8 August 2015, Greg Keogh wrote: > We were using VS 2013, which want too bad with JS intellisense, etc. >> Compile time checking would help, but I think that's only available for >> TypeScript. >> > Okay, err, overall this isn't sounding great to me. I don't even have > Chrome installed (I reckon it's a virus) and I see others are also using it > for development. I have also found the VS2015 JS intellisense to be flakey > and misleading. Does the JS development experience have to be so retarded? > Surely others here must have some way of being as productive as we can be > writing strongly typed languages in a good IDE?! > > This is the future of software development for web client apps is it? > JavaScript is the typeless assembly-like script that is wrapped by > libraries like jQuery to try and make it more digestible and round down the > host incompatibilities, which is then wrapped by further libraries to > create the illusion of binding and asynchrony. In previous decades I wrote > reasonably serious "apps" in scripting languages like CLIST and Visual > REXX, but there was an insanity point beyond which the limits of the > language stonewalled you and you wasted time and you had to be mature > enough to decide to move to a "serious" language and development > environment. Sadly, in the 21st century, the scripting language > (JavaScript) has become a cancerous growth that won't die after almost 20 > years, it's been pushed to ludicrous levels of abstraction insanity, and > the one great hope that could have killed it (Silverlight) was buried > without a funeral. > > Oh well, back to writing JavaScript and html in Notepad (lucky I don't > have to use punched cards). > > *Greg K* >
Re: Debugging AngularJS
> > Why is Chrome a virus? I'd like to know so I can stop using it if necessary > You can't stop using it. You still don't get it, do you?! Chrome will find you! That's what it does! That's *all* it does! You can't stop it! It'll wade through you, reach down you throat, and pull your f***ing HKLM out! (with apologies to James Cameron) -- *Greg*
Re: Debugging AngularJS
Everything mentioned above with Chrome can be done in IE11. And in my experience, it is quite usable now.. as for JavaScript, I'd suggest you move to TypeScript and 'suffer' the modest compiler overhead. There are lots of examples of working with Angular online. Also, I am using VSCode for all TypeScript/Aurelia work (and some Angular before that) and it works well. It is only a lightweight editor, but TypeScript intellisense is there if you organise your code around a tsconfig file - to help TypeScript with finding all your types. On 8 August 2015 at 22:05, Greg Keogh wrote: > Why is Chrome a virus? I'd like to know so I can stop using it if necessary >> > > You can't stop using it. You still don't get it, do you?! Chrome will > find you! That's what it does! That's *all* it does! You can't stop it! > It'll wade through you, reach down you throat, and pull your f***ing HKLM > out! (with apologies to James Cameron) -- *Greg* > -- http://benlaan.com
Re: Debugging AngularJS
The Atom TypeScript package is pretty good too - https://atom.io/packages/atom-typescript On 10 August 2015 at 14:48, Ben Laan wrote: > Everything mentioned above with Chrome can be done in IE11. And in my > experience, it is quite usable now.. > > as for JavaScript, I'd suggest you move to TypeScript and 'suffer' the > modest compiler overhead. There are lots of examples of working with > Angular online. Also, I am using VSCode for all TypeScript/Aurelia work > (and some Angular before that) and it works well. It is only a lightweight > editor, but TypeScript intellisense is there if you organise your code > around a tsconfig file - to help TypeScript with finding all your types. > > On 8 August 2015 at 22:05, Greg Keogh wrote: > >> Why is Chrome a virus? I'd like to know so I can stop using it if >>> necessary >>> >> >> You can't stop using it. You still don't get it, do you?! Chrome will >> find you! That's what it does! That's *all* it does! You can't stop it! >> It'll wade through you, reach down you throat, and pull your f***ing HKLM >> out! (with apologies to James Cameron) -- *Greg* >> > > > > -- > http://benlaan.com > > >
Re: Debugging AngularJS
Wait 'til Greg discovers Atom is built on Chromium. On Mon, Aug 10, 2015 at 3:10 PM, William Luu wrote: > The Atom TypeScript package is pretty good too - > https://atom.io/packages/atom-typescript > > On 10 August 2015 at 14:48, Ben Laan wrote: > >> Everything mentioned above with Chrome can be done in IE11. And in my >> experience, it is quite usable now.. >> >> as for JavaScript, I'd suggest you move to TypeScript and 'suffer' the >> modest compiler overhead. There are lots of examples of working with >> Angular online. Also, I am using VSCode for all TypeScript/Aurelia work >> (and some Angular before that) and it works well. It is only a lightweight >> editor, but TypeScript intellisense is there if you organise your code >> around a tsconfig file - to help TypeScript with finding all your types. >> >> On 8 August 2015 at 22:05, Greg Keogh wrote: >> >>> Why is Chrome a virus? I'd like to know so I can stop using it if necessary >>> >>> You can't stop using it. You still don't get it, do you?! Chrome will >>> find you! That's what it does! That's *all* it does! You can't stop it! >>> It'll wade through you, reach down you throat, and pull your f***ing HKLM >>> out! (with apologies to James Cameron) -- *Greg* >>> >> >> >> >> -- >> http://benlaan.com >> >> >> > -- w: http://jcooney.net t: @josephcooney
Re: Debugging AngularJS
So is VSCode! On 10 August 2015 at 14:43, Joseph Cooney wrote: > Wait 'til Greg discovers Atom is built on Chromium. > > On Mon, Aug 10, 2015 at 3:10 PM, William Luu wrote: > >> The Atom TypeScript package is pretty good too - >> https://atom.io/packages/atom-typescript >> >> On 10 August 2015 at 14:48, Ben Laan wrote: >> >>> Everything mentioned above with Chrome can be done in IE11. And in my >>> experience, it is quite usable now.. >>> >>> as for JavaScript, I'd suggest you move to TypeScript and 'suffer' the >>> modest compiler overhead. There are lots of examples of working with >>> Angular online. Also, I am using VSCode for all TypeScript/Aurelia work >>> (and some Angular before that) and it works well. It is only a lightweight >>> editor, but TypeScript intellisense is there if you organise your code >>> around a tsconfig file - to help TypeScript with finding all your types. >>> >>> On 8 August 2015 at 22:05, Greg Keogh wrote: >>> Why is Chrome a virus? I'd like to know so I can stop using it if > necessary > You can't stop using it. You still don't get it, do you?! Chrome will find you! That's what it does! That's *all* it does! You can't stop it! It'll wade through you, reach down you throat, and pull your f***ing HKLM out! (with apologies to James Cameron) -- *Greg* >>> >>> >>> >>> -- >>> http://benlaan.com >>> >>> >>> >> > > > -- > > w: http://jcooney.net > t: @josephcooney > -- http://benlaan.com
Re: Debugging AngularJS
Webstorm is a great Javascript IDE On 10 August 2015 at 17:20, Ben Laan wrote: > So is VSCode! > > On 10 August 2015 at 14:43, Joseph Cooney wrote: > >> Wait 'til Greg discovers Atom is built on Chromium. >> >> On Mon, Aug 10, 2015 at 3:10 PM, William Luu wrote: >> >>> The Atom TypeScript package is pretty good too - >>> https://atom.io/packages/atom-typescript >>> >>> On 10 August 2015 at 14:48, Ben Laan wrote: >>> Everything mentioned above with Chrome can be done in IE11. And in my experience, it is quite usable now.. as for JavaScript, I'd suggest you move to TypeScript and 'suffer' the modest compiler overhead. There are lots of examples of working with Angular online. Also, I am using VSCode for all TypeScript/Aurelia work (and some Angular before that) and it works well. It is only a lightweight editor, but TypeScript intellisense is there if you organise your code around a tsconfig file - to help TypeScript with finding all your types. On 8 August 2015 at 22:05, Greg Keogh wrote: > Why is Chrome a virus? I'd like to know so I can stop using it if >> necessary >> > > You can't stop using it. You still don't get it, do you?! Chrome will > find you! That's what it does! That's *all* it does! You can't stop > it! It'll wade through you, reach down you throat, and pull your f***ing > HKLM out! (with apologies to James Cameron) -- *Greg* > -- http://benlaan.com >>> >> >> >> -- >> >> w: http://jcooney.net >> t: @josephcooney >> > > > > -- > http://benlaan.com > > >
