6 ms·
Could do with some smoothing and polishing. Jerks all over the place. Also, what is with this new fashion of declaring functions as anonymous methods? var
by mattmanser 14y ago
Could do with some smoothing and polishing. Jerks all over the place.
Also, what is with this new fashion of declaring functions as anonymous methods?
var recalculateLimits = function () {
/* snip */
};
var update = function () { recalculateLimits(); onScroll(); };
Have I missed a memo?
EDIT: I forgot to say apart from my moaning, does the job, good code, good job! And it's only jerky when you use the scroll button on a mouse.
- prezjordan 14y agoThis [0] is the only difference I am aware of. But I would love to hear someone talk about performance differences (if any). [0]: http://stackoverflow.com/a/336868/712889 http://stackoverflow.com/a/336868/712889
- mattmanser 14y agoI actually got in an argument with someone on SO the other day who swore blind that the only was to declare a 'class' was using this pattern. Took a fiddle to shut him up. I just don't get what it adds to your code apart from hiding simple function definitions in the visual trappings of a static helper object or closure. Javascript is already homogeneous enough without making it visually even more.
- jonahx 14y ago>> I just don't get what it adds to your code apart from hiding simple function definitions in the visual trappings of a static helper object or closure. Javascript is already homogeneous enough without making it visually even more. What method do you use instead of the following, when creating namespaces? var yourNamespace = { foo: function() { }, bar: function() { } };
- piva00 14y agoWait, I don't think that JavaScript is homogeneous, not in the least, for me it's really heterogeneous, I can look at 3 or 4 scripts developed by people of different skills and backgrounds and see it done in 3 or 4 completely different styles, visually and syntactically. Did you messed up the wording over homogeneity?
- mattmanser 14y agoI mean the syntax is homogeneous, I agree the styles in use today certainly aren't!
- jonahx 14y agoThe one I mentioned above, you cannot conditionally create functions using function declarations.
- hkuo 14y agoI learned this method with the book JavaScript the Good Parts, though it was a while ago and I can't remember the specific reasoning behind the books' recommendation. From the other commenter's SO link, I found this link to go more in depth into the differences of declaring functions, and it seems to come down to having stricter control on the order of events with no surprises. http://javascriptweblog.wordpress.com/2010/07/06/function-declarations-vs-function-expressions/ http://javascriptweblog.wordpress.com/2010/07/06/function-de... And here's an example of one of the surprises you'll run into if you don't declare your functions in this way: http://www.adequatelygood.com/JavaScript-Scoping-and-Hoisting.html http://www.adequatelygood.com/JavaScript-Scoping-and-Hoistin...
- gjulianm 14y agoI'm not a JS programmer, but I'd say that always using the function expressions (var a = function() {}) is bad. I understand that it's more useful when you intend to manage it as an object, or as part of a bigger object (the additional reasons your first link gives). But about the hoisting problems... For me, the real problem is that you're declaring a function inside a function. Or using variables with the same name. That's a bad practice, it doesn't make sense. It should be avoided instead of using language constructs to work around it.
- mattmanser 14y agoThat's definitely not in javascript the good parts. It's a new thing and its spreading like some sort of horrible virus. It has quite the opposite effect that you're prescribing to it. Your second link describes both variable hoisting, a real problem which causes serious problems, and function hoisting that has never been a problem as almost every other modern language behaves that way. You don't seem to be a polyglot or you'd understand the problem immediately. Variable hoisting is just downright bizarre if you've worked in almost any other language, whereas function declarations can be anywhere in most languages and so when they are declared is almost completely irrelevant to a programmer. Artificially assigning them to a variable so that suddenly function declaration order does matter is just downright weird. The 'normal' function declaration is better and clearer.
- 14y ago
- fabriceleal 14y agoFrom the discussion in one of the replies: Named function expressions demystified http://kangax.github.com/nfe/ http://kangax.github.com/nfe/
- mattmanser 14y agoThat's actually discussing totally different concepts with a couple of side mentions (the only related bit being in Function names in debuggers). But at no point do the use this technique for declaring functions any where else. Interestingly in that article they don't even entertain the possibility that someone would ever declare a javascript function that way. A mere 3 years ago.