amadeus

10 ms·

61.
by amadeus 15y ago
He's sitting right across the table from me :)
62.
by amadeus 15y ago
Sarcasm is lost on this one :)
63.
by amadeus 15y ago
It's only messy if you don't understand it. Just because a concept is difficult to grasp initially, doesn't mean it's messy. Using this properly can prove to be a very powerful and flexible tool in your JS skill set. Ultimately I think it f
64.
by amadeus 16y ago
Brian did it all himself. While I do not know the wealth of his parents, they have played almost no role in Kiip, other than being his cheerleaders. I have only met his father once, as his parents still live up in Canada. I know this becaus
65.
by amadeus 16y ago
Since I'll probably be using this for a couple smaller things of mine, I forked it and went ahead and changed it to: subscribe/unsubscribe/publish and also added return this. https://github.com/amadeus/microevent.js
66.
by amadeus 16y ago
When deploying to live, you should compress all JS and aggregate into a single file.
67.
by amadeus 16y ago
I really like the code, I think it's very well written! A couple small suggestions and thoughts: Add a couple lines so that all methods return this; to allow for chaining, especially helpful when using it as a mixin. Rename bind/unbind meth
68.
by amadeus 16y ago
You're actually further proving my point. I said that if you are writing an external library, it's a good practice NOT to extend prototypes since the context the plugin will be used in is entirely unknown. The argument that you are giving f
69.
by amadeus 16y ago
I have to plug my console wrapper which takes care of problems like these :) https://github.com/amadeus/dbg
70.
by amadeus 16y ago
Again, it's not 'bad for you'. You don't NOT use a hammer because it doesn't work well with screws. It works great on nails, so again, context is everything. Supplying best practices that include the words 'always' or 'never', often fall qu
71.
by amadeus 16y ago
Actually, that's still the point though. If you are building a library to be used in a variety of contexts, with no prior knowledge of the environment, it's probably not a good idea to extend native prototypes. If however, you are building
72.
by amadeus 16y ago
Well that's why the statement is controversial. This person flat out says, NEVER extend native prototypes except for 1 single case. Sorry, but blanket statements like that are complete B.S. It all depends on context; it makes me dubious of
73.
by amadeus 16y ago
You can see your results on their own page by appending /show to a saved fiddle, see: http://jsfiddle.net/amadeus/5y5nE/show/ Also, it's recommended to use jsFiddle over Mootools Shell, since MooShell is essentially a really old version o
74.
by amadeus 16y ago
Awesome! Yeah this reminds me of a little experiment I did back in the day that was similar, but not using the logo of course: http://fun.amadeusamade.us/iphone/ (Warning, my deceleration method is gehetto, so please forgive, I coded it i
75.
by amadeus 16y ago
I improved this with a couple lines of CSS to add 3d support. http://fun.amadeusamade.us/improvedSpinner/
76.
by amadeus 16y ago
Another really great tool is http://jsfiddle.net It allows you to mock up quick examples/bugs/etc.