Ask HN: MVP uses PHP, needs a rewrite. Should we use Laravel, or Ruby on Rails?
I'm working on a project and am considering a full rewrite in order to clean up bad code, improve security, and most importantly: make it easier to add new features going forward.
I'm knowledgable in PHP, and new to Ruby on Rails. I could reuse existing code with Laravel [0], but it needs much more than a simple refactoring, and it'd be nice to rewrite everything with PHP5+ conventions (classes and inheritance, etc).
Switching to Ruby on Rails will force a full rewrite, and I wouldn't mind using this project as a means to dive into ruby.
One concern is that it might take longer to learn ruby on rails than to rewrite the PHP version, but if ruby makes adding new features easier in the future, it would have been well worth it.
In the end, both approaches are basically a full rewrite. Any suggestions? Has anyone encountered a similar scenario?
[0] http://laravel.com/
4 comments
[ 3.7 ms ] story [ 23.1 ms ] threadSure it is nice to learn a new language/framework while you work on an idea but it is also the easiest way to get discouraged from finishing as it will take longer to complete.
If you want to make money on the project and want to get it out as fast as possible Go with laravel. You already know the stack and will be productive in it. You might also be able to reuse parts of the code thats already written or put it in the right place.
On the other hand if you want to learn another programming language or want to go outside of your comfort zone then give Ruby on Rails a shot. Not sure about Laravel but for a small to medium website, ruby does make adding a lot of features much faster via its gems.