Re:Writing Rails code makes me miss writing in Objective-C. ...
by saurik on Wednesday July 14, 2010 @09:21PM
(#1516564)
Tests don't make code work. The problem I've experienced with the Ruby commumity is a constant belief in "this can't be that hard, I'll just throw one together". One day I traced a major bug in a client's app to their Ruby webserver not handling HTTP 100 Continue correctly... that simply should not happen. Pulling apart the server I found that most of the behavior was hardcoded for common clients, and certainly no one had bothered to read the HTTP spec. That wasn't an isolated problem, either, but I feel like I need not go into every single library bug I've run into. I simply did not get that feeling from the large number of Java libraries I used to use, many of which were actually the official reference implementation for the specification. ;( Bugs, yes; completely misunderstanding the problem domain and thereby not really being worth using, no.
[ Parent
| on HN ]
Re:Writing Rails code makes me miss writing in Objective-C. ...
by a4agarwal on Wednesday July 14, 2010 @09:33PM
(#1516591)
Thank you, I agree 100% and this is basically the gist of my post.
That's why there is so much fragmentation in ruby gems. When one gem fails to do something, a developer thinks, "well I can just do this myself and do it better!"
And do you end up with 10 gems that all do roughly the same thing, but not perfectly, each designed by and for a different person.
Re:Writing Rails code makes me miss writing in Objective-C. ...
by mattmcknight on Wednesday July 14, 2010 @11:32PM
(#1516863)
I know the fans will vote me down for saying this, but Github has greatly increased the level of fragmentation. With the exception of the core projects, people seem to fork more than they join forces to build a better gem.
It's a very easy problem to solve though- build fewer dependencies on thinly supported libraries. That applies to all languages.