The poster's point isn't really about Ruby. Ruby works just fine with HTTPS, thank you very much. It's not like Ruby handles the HTTPS encryption. I think his point is more "I hear the excuse 'it uses too much CPU time', but this is often from people who [should be looking elsewhere if they have performance problems]".