Ruby on Rails and your single-origin latte is calling. C is the most performant for years now, a large part of the kernel is in assembly. Remember to download your gems tonight, rude boy.
I see, makes sense - it is easy to multiply big nums together but insane to factor the bignums out of them. You explained it more succinctly than I've ever understood it, thanks a ton!
Couldn't a cross-comparison be used, encrypting different known blocks and observing certain key properties? I would imagine that any kind of reversible operation would be able to be deduced if it can be applied to specific data that reveals its true form/operation.
This pattern is egregious and shows a lack of knowledge of the architecture and language.
All these private methods are going to be duplicated for every object created. The whole point of the 'this' magic in javascript is to allow the same function, ie. the same memory usage, to be used with 1000s of objects with no hit. Here, you're going to get unique functions, extra memory, for just having the 'this' operator substituted by a variable named _elem. This code is fundamentally flawed and I severely suggest to never use closures for shared object methods when instead a shared method that is bound using '.bind' will ensure much better performance and memory usage.
Yes, render,reflow,timeouts,event handling, etc happens..
You might need to set a CSS property and then animate it. In this case you'll need to wait for a render in between the two steps
Also useful if you need to wait until after all event handlers are executed in the current context
CoffeeScript is a debauchery of JS. With ECMAScript 6 you won't need CoffeeScript for anything except maybe it's inline printf-like string substitution.
This article is great because it doesn't argue for piracy or against it. I do feel that it is missing a discussion about the colour of bits being amalgated by other bits. IE, if I buy a movie and then I torrent that same movie, is the torrented copy still illegal? Cloudy at best, I'd say.