FYI: Creating circular references is a perfectly OK thing to do.
in [JavaScript]
|
From: David Mark on 26 Jul 2010 18:45 On Jul 26, 9:01 am, Ry Nohryb <jo...(a)jorgechamorro.com> wrote: > On Jul 26, 2:45 pm, David Mark <dmark.cins...(a)gmail.com> wrote: > > > > > Get help, Jorge. Seriously. > > You know, deep inside, that I'm right on this one. No I don't. I'll direct you to my previous comment (which you cropped), as well Richard's. What part of "quixotic" do you not understand? :) Get better, Jorge! Your office will be waiting for you when you get back...
From: David Mark on 26 Jul 2010 18:46 On Jul 26, 9:07 am, Ry Nohryb <jo...(a)jorgechamorro.com> wrote: > On Jul 26, 2:48 pm, Richard Cornford <Rich...(a)litotes.demon.co.uk> > wrote: > > > > > <URL:http://en.wikipedia.org/wiki/Tilting_at_windmills> > > Yeah... resistance is futile ? > Why are you trying to resist an "army" of windmills. Doesn't make sense, does it? Take some time off, Jorge. Really.
From: David Mark on 26 Jul 2010 18:49 On Jul 26, 5:05 pm, Ry Nohryb <jo...(a)jorgechamorro.com> wrote: > On Jul 26, 4:09 pm, Tim Down <timd...(a)gmail.com> wrote: > > > > > > > On Jul 26, 1:16 pm, Ry Nohryb <jo...(a)jorgechamorro.com> wrote: > > > > LET'S MAKE THIS CLEAR: > > > > Creating circular references is a perfectly OK thing to do, what's > > > BOTCHED is/are MICROSOFT's INTERNET EXPLORER (all versions): its - > > > their- garbage collector which is broken, and that's what produces the > > > memory leaks. It's not my/your/our fault. It's solely Microsoft's. > > > > OTOH, whenever you do extra work and code fixes/workarounds for these - > > > IE's- memory leaks in your page/web app, you're: > > > > 1.- Wasting your time. > > > 2.- Wasting (somebody's) money. > > > 3.- Making your code more complex, unnecessarily. > > > 4.- Aggravating the problem, because Microsoft won't ever feel the > > > need to fix what you're fixing for them, and for free. > > > > So, if you/we/them don't ever fix their (IE's) bug(s), people will end > > > up, sooner or later, seeing that The Web works well everywhere but in > > > IEs, and either : > > > > -Microsoft will have to fix their browsers' bugs -finally-, > > > > or, > > > > -People will switch to another browser, one that works, of which there > > > are at least four very nice ones: FireFox, Opera, Safari and Chrome. > > > > Have a nice day. > > > -- > > > Jorge. > > > Microsoft now seem to be following a strategy of releasing new and > > dramatically improved versions of Internet Explorer and encouraging > > people to switch to them. What else do you want them to do? > > I'd just like them to fix their most ugly and long-standing bugs > (circular references, named function expressions, innerHTML, host- > objects' eccentricity, etc.), and I'd like if it didn't take them 10+ > years to fix them. They invented innerHTML, Jorge. They documented it fairly well also. What more can you ask? > > And I'd like full, 100% compatible, bug-free HTML5 support. And the > <canvas>, please ! > IE9 looks very good, but you'll still have to write competent scripts that work in IE < 9 for years to come. I know. Life is so unfair. :(
From: Ry Nohryb on 26 Jul 2010 19:32 On Jul 26, 11:18 pm, Asen Bozhilov <asen.bozhi...(a)gmail.com> wrote: > (...) if you write for any > environment with reference counting GC you will have the big issue. > The good habits are the best solution in this case. I really don't > care about circular reference pattern, just because I don't use it. > The circular reference pattern must be fixed during design stage of an > application. > (...) Bullshit. The only botched GC is the one in Microsoft's Internet Explorer(s). Except when coding -defensively- against Microsoft's IE's bugs, there's nothing to "fix during design stage of an application" wrt circular references. And, many JavaScript/Web programmers -like you- ought to quit this awful habit of styling and circumscribing the code to the -pitiful- subset of JavaScript/DOM that remains after cutting out and removing the -many- broken pieces in Microsoft's JScript+ the IE DOM. Or more or less convoluted workarounds. How many millions of man hours have been/are still being wasted due to the habit of coding workarounds for IE's bugs ? You should instead try to make it as evident as possible to the site visitors: inform them that their browser is broken, and that that's NOT your fault/the site's fault. And please don't pretend that the users of your site(s) are all stupid. Most of them are perfectly able to switch IE for another - good- browser that works, *as*soon*as*/if the need arises (corporations included). -- Jorge.
From: Ry Nohryb on 26 Jul 2010 19:36
On Jul 26, 11:49 pm, David Mark <dmark.cins...(a)gmail.com> wrote: > > They invented innerHTML, Jorge. They documented it fairly well also. > What more can you ask? Oh, I don't know... that it worked with tables, for example ? They invented the XHRs, too. +1 to them for that. -- Jorge. |