If you’ve got a great idea for the next big web framework, the first thing you should do is not write a douche-y blog post bashing other web frameworks. Here’s some ideas for things you could do instead:
- You could make a website promoting the advantages of your framework over other existing frameworks.
- You could improve the framework itself.
- You could document the framework so that others can easily begin using it.
The point is by attacking others, you don’t accomplish anything other than branding yourself as a grade A asshole. It’s fine if programming in C and doing all that memory allocation, dealing with pointers, and calling functions validates your skill as a programmer. I happen to like Ruby because I don’t have to do those things. What’s great is that we can co-exist. You can have your fast framework written in C and serve thousands of pages a second. I’ll stick to my ’slow’ framework written in Ruby. Chances are the people visiting the sites will never know the difference anyway.
Drop the ego. Realize that there can be more than one approach to solving a problem and yours isn’t always going to be the best one.
I agree that that blog post is total asshattery. Though I also have to note the irony that this site apparently died under the redditing yesterday, so I couldn’t read it until today. Sometimes the users of the site _will_ know the difference
Chris is just pissed because he’s being paid 1/4 what a Rails dev gets. I’m sure he’s right, and the market is just confused. Has anyone seen my Fortran book?
He has a weak argument. “C is faster than ruby”. No shit. How much and is it enough to care? Assembly is faster than C, if he wants performance write it in assembly.
For some reason I find it comical that his blog is running on Wordpress.