Prev: how to assign a id as a variable
Next: Initializing a global namespace object
From: David Mark on 26 Jul 2010 20:52
On Jul 26, 8:16 pm, Ry Nohryb <jo...(a)jorgechamorro.com> wrote:
> On Jul 27, 12:49 am, David Mark <dmark.cins...(a)gmail.com> wrote:
>
>
>
> > IE9 looks very good
>
> To whom ?

To me (among others).

>
> Does it -finally- come with the <canvas> ?

Yes, Jorge; there is a canvas. Why don't you climb down from your
high horse and survey the territory...

>
> > but you'll still have to write competent scripts
> > that work in IE < 9 for years to come.
>
> Ah, No no no. Not me. I won't. Thanks but no, thanks.

Then you won't be employable as a professional Web developer for years
to come. Of course... :)
From: Matt Kruse on 27 Jul 2010 00:02
On Jul 26, 7:09 pm, Ry Nohryb <jo...(a)jorgechamorro.com> wrote:
> On Jul 27, 1:52 am, "Michael Haufe (\"TNO\")"
> > > Bullshit. The only botched GC is the one in Microsoft's Internet
> > > Explorer(s).
> > Which one? You do realize that the problem is partially related to the
> > fact that there is more than one right?
> No. More than one what ? more than one GC ?

I believe that's the root of the problem, isn't it? The GC for jscript
objects is separate from the one for host objects, and they don't talk
to each other. So they cannot resolve the circular reference to
realize that both objects may safely be destroyed. They just each see
an external reference count of 1 and remain in memory forever.

Matt Kruse
From: Asen Bozhilov on 27 Jul 2010 02:04
Ry Nohryb wrote:
> Asen Bozhilov 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).

Please follow the posted link. As I wrote the problem is in the
programmer, not in GC. If you write application with XPCOM objects,
again you have a deal with reference counting GC and again circular
reference pattern is an issue.

<URL: https://developer.mozilla.org/en/Using_XPCOM_in_JavaScript_without_leaking
/>

If programmers understand the problem, they never use circular
reference pattern.

From: Ry Nohryb on 27 Jul 2010 03:38
On Jul 27, 8:04 am, Asen Bozhilov <asen.bozhi...(a)gmail.com> wrote:
>
> Please follow the posted link. As I wrote the problem is in the
> programmer, not in GC. (...)

The problem is in IE, only in IE.
And in Redmond, WA.
--
Jorge.
From: David Mark on 27 Jul 2010 03:44
On Jul 27, 3:38 am, Ry Nohryb <jo...(a)jorgechamorro.com> wrote:
> On Jul 27, 8:04 am, Asen Bozhilov <asen.bozhi...(a)gmail.com> wrote:
>
>
>
> > Please follow the posted link. As I wrote the problem is in the
> > programmer, not in GC. (...)
>
> The problem is in IE, only in IE.

The problem is in your head, Jorge. Somehow you think you don't have
to deal with the most-used browser. You have to accept the things you
cannot change.

> And in Redmond, WA.

Why don't you invade and attack their windmills? :)
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13
Prev: how to assign a id as a variable
Next: Initializing a global namespace object