4 ms·

Inserting a big chunk of C++ into my Apache listeners doesn't give me warm fuzzy feelings. Neither does the fact that mod_rails just flat-out doesn't work on OS

by rcoder 18y ago

Inserting a big chunk of C++ into my Apache listeners doesn't give me warm fuzzy feelings. Neither does the fact that mod_rails just flat-out doesn't work on OS X, which is where a large number of Rails developers do most of their actual, y'know, development. Personally, I don't think you can really call this a 1.0 release. Pre-beta preview, maybe; stable, point-oh release, definitely not.

prototype 18y ago
"Inserting a big chunk of C++ into my Apache listeners doesn't give me warm fuzzy feelings." Uhm, what language do you think all the Apache modules (mod_rewrite, mod_perl, mod_php, etc.) are written in? They're all either C or C++, so by your logic all of Apache won't give you warm fuzzy feelings. "Neither does the fact that mod_rails just flat-out doesn't work on OS X," This is false. Passenger does work on OS X, but because of an issue in the default Apache installation provided by OS X, Passenger is unable to work. If one installs Apache via MacPorts (or some other means) then Passenger will work just fine. In fact, the installer warns the user about exactly this issue. Many, many people have tested Passenger on OS X, and it works fine for them. Ryan Bates of Railscasts, the one who made the screencast, used OS X. Pratik Naik, a Ruby on Rails core developer who helped with testing Passenger, used OS X.