4 ms·
We did go for Ruby in order to increase developer productivity (having a very small team of just two developers), and good code quality/high test coverage. We w
by jrirei 15y ago
We did go for Ruby in order to increase developer productivity (having a very small team of just two developers), and good code quality/high test coverage. We were sure we needed to refactor a lot later on. So Ruby seems like a good choice.
But Ruby is NOT good at waiting no a database / network latency. But I guess with PHP we would have had exactly the same problems.
- iconfinder 15y agoDid you compare bare bones PHP with Ruby or PHP with a library such as Zend? I curious because I'm considering recoding a large part of a website and are trying to avoid scaling issues. Thank you for the answer.