Profile_bird

Hey there! dewitt 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 dewitt's tweets.

Already using Twitter
from your phone? Click here.

dewitt

  1. Congrats to Palm for launching Project Ares - a web-based IDE for the mobile web: http://j.mp/4n2Fuy and http://j.mp/7PTALo
  2. Don't worry. Save some time. Your story doesn't need a shred of truth to it. It will be retweeted just the same.
  3. I suppose my dream of getting a Lala app on my Android phone is out of the question now, huh?
  4. AT&T is still sending Yellow Pages to every home in San Francisco. Have you used a paper Yellow Pages in the past five years?
  5. This post on using HTML5 to make Gmail blazingly fast and feature rich on mobile devices makes me insanely happy: http://j.mp/86xcvy
  6. When I used your website once two years ago, at no point did I want you to send me "Happy Holidays" emails. Geez.
  7. You keep using that word. I do not think it means what you think it means.
  8. Incredible momentum for OpenID in 2009: http://bit.ly/6zMPWh
  9. @Carnage4Life Try 'curl -v http://fb.me/3BhhNXU'. Looks like the 302 redirect is public. It's the final location that's protected.
  10. Welcoming Google Fusion Tables to our growing family of developer APIs: http://j.mp/4n85ZC
  11. Rich Hickey and Clojure are raising funds to sustain open source development. I donated. Thank you, Rich! http://j.mp/4MJHsJ
  12. Glass houses and all, but seriously? How could this get past a launch review? http://j.mp/7wwQ16
  13. Amazon moves the needle yet again: Auction market pricing for as-available EC2 compute resources: http://j.mp/90TUD7
  14. 2009 has been a good year for languages. Clojure 1.0, Go, C# 4.0 beta, Python 3.0 (and Unladen Swallow).
  15. @timbray Agreed that the danger is in trolls, but the good guys need to set the bar. And even good guys can go bad... We could go on and on.
  16. @timbray "Just CC license the API docs" was what we were trying to improve on. Copyright was never the issue. Trademarks and patents are.
  17. @timbray I strongly disagree that nothing does. For one, the OWFa does (bit.ly/5u7TXx), which replaces dozens of one-offs that also do.
  18. @crazybob Right. Though we eventually concluded that the Apache license wasn't best applicable to specs, hence the OWFa: http://j.mp/5u7TXx
  19. @Carnage4Life I'd turn that around a bit. It was the web that mattered most, regardless of how you get to it. Mobile is just another way.
  20. You *can* copyright an API's docs. And trademark its vocabulary. And hold patents that read on implementations. That's why we have licenses.