Mikeal Rogers

It's true, we also experienced data loss (several millions of log data caused by dirty shutdown, it's data file is very fragile) issue like this thread http://groups.google.com/group/mongodb-user/browse_thread/thread/d0111a47984cb688

I found the following two posts very insightful：

1, http://www.mikealrogers.com/2010/07/mongodb-performance-durability/

"This (mongodb's write plolicy) is kind of like using UDP for data that you care about getting somewhere, it’s theoretically faster but the importance of making sure your data gets somewhere and is accessible is almost always more important."

2, http://www.paperplanes.de/2011/1/10/mongodb_and_data_durability.html

"It's okay to accept trade-offs with whatever database you choose to your own liking. However, in my opinion, the potential of losing all your data when you use kill -9 to stop it should not be one of them, nor should accepting that you always need a slave to achieve any level of durability. The problem is less with the fact that it's MongoDB's current way of doing persistence, it's with people implying that it's a seemingly good choice. I don't accept it as such."

Node.Philly - http://www.youtube.com/nodephilly

dominode - https://github.com/maxogden/dominode

browser-stream - https://github.com/dominictarr/browser-stream

cdir - https://github.com/hij1nx/cdir

crypto-browserify - https://github.com/dominictarr/crypto-browserify

Stream vs. Callback vs. EventEmitter - http://groups.google.com/group/nodejs/browse_thread/thread/7b677932c3cfb53a

node-disorder - https://github.com/substack/node-disorder

OAuth with Request vs Passport vs EveryAuth

Mikeal's TC39 Post - http://www.mikealrogers.com/posts/tc-thirty-what.html

npm-www - https://github.com/isaacs/npm-www

Node.js 0.8 Milestones

NodeConf - http://www.nodeconf.com/

TacoConf - http://tacoconf.com/

node-falafel - http://github.com/substack/node-falafel

LXJS - http://lxjs.org

Testling - http://testling.com

I think open source has changed a bit with the rise of the GitHub era. IMHO, I think @mikeal did a good post regarding this change "Apache considered harmful" http://www.mikealrogers.com/posts/apache-considered-harmful.html

Even in the old days, it's easier to fork than work with upstream. I think these days it's just easier share those forks with services like GitHub. It should help spread ideas and improved solutions IMHO so downstream consumers actually benefit.

In Twitter's case, they are planning to do what works for them at the moment: "While we initially focused on the challenging goal of making Memcached work extremely well within the Twitter infrastructure, we look forward to sharing our code and ideas with the Memcached community in the long term."

Here are the ones in my reader, admittedly I haven't visited often enough over the past couple of months:

http://www.igvita.com/

http://ejohn.org/

http://codingrelic.geekhold.com/ (Denny covers assembly and networking issues often in great detail)

http://buhrmi.tumblr.com/

http://elegantcode.com/

http://72lions.com/

http://kellabyte.com/ (mobile-ish dev)

http://lambda-the-ultimate.org/

http://ihumanable.com/blog

http://4loc.wordpress.com/

http://www.maxogden.com/

http://till.klampaeckel.de/blog/

http://www.quirkey.com/blog

http://www.mikealrogers.com/

http://cocoawithlove.com/