Top 10 Reasons Why Ruby Sucks Ass
a counterpoint to the previous post
Possibly Related Posts
- Rocky Mountain, Hi
- Location, location, location. It’s all about location..
- It’s Happens to Everyone Eventually
- Geeky Distractions
- Time for Questions
What We’re Reading
- Jason Calacanis vs. David Heinemeier Hansson on This Week in Startups
- Set Up Your Own Google-Style 20-Percent Time to Try New Projects [Motivation]
- The Million Follower Fallacy: Audience Size Doesn't Prove Influence on Twitter
- EventMachine: Get Excited By Scalable Non-Blocking I/O
- LoKast : The Disposable Social Network
- The Current State of Twitter [INFOGRAPHIC]
- Socket.IO - multi-transport socket server for Node.js
- RequireJS: Asynchronous JavaScript loading
- When can I use...
- Distributed Version Control is here to stay, baby
- Users Rejecting Security Advice Considered Rational
- Crowdsourcing in the Enterprise With Gambling In Mind
- Creativity Alone is Not Enough
- OpenSocial 1.0 spec published
- OpenSocial 1.0 spec published
- Now A No-Evil Zone
- Adequately Good - JavaScript Module Pattern: In-Depth
- Using CoffeeScript in Rails and even on Heroku
- A deep dive and analysis of the JavaScript Module pattern
- louisgray.com: ActivityStreams Aim to Be DNA of the Future Web