Comments for I does Javascript!

Comment on IE quirk with onload event for elements by Samuel

Samuel — Mon, 20 May 2013 14:00:11 +0000

I got this problem this week also with IE 10. The event was fired _sometimes_. Like with random probability. Did not know a solution for that yet. Thanks a lot for sharing this!

Comment on Logical AND (&&) and Logical OR (||) in Javascript by Graham

Graham — Fri, 19 Apr 2013 12:08:57 +0000

Thanks for this explanation. I came across this use of the || operator in some code and couldn't work out what was going on. This article really helped.

Comment on IE quirk with onload event for elements by Soupatowtow

Soupatowtow — Mon, 15 Apr 2013 13:19:15 +0000

Thanks a lot !

Comment on True private variables in Javascript with prototype by sstchur

sstchur — Tue, 09 Apr 2013 17:20:10 +0000

Igor, I honestly don't have much to offer you, unfortunately. I wasn't attempting to solve any sort of inheritance problems. In fact, I wasn't really attempting to solve any "real" problem with this post. It was more of an "information only" type post. I even say, directly in it, that I don't really recommend it. It was more a proof of concept — is it even possible to use prototype and still have truly private variables. That's what I was attempting to demonstrate.

The truth though, is that I've never used this, and honestly don't think I ever would. I think it's kind of a bad idea in a real-world scenario in a number of way. But I DO think it was interesting to talk/blog about.

Comment on True private variables in Javascript with prototype by Mahn

Mahn — Wed, 03 Apr 2013 01:36:37 +0000

This method redefines the prototype of the object with every instantiation, even though the prototype itself never changes, which makes it a bad idea in several fronts. Don't use unless you are absolutely positive you know what you are doing and the implications it has.

Comment on IE Bug dealing with CSS custom cusors by Radu

Radu — Sat, 16 Mar 2013 11:09:58 +0000

the next step would be to also cover having custom cursor hotspot which also requires a workaround for compatibility. I am sure the result of combining the workarounds together will be some disgusting css, all thanks to IE

Comment on IE quirk with onload event for elements by Rat

Rat — Fri, 08 Mar 2013 07:17:03 +0000

Thanks, you saved

Comment on IE quirk with onload event for elements by Sergey Tselovalnikov

Sergey Tselovalnikov — Mon, 04 Mar 2013 07:28:08 +0000

Thanks, it is very helpful for me!

Comment on Avoiding recursion in Javascript by Everson Siqueira

Everson Siqueira — Sat, 02 Mar 2013 10:14:44 +0000

Andreas, it is more than an year since your suggestion for a tail recursion call… Actually this is still not available to JavaScript. Each time you call a function in JavaScript you are piling a stack execution context for that invocation. This is being frequently discussed and, at some point, recursive tail optimization will be implemented – but for now iteration is faster (and uses much less memory) than recursion.

Comment on True private variables in Javascript with prototype by Igor

Igor — Wed, 20 Feb 2013 20:13:14 +0000

Hi sstchur,

Great blog. I'm currently looking for a good default pattern when working with javascript objects, privacy and inheritance. Like in the pattern book by Stefanov, you show that even prototypes can be defined inside closures to allow access on private variables.
Where i now stumble upon (and maybe also your solution) is the following problem: If you want to use inheritance and your Cat constructor were the supertype, then you would have a subtype like e.g. FeralCat. This would look like:

var cat1 = new Cat('Garfield', 7);
FeralCat.prototype = cat1;

After the assignment, FeralCat.prototype cannot further be extended using the same smart way with closures. All of the subtype protoype members will have to be public.

Maybe your blog does not claim to solve inheritance issues, maybe i miss a point. Anyway, what do you think?