Via InfoQ.

* Symbol#to_proc本是rails的甜头。一个框架居然反过来影响了它所用的语言，甚是好玩
* 突然发现curry和linus鼓吹的DVCS颇有几分神似阿，汗

Watch the video here. You'll find a good summary here.

Git vs SVN/CVS/etc. is not only a comparison on tool, it's a comparison on development model/philosophy.

Sometimes you have some fixutres want to load them into some db by hand, maybe as useful data. You can do this by rails console:

$ script/console
>> table = YAML.load_file("#{table_name}.yml")
>> ActiveRecord::Base.transaction do
>> table.each do |fixture_name, fixture|
>> ActiveRecord::Base.connection.execute "INSERT INTO #{table_name} (#{fixture.keys.join(",")}) VALUES (#{fixture.values.collect {|value|  ActiveRecord::Base.connection.quote(value) }.join(",")})", "Fixture Insert"
>> end
>> end

via

1. Although you don't have to take my word for it, eventually you're going to have to accept the truth. Thread#kill, Thread#raise, timeout.rb, net/protocol.rb all suffer from these problems. net/protocol.rb could be fixed to use nonblocking IO (select), as could I suspect most of the other libraries, but there is no safe way to use Thread#kill or Thread#raise. Let me repeat that: there is no safe way to use Thread#kill or Thread#raise.
2. Start lobbying the various Ruby implementations to eliminate Thread#kill and Thread#raise (and while you're at it, eliminate Thread#critical= as well, since it's probably the single largest thing preventing Ruby from being both concurrently-threaded and high-performance).
3. Start lobbying the library and application maintainers using Thread#kill, Thread#raise, and timeout.rb to stop.
4. Stop using them yourself.

• If you want to be able to kill a thread, write its code such that it periodically checks whether it should terminate. That allows the thread to safely clean up resources and prepare to "die itself".
• If you need to time out an operation, you're going to have to find a different way to do it. With IO, it's pretty easy. Just look up IO#select and learn to love it. With arbitrary code and libraries, you may be able successfully lobby the authors to add timeout options, or you may be able to hook into them yourself. If you can't do either of those...we'll, you're SOL. Welcome to threads. I hope others will post suggestions in the comments.
• If you think you can ignore this, think again. Eventually you're going to get bitten in the ass, be it from a long-running transaction that gets corrupted due to a timeout error or a filesystem operation that wipes out some critical file. You're not going to escape this one, so we should start trying to fix it now.

不知道还有木有人记得我以前介绍过的蒸汽达人，今天又来一位差不多的，他的爱好是制作机械昆虫。不同的地方是他比较喜欢太阳能驱动，而不是蒸汽驱动 － 还是蒸汽驱动更帅，我觉得。

 

原以为是个js database layer，结果是和prototype一个类型的东西。。。还真好用。jQuery真应该换个名字，光名字就阻止了多少潜在用户阿，都去用prototype了。

http://learning.palm.com

Palm真是不务正业，产品被blackberry/iphone打得节节败退还有心思花那么大力气给老掉牙的产品做这么华丽一帮助网站。。。sigh

实在无法继续忍受bloglines beta那种简直能让firefox发出吱吱嘎嘎声音的超重量级界面了。几乎同样的功能，google reader却能显得轻量级许多。不知道这是不是google赞助firefox挖到firefox头号开发者的直接好处? 总之直接后果是，一名有着三年光辉历史的bloglines忠实用户如今叛变进入google reader阵营了。

我心不甘阿。