My brother also works at Google. Are you saying he is a virus writer? One could argue the same about Microsoft. And Yahoo. And Facebook. And <Insert large organisation>. Perhaps you are against large corporations, and capitalism? Jealousy?
It sounds like you are frustrated with things that don't work as you expect them. I see a number of alternatives for you. 1. Don't use them. Write it all yourself. Oh, what's that? it would take too long? Hmm.. quite a dilemma you have there... Standing on the shoulders of giants, using the fantastic work that fellow humans have created (with the mix of quality that goes with said complex systems) is a double edged sword. Yes, you get the bugs, but you also get the hundreds and thousands of man hours that went into it. Choose. 2. Retire. If you long for the simple days of when you could code from a book on the shelf, and that book contained all there was to know, then you are out of luck. Those days are gone. They are inventing this stuff faster than anyone can learn it all. Almost daily, I turn and find some new tool or framework or something exciting and new and shiny. And the next day something I was using is dead and buried. (I'm looking at you Silverlight). 3. Suck it up and roll with the punches. This job is fun and exciting, and often at times, frustrating. But I love it and wouldn't give it up for anything else. I don't know it all, and never will. I love learning new things and strive for personal improvement. Writing code is becoming more expensive because it is becoming more complicated. Embrace change and do the best you can. Flower where you are planted. (my favourite motto). Don't forget to stop and eat the roses. :) On Tue, Jul 9, 2013 at 12:04 PM, Joseph Cooney <[email protected]>wrote: > My brother works on the chrome team. Are you saying there is something > improper about the work he is doing? > On 9 Jul 2013 13:38, "Greg Keogh" <[email protected]> wrote: > >> Thank chaps, I'll have to look into Chrome, although I've never >> previously allowed it only my work machines because it's like a virus, >> everything from Google is like a virus. >> >> I would like to mention that in the previous hour I've been cobbling >> together my price-calc html page, I have needed to run a web search on how >> to code each individual line: set and get a checkbox, detect textbox >> changes, disable a control, set text in a span, etc. all absolutely >> fundamental things you need to do. The inconsistency and patternless >> quagmire is beyond human endurance. Did the inventors of JavaScript, jQuery >> and DOM invent this stuff to hamper the progress of the human race? The >> inventors of this mess should be hunted down if they're still alive and >> strangled with their own entrails. Examples that need a search for each >> line and I find absolutely no consistency at all (the first one is utterly >> cryptic): >> >> Is a checkbox checked -- $('chk1').is(':checked') >> Set text in a span -- $('#span1').text(thevalue) >> Set text in a textbox -- $('$text1').val(something) >> Disable a control -- $('radio1').attr('disabled', show) >> >> Even worse, most search results have screenloads of people arguing about >> what bit of sample code is correct. There are sometimes 6 suggestions of >> how to do a single thing, and 4 of them don't work. The official jQuery API >> server is offline which makes my experience even better. I'm sure I'll feel >> better once I can see some sort of pattern in the jQuery/DOM chaos. >> >> Greg K >> >> On 9 July 2013 13:04, Jorke Odolphi <[email protected]> wrote: >> >>> Chrome has by far the best debugging experience – very similar to how >>> it works with .net – and its the same experience on each platform - >>> (although osx makes you do unnatural acts with key combinations). I've >>> found I've been writing code on the console to validate it, and its super >>> easy for debugging ajax as well. Some very nice profiling things there as >>> well – really lets you tune the rendering etc. >>> >>> I tried the tool chaining with VS and it was just too hard to make it >>> work, although I do rate VS as the best JS editor (before sublime :) ) >>> >>> >>> From: "[email protected]" <[email protected]> >>> Reply-To: ozDotNet <[email protected]> >>> Date: Tuesday, 9 July 2013 12:31 PM >>> To: ozDotNet <[email protected]> >>> Subject: jQuery debugging >>> >>> I'm trying to create a single html page with jQuery inside to >>> interactively calculate a price total based upon the settings of other >>> controls. It's a classic sort of "make you order" page. >>> >>> Can I get a familiar debugging experience like I'm used into in Visual >>> Studio while writing this page and scripts? I haven't written any >>> JavaScript for years and I have no idea what's available to help me these >>> days. There must be some people in this group writing plain JavaScript or >>> jQuery in their html pages, so what do you do to keep productive? >>> >>> Greg K >>> >>> >> >>
