3 ms·
To me the biggest annoyance about the Ruby community is the belief that they invented everything and know how to do everything right if others would just listen
by btilly 14y ago
To me the biggest annoyance about the Ruby community is the belief that they invented everything and know how to do everything right if others would just listen.
And then, through unfamiliarity with what others learned a long time ago, they do it wrong.
As a random example, unit testing has been the standard for perl (note capitalization - I'm referring to the interpreter here) since it was released in the mid-80s, and for the Perl community since CPAN was created in the mid-90s. And when I say standard I don't mean that someone writes tests, runs it, then packages. I mean that - by default - nothing gets installed anywhere until it has passed its full test suite. Furthermore if I release a module to CPAN, I'll get automated emails about every OS and version of Perl that it didn't work on.
Core ruby still does not have good unit tests, and you have to go out of your way to run unit tests for gems. If you do that, you will find that a good portion were only set up for the author to run - they didn't think anyone else would ever do that.
And yet I've had Ruby devs with a straight face trying to tell me that Ruby is awesome for its testing culture, and everyone else has a lot to learn from them.
They are missing a lot, and don't realize it.
- hilko 14y agoCould it be that Rails (and by extension Ruby) is the first really popular post-web-revolution language used for development since PHP, and, unburdened by lots of bad practices having evolved alongside (not necessarily because of) PHP, re-introduces a whole bunch of good practices like unit testing? And could it be that as a result young, excited and still green developers, comparing themselves to the 'bad' previous web generation, get a bit cocky about it? These are not rhetorical questions; I'm actually asking this. I came from humble hack-together-crazy-bad-php-apps, went through getting used to more frameworky stuff with Drupal, and then ended up at Rails with a certain comfort and a definite increase in best-practice. My first introduction to unit testing was through Hartl's tutorials, perhaps because I have no formal programming background. I could see how some people after a similar process get cocky about how great they are because they write tests. I'm not defending cockiness or whatever characterizes the Ruby community. I'm just wondering.
- btilly 14y agoPeople who come to a better environment from a worse one often do get "true religion", and I am sure that happened to a lot of Ruby devs. You cite PHP. I would also cite Java devs whose first dynamic language was Ruby, and then went overboard. Either way, enthusiasm combined with lack of perspective leads to annoyance for people who have that perspective, who realize that you're still missing some basic lessons. (Monkeypatching anyone?)
- hilko 14y agoAh, great observation. That really does explain it. It's not unlike the zeal of just-reborn Christians, or even just-'deconversed' nonbelievers.
- chromatic 14y agoThat's the attitude which annoys me, as someone who first used Ruby in 2000 and had been doing web programming since 1998. Neither Ruby nor Rails invented a lot of things, nor did it perfect them. (Rails does deserve credit for promoting "convention over configuration" as a design concept, but plenty of us were doing similar things years earlier.)