Profile_bird

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

Already using Twitter
from your phone? Click here.

headius

  1. @feyeleanor Mmmm, not bad...I bet that had at least something to do with it.
  2. @RichardConroy I think it's hard to ignore the amount of effort MRI or others would need to have to catch up with JVM, though.
  3. If mobiles are the computing platform of the future, then Darwin vs Linux is shaping up to be the next big OS war.
  4. @feyeleanor I'm just lucky that what I'm interested in doing happens to intersect with a giant money-rich world.
  5. @feyeleanor I think I hear it already :)
  6. Found an old (Oct 2003) LiveJournal post from me that's oddly prescient: http://is.gd/52N94
  7. @RichardConroy I appreciate that, but it's not just ruby-core...it's *everyone* caring little about those users. I hear it all the time.
  8. @feyeleanor When those masses absolutely dwarf the existing Ruby community, it seems like a good thing to do :)
  9. @mohdabdurraafay Left to right it's me, @olabini, @nicksieger, and @tom_enebo.
  10. RT @cmercier: Looking for the right person to take over isitjruby.com. Email if interested. #jruby @jruby
  11. @jrubyist I have not...blogged about it somewhere?
  12. @bphogan In JRuby 1.4 we put in a *lot* of extra effort to make sure JRuby works really well on Windows. We will continue to do so.
  13. @philswenson In general, good benchmarks of the JVM must do some real work to ensure hotspot doesn't optimize things completely away.
  14. RT @madwombat: JRubyConf was fantastic! ...thanks to @headius, @nicksieger, @olabini, and @tom_enebo for being both accessible and awesome.
  15. @jaymcgavren I'm sure we can use your help; both Tom and I suggested that to each other.
  16. @jrubyist Interesting...looking forward to your post on ThreadPoolExecutor.
  17. @monkchips If there's a JVM for it, we'll try to run on it. Maybe we need a fork of Hotspot called HotTomato?
  18. @jrubyist If you haven't reported a bug, do that first. Could be a few things, but we'd have to see the error/trace to know.
  19. @haruki_zaemon I intend to keep moving it forward, definitely. It's a tool I want for my own use, and others seem interested now too.
  20. @locn I'm not sure, but they're usually pretty fast. I will tweet, as will other JRubyists I'm sure.