Profile_bird

Hey there! jschementi 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 are you doing? Join today to start receiving jschementi's tweets.

Already using Twitter
from your phone? Click here.

jschementi

  1. Ah IronPython in my hometown: RT @voidspace: IronPython training in New York in January: http://twurl.nl/ifqp48 #python
  2. Clippy invades VIM http://bit.ly/2c31in
  3. @NathanStults I've used IronRuby to open the file and remove the BOM ... I'll post it to the IronRuby website eventually.
  4. @binaryape Let me know if you have any IronRuby questions
  5. @suhinini Need any proof-readers?
  6. @SoftMind Yep, that is on the list. After 1.0 I'll have plenty of time to document certain fxs working with IronRuby like Azure
  7. @ntmisa @ch9live When the IronRuby/IronPython tooling is built, it'll separate from VS2010, since we're open-source and want to keep agile.
  8. @ntmisa @ch9live We actually have no VS integration today, though IronRuby and IronPython work in .NET 4.0.
  9. @NathanStults :) good man.
  10. @panesofglass But it's not just about templates; we need a custom project system, colorization, and repl integration for it to be useful.
  11. @panesofglass Which in almost all cases would be an empty file =P
  12. @panesofglass Yep, that's what we're talking about. Point is to make that work VS would want to ship WITH IronRuby and IronPython.
  13. @NathanStults Did you see my latest tweet?
  14. @softmind As the integration gets more mature, then would be a good time to consider shipping in VS, with a easy way to upgrade.
  15. @softmind Which was the plan the whole time; it's more important to keep IronRuby and IronPython agile and open-source.
  16. @softmind IronRuby and IronPython VS2010 integration will be an seperate download. To be *in* VS2010, it had to get it more than a year ago
  17. Woohoo, now I'm giving the "Python in the Browser" talk at #PyCon2010 http://bit.ly/4jd1zl #ironpython
  18. @nightshade427 Not yet =)
  19. @voidspace Yes, @DevHawk is a difficult person to replace. I'll be doing all the public-facing #ironpython things.
  20. @kradcliffe awesome. but crap, I haven't given them links to my demos =P ... I'll get on that