不明白。。。那為什麼不要 GBP 英鎊？除非你是生活在美國吧。

很正常，美國大學甚至全部都是 Mac .....

看過 1.9 / 2.0 / 2.1 NewRelic Pref Graphs, GC 其實已經很大進步，餘下來的就是 Ruby Execution Speed，仍然有很大進步空間。

有說他們買了 Sublime Text，Atom 是 Sublime Text 的 Online 版本

應該是有美女很有可能能改善「關係的和睦程度」，也就是改善工作環境。。。我是這麼理解的。。

男生們，是公司美女如雲真的很有吸引力？

天下那裡有貓不吃魚，窈窕淑女、君子好逑。吸引力是一定有的，不過會否加入公司；應該是另一個問題。

個人覺得 ( 不喜勿 X ) 美女在太多男性公司例如技術公司 / 或其他工作時間長的職業真的很麻煩，特別是很多男生同時間追同一個女生，超。嚴重影響工作表現，同事關係，等等。特別是年青美女問題更加嚴重。如果是已婚，成熟的美女 / 婦大多數的確能 "改善「關係的和睦程度」，也就是改善工作環境 "。不過也只限於特定條件。

說真的， Ruby 不算快，慢與不慢就個人觀點，不過肯定不是快。 而 Rails 真的很慢。。。。。 不過這個 Patch 要到 4.1 後才 Merge..........

http://www.erlang-factory.com/upload/presentations/558/efsf2012-whatsapp-scaling.pdf

不得不佩服 Erlang 在這領域上的優勢。OTP + Beam 在這短時間內上 3M Concurrent Connection / Server。不敢說 Java 不能，不過應該無有這麼容易。Ruby 嗎。。。 ( 自己也不肯定。。。。 )

不過 190 億美元中有好多是股份，而現時 FB P/E 是 111.....................

記得早前有個 HN Post 都說 Account 被盜用作 BitCoin 採礦。

@dorentus 問題是我應為正常的不等於其他人覺得正常的說法麻。在外國當然不會有這個情況出現。

@lgn21st 可以討論一下 Discourse 有什麼比較好嗎？技術上最大差別肯定是 Client Side ( Discourse ) Vs Server Side ( Ruby-China ) Rendering. 而且 Ruby China 明顯地比 Discourse 快。 純 User 角度看，我個人覺得 Ruby -China Forum 是我見過最好用的 Forum 之一，簡單，易用，易明，清析。我甚至不明白為什麼無有其他人使用。比較起國內的 Discuz，國外的 IBP，Vb，PhpBB 都更加好用。唯一可以比較的只有 Vanilla Forum。Ruby China 現在時最缺的是內建 Search。相信這個將來可以用 Elasticsearch ( 剛剛宣布 V1.0 ) 。

@chunlea

Q: If you're going all in on Basecamp, what happens to Campfire and Highrise?

In the short term, everything stays the same. Business as usual. No interruption in service, no changes that affect our customers.

In the long term, one of three things:

SCENARIO 1: We'll spin them off into separate companies where we'll retain partial ownership, but another fully-dedicated team will run the products and own the majority of the company. This would be our ideal situation as it would ensure continuity and no interruption for our customers, but we'd have to find the right entrepreneur/team with the right experience and enough financing to make it work.

SCENARIO 2: We'll sell the products outright (either separately or together). The key for us in this scenario is that the products, and our customers, are well looked after. We will not sell either of these products to a company that is planning to shut the products down. And since no one from our team goes with the sale, this is not an acqui-hire situation. We're looking to sell to a company that wants to add well-respected, well-established, profitable, growing products to their portfolio.

SCENARIO 3: If we can't find the right partner or buyer, we are committed to continuing to run the products for our existing customers forever. We won't sell the products to new customers, but existing customers can continue to use the products just as they always have. The products will shift into maintenance mode which means there will be no new development, only security updates or minor bug fixes. We did this successfully in 2012 with Ta-da List, Writeboard, and Backpack, so we know how to make it work.

If you're a company or team interested in exploring scenario 1 (spin-off) or scenario 2 (outright purchase), please get in touch. Based on current revenues, current growth rates, and a conservative multiple, Campfire will sell in the single digit millions, and Highrise will sell in the tens of millions, so serious inquires only please. Disclosure: We're currently in early discussions with a few interested parties.

太好了原來可以單買。！！

@zeeler In memory Database，是 Redis 還是 Memcached?

可以看看 @flyerhzm 黃智敏 這個
https://speakerdeck.com/flyerhzm/gou-jian-yi-bu-apifu-wu

他也在 Homepage http://huangzhimin.com/ 上寫到 I have built a large high-traffic platform, with more than 250 million users, handle more than 300k rpm. I also built some async non-blocking api services, based on EM + fiber, only 16 ruby instances can easily handle 240k rpm.

為什麼 funny-falcon patch 永遠無法 Commit to Mainline / Trunk?

#2 楼 @googya 限制為 pg 沒什麼不好吧，反正想不到不用 PG 而用 MySQL 的原因。

對不起，引起這誤會 @@"，下次會用回 'released'.

#22 楼 @jarorwar 最近 groupon 都轉到 NodeJs 了， https://engineering.groupon.com/2013/node-js/geekon-i-tier/ 雖然 @luikore 大說還有下文。。。。

GitHub 中國遊記之 CSDN——Git+Code=Gold

CSDN：能談談 scaling 的問題麼？

Zach：最開始只有 github.com 的時候，好多人都說，你們用的是 Ruby on Rails，吞吐量的問題怎麼解決？我當時真想說，Ruby on Rails 不是導致速度受限的問題，數據到磁盤的讀寫速度才是硬傷。現在我們更新了一大批服務器，速度很快。

http://www.csdn.net/article/2013-12-23/2817890-GitHub-journal-in-China-Part2/1

Update: This repo is obsolete. The main point of event based IO is less memory for concurrent connections, and pay less time in CPU context switching, thus leading to higher performance benchmarks. But in real the heavy computation remains in ORMs like active record, the saved CPU time is insignificant while the implementation requires complex tweaks.

@luikore 可以再詳細解釋下嗎？

1. 以 Ruby Communities 來說，這個 Site 不論 Design / Fonts / Colour 都可以說很差，不及格。
2. 有 Rbx 嗎？還是說我瞎了眼 @@

這個問題我想問很夠了，什麼原因選擇 MongoDB

@luikore 還沒出現嗎 @@" 不過 nyara 最近也沒有 update......

不過簡單測試，Raw JRuby，TorqBox 也有近 87% Top Speed。相信未來這個組合不難達 90% 或以上。但加上 Rails 就只有 2.5%。証明 Full Framework 和 No Framework 差別有多大。

發生什麼事？

Atmail

5 號 = Old www.scala-lang.org/ ........... ><"

為什麼總是使用 MRI，PUMA 不是最好使用 Rubinius ?

Waiting to see some Input and reaction from @luikore

Update with Benchmarks.