tl; dr

Posted by s.f. on November 23, 2008

Echo-chamber-driven Internet Drama on the rise in the Ruby community. Again.

Giles Bowkett:
original, followup, self-flagellation

_why’s sum-up and thoughts.

Zed’s response to _why’s mention.

_why fires back.

Can we skip this and go straight to the Yo Momma Fight? Loser gets Force-chucked into experts-exchange.com!

testing to irritation 2

Posted by s.f. on March 31, 2008

So after wasting spending a few days checking out other test frameworks for Ruby/Rails, I’ve come up with this:

Rspec:
The Textmate plugin is barely useable; it appears to have a completely different manner of loading files versus the standard spec command(placing a spec file next to its target and doing a simple ‘require’ worked for the spec binary; the Textmate plugin waves its hands desperately). Wolf howls and tumbleweed are all that is received from asking about it on the #rspec IRC channel.
The bundle works OK under Rails,but of course now the simple use of cache_fu is freaking it out when coming to fixtures(and not even guarding the acts_as_cached statement with ‘defined?’ works because rSpec hooks into Kernel and does all kind of crazy voodoo).
This post gushes about “rspec leaving TDD in the dust”, I’ll believe it when some more consistency is gained.
rspec’ers are going to accuse me of being another idiot user who can’t set up their system correctly. I’ve setup Mysql multiple times(binary release, DarwinPorts, Macports, version) and made countless other mistakes(and fixed them) on my G4 laptop since 2004; I have a hard time thinking that some obvious mistake I’ve made is gumming up the works.

Shoulda would be a nice alternative(plugs into existing test/unit, but it depends heavily on autotest, and autotest still petulantly refuses to believe in namespaced Rails controllers, despite the availability of a patch. I may try updating the patch in the next day or two and giving it another go, but after two days and negative productivity gains, my gut feels like sticking with Test/Unit and friends, because They Just Work. And Just Working is rated higher in my book, no matter what sexy new features are in abundance(like mocking/stubbing)

:eno: 2

Posted by s.f. on January 05, 2008

So, Zed spewed. Since I guess I’m now a Rails “professional”, I guess I’m supposed to have some sort of up-in-arms opinion.

I really couldn’t care less.

Once you pick up that Zed writes in a deliberately provocative manner, reminiscent of the SA Forums, the rant’s main points boil down to his personal experiences with consulting, and elements of the Rails community being too uptight.

The only thing I found really entertaining about the affair(outside of the Rubinius praise) are the responses popping up on mailing lists looking to move away from Mongrel, because they just can’t trust software written by a person who posted “something like that”. If your sentiments are similar, I hope you’re not using OpenBSD(Theo), ReiserFS(Reiser), or anything GNU-related(Stallman)

In my professional life I’ve had to use a lot of software I considered brain-damaged(custom Java object-frameworks, antiquated news databases, PHP), but the dislike almost always stemmed from experience with the software itself, not the person/teams behind it.

you are in a twisty little maze of developer packages, all alike

Posted by s.f. on November 29, 2007

“Use Fink until it pisses you off, then switch to DarwinPorts. That’s what everyone else seems to do.” : from jwz’s blog.

“Indeed”, he said, as he executed “sudo rm -rf /sw” on his developer machine at work.
(That’s not to say MacPorts is a utopia free from stupid issues though, it just seems to guarantee more consistency).

protip: you see no protip here

Posted by s.f. on September 19, 2007

I had bullet points for a Visual Studio rant after wrapping up the C# side-project that has consumed my summer, but this guy already said much of what I wanted to say.
About all I can add to it is a harumph at Microsoft documentation: yes, MSDN is obviously a force to be reckoned with(if you can pay the entry fee), but it’s tedious to play the back-n-forth game of “look up the actual API via IntelliSense, and look up actual examples in MSDN’s clunky public web interface / hope that a google search for the control will return more than a ‘getting-started tutorial’ that covers what MSDN already did”.

Contrast that with How To Learn Cocoa, Cocoa Dev Central, and Apple’s own Cocoa Reference Library. All free, fairly well written, and more than enough to get you started with basic Cocoa apps.

Meanwhile, discovering exactly how to fire events from buttons in .NET took up most of a week’s evenings.