3 ms·
As a PHP developer, I found learning Ruby and Rails at the same time too much. I went back to PHP, learned MVC in a language I was familiar with, and then when
by seldo 16y ago
As a PHP developer, I found learning Ruby and Rails at the same time too much. I went back to PHP, learned MVC in a language I was familiar with, and then when I went back to rails it was clear which bits were Rails features and which bits were Ruby language constructs.
Of course, I then decided that I didn't like Rails enough to put up with its performance issues, and went back to writing MVC in PHP, so I may be a bad case study. (I hear RoR 3.0 is much better performance-wise, but my current solution works well enough that I'm not interested in trying it out again)
- regularfry 16y agoI found precisely the opposite. Because it was relatively quick to get something impressive working in Rails, it didn't matter to me initially which bits were Ruby and which were Rails. That all came later.