Interesting thoughts. I'll leave it to the more technologically gifted to make the predictions and to explain the tech, but like you said, who can complain about a free glass of beer without ads?
Should Twitter go the way of ICQ, CompuServe (my first online community), or others, it will be interesting to see. In the meantime, my PDX "friends'" tweets have opened my eyes to a whole new world of OpenID, dataportability, and the real value of social/business networking.
@Gary: Looking over my geeky feeds, it looks like a few other failures can be attributed to Herr Jobs, Engadget, CrunchGear, FSJ, MacDailyNews, and more. I expect uncov to have some appropriate snarky comments by tomorrow.
It's funny (or sad, depending on your viewpoint) to note: 1) what the Interweb cares about most and 2) how woefully unprepared these sites are.
bex
· 1 year ago
Its indicative of how C-Ruby and Rails performs poorly, but not necessarily a reflection of Java-Ruby and Rails.
Most of the performance problems in Ruby/Rails (poorly written IO, poorly written thread management, poorly written garbage collector, poorly written memory management) can be mitigated by using what's built-in to Java.
The JRuby guys have a chance to re-do Ruby the right way... they're already getting better performance than optimized C-Ruby for number crunching, without even trying hard:
All Comments
Should Twitter go the way of ICQ, CompuServe (my first online community), or others, it will be interesting to see. In the meantime, my PDX "friends'" tweets have opened my eyes to a whole new world of OpenID, dataportability, and the real value of social/business networking.
http://twitter.com/gwalter
It's funny (or sad, depending on your viewpoint) to note: 1) what the Interweb cares about most and 2) how woefully unprepared these sites are.
Most of the performance problems in Ruby/Rails (poorly written IO, poorly written thread management, poorly written garbage collector, poorly written memory management) can be mitigated by using what's built-in to Java.
The JRuby guys have a chance to re-do Ruby the right way... they're already getting better performance than optimized C-Ruby for number crunching, without even trying hard:
http://headius.blogspot.com/2007/11/java-6-port...
I'll let him comment more in detail on the larger issue of Rails vs. JRuby.