Quote:
Originally Posted by JD159
Just managed a project built in Ruby on Rails for the backend and React on the front-end. Chose Rails because I really don't like the inconsistent skill levels with PHP development. Whereas with rails if you follow the conventions it is pretty secure, just harder to find a developer.
PHP developers are a dime a dozen and many won't follow proper conventions. As a language it is getting kinda messy for some web applications. If your project has outsourced PHP, usually the code is the reason for the website being brought down. Ask me how I know!
I develop myself in HTML, CSS and jQuery, but am not versed in PHP or SQL, aside from holding together a "legacy" program. I had a new developer start a project in PHP and saw where it was going and how messy/vulnerable the structure was and cancelled. That was when I began looking for Rails.
What's your thoughts on Rails as a backend stomachmonkey? PS. Used postgres for the database on my new program.
|
I actually prefer PHP primarily since it's so easy to find people.
I only have two guys I work with when it "matters".
I'm less concerned with the language, it's "the guy" that matters.
But we also do a lot of hand off work. Meaning build it for the client then they take it over. That kind of dictates to some degree what is used to build their solution. We don't like doing maintenance stuff.
I also hate being held hostage by proprietary solutions that keep me tied to certain individuals / groups and take that approach with clients. They are more than welcome to retain us long term but the choice is theirs and the work is done in a way that leaves the choice up to them.