I realize that YouTube is a crazy hard problem to tackle, and that is probably why stuff like this is necessary.
38 karma · joined November 20, 2012
I realize that YouTube is a crazy hard problem to tackle, and that is probably why stuff like this is necessary.
Now, when i drive i look further down the road, i plan out how to follow the road, i see the intersection coming up, and try to anticipate the routes of the other cars/bikes and that requires far less energy, than only processing the immediate surroundings.
please open presentation X from my dropboxThe implementation is not at all as neat as the original, and i haven't done thorough testing, i just had an idea and tried it out.
"click:#elem1 click:#elem2 keyup:13"
That would enable you to make slightly more advanced easter eggs or "cheets"
The only thing I dislike about TS is the way it handles dependencies. The require/declare/import/export methodology confuses me. And on top of that there is the //<reference /> tag, and all of it seems to be relying on files, rather than on constructs in the code. Relying on files, means that I have to maintain the order of which to import what, and this becomes even harder if some of the files contain code that is not just module/class definitions, but actual statements in global scope.
2. There seems to be some SQL stuff in there - IO would be a nice addition though.
3. This could be a problem. Let us host the app our self, and we might be able to handle it?
With that in mind, i would love to have this as a part of my daily toolset.