You have been watching us through our webcams, haven't you? Ah come on... Just admit it... It's okay...
I must say I do agree with your first line... After that it got a bit blurry. See I always thought that the guyz using only global vars with obscure names calling them from god-knows-where, were going for the job security thing. Apart from that, your email takes a kind of i-won't-use-names-but-I'll-try-to-offend-you-all anyway tone, and your assumptions are just plain wrong on multiple levels. As I said simply the tone of your email makes it clear there is no use discussing it as well, you seem to have it all sorted out. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steven Sacks Sent: Wednesday, February 01, 2006 8:43 PM To: 'Flashcoders mailing list' Subject: RE: [Flashcoders] Tell me more about "_global" Let's make classes for everything. Let's make components out of everything. There are so many benefits to complicating things and we CAN do it so we SHOULD do it because it's so clever and smart to do it that way. Let's code everything in one frame when working closely with designers so we can make them feel stupid and helpless when they go into our application and can't find anything and we can feel so superior to them because it's so obvious and now we have to walk them through it and by doing so can show them how smart and clever we are. Let's stroke our egos to prove what smart coders we are and program job security into our applications by making it extremely difficult for our clients to hire anyone else to work on our code, especially considering we might not be available (busy, vacation, dead) to help walk anyone through the complicated messaging system we've put into place to do something as simple as storing global variables. It's such a clever way of doing things, don't you see? We've built a better mousetrap! Those people using a simple global namespace objects are suckers! I'm not saying variable watchers and events don't have their place, but we're talking about a global namespace to store variables available to the entire application, a replacement for _global and the conflicts that can arise from it, something that has been done longer than you've been coding. You're acting like a simple global namespace to store variables is only for noob coders and that really smart coders make their code super complicated. You guys are the reason Dreamweaver MX 2004, Photoshop 7, etc. take 10-20 seconds to start up instead of 1-3 like their predecessors. You guys are the reason many clients have bad tastes in their mouths from working with independent contractors. Why not apply your cleverness and creativity to planning your next D&D campaign or go learn a real programming language like C and learn to program games if you're so smart. As far as debugging goes, I've never had trouble with standard debugging techniques. You know, like trace() and NetDebug.trace(). Quick and easy. Here's my debug code: import mx.remoting.debug.NetDebug; NetDebug.initialize(); _global.out = function(m) { trace(m); NetDebug.trace(m); } Oh noes! It's not complicated enough for you! Feel superior in your complicated debugging style! ;) _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
