Re:Stop writing good code; Start writing good software.
by davesims on Saturday November 19, 2011 @05:09PM
(#3256423)
Ah, gotcha. Yeah, config issues can be painful in many environments, and Rails has its own brand of frustrations, particularly when upgrades are concerned.
This is just a shot in the dark, but if you're on REE/Passenger and getting thread/segfault issues, you might try Apache's Passenger config with the conservative spawn method. I've had similar issues in the past resolved by simply not using REE's shared memory.
http://modrails.com/documentation/Users%20guide%20Apache.htm...
Re:Stop writing good code; Start writing good software.
by nirvdrum on Saturday November 19, 2011 @05:18PM
(#3256453)
Thanks. I had to do that recently because of issues with the prepared statement pool in 3.1 + Passenger. But I can segfault in 1.9.2 just by loading a console or running tests. It doesn't instill a grand sense of stability.
Thanks for the feedback though. I find it helpful to do periodic sanity checks.
So, when looking at productivity, I'm not necessarily looking at the language itself, but the entire environment I need to work in. I may just be doing something grossly wrong, which is why I inquired.
If it helps frame things at all, my primary project is coming up on 2 years old and started as a Rails 2.3 app that recently had a very painful upgrade to 3.1 (took on the order of 75 hours). And I had a couple years experience prior to that doing Ruby & Rails stuff.