Profile_bird

Hey there! SubtleGradient is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What's happening? Join today to start receiving SubtleGradient's tweets.

Already using Twitter
from your phone? Click here.

SubtleGradient

  1. @samleb you're working on a js css selector engine? I'd love to collaborate on specs. 9:15 PM Dec 15th from Tweetie in reply to samleb
  2. RT @mojombo: Introducing Semantic Versioning - A technique to avoid "dependency hell" - http://semver.org/ 11:58 AM Dec 15th from API
  3. @Bluebie MooTools doesn't duplicate JavaScript native inheritance. It uses it. Just adds some extra sugar to make it easy and standardized 6:17 AM Dec 15th from Tweetie in reply to Bluebie
  4. @i386 @ycros I think jQueryUI hard-codes classnames so that themeroller themes will all work. But yeah, I prefer much more extendability. 6:09 AM Dec 15th from Tweetie in reply to i386
  5. which one you think is the best tool to create JavaScript documentation? /via @WebReflection TextMate or Espresso.app ;) 4:28 AM Dec 15th from Tweetie
  6. @wycats I'm working on rubygems for JavaScript. Partially based on your TextMate gem I submitted a few patches for. Should be awesome. 10:41 PM Dec 14th from Tweetie in reply to wycats
  7. RT @cheeaun: MooTools featured on GitHub Rebase #32 http://github.com/blog/566-github-rebase-32 #mootools 10:33 PM Dec 14th from API
  8. @Ycros ahh I see. I like both approaches. Inheritance and mixins! MyThing implements Events & Options 9:41 PM Dec 14th from Tweetie in reply to Ycros
  9. @Ycros @i386 inheritance keeps you from having to hack the source to extend. Simply override the bits you need without having to fork code 9:37 PM Dec 14th from Tweetie in reply to Ycros
  10. … better to prefer composition over inheritance. /via @Ycros Do you have examples that show how "composition" is preferable? 9:35 PM Dec 14th from Tweetie
  11. … preferring one abstraction over another is the same as hating abstraction. /via @wycats I'm afraid I don't follow you. Care to explain? 9:29 PM Dec 14th from Tweetie
  12. Inheritance is very powerful. Create very clean and focused code. If you need an extra feature in only a few places, subclass and extend it 9:26 PM Dec 14th from Tweetie
  13. @wycats do you need inheritance in Ruby? Wouldn't Rails totally blow without it? How would you ever extend anything? Hack the source? 9:12 PM Dec 14th from Tweetie in reply to wycats
  14. @wycats I don't need helpers, I like them. They help enforce patterns. Patterns help you code quickly, share and extend. No constant redos 9:07 PM Dec 14th from Tweetie in reply to wycats
  15. if you need helpers on the web you're overusing it. You don't need inheritance. /via @wycats You don't need Ruby. Just code in C. 9:00 PM Dec 14th from Tweetie
  16. @wycats worse how? worse than what? I use helpers to make prototype inheritance coding faster. I've never seen anyone do it well manually 8:47 PM Dec 14th from Tweetie in reply to wycats
  17. protip: Working weekends does not send you back in time. 12:00 PM Dec 14th from Tweetie
  18. http://macrabbit.com/espresso/whatsnew/ New MacRabbit Espresso.app 1.1 just released! The project-wide search UI totally rocks my socks. 7:30 AM Dec 14th from Tweetie
  19. Inbx zero is a great idea. RSS, Twitter & mailing lists zero is a very bad idea. 3:21 AM Dec 14th from Tweetie
  20. @tolmasky the MooTools team has just begun using code tagging for embedded compat and engine-specific fixes, etc… http://j.mp/8xdS0W 3:10 AM Dec 14th from Tweetie in reply to tolmasky