I'd wonder why they're pressuring you to move to PHP. I've written PHP in the past, and recently started maintaining a site in PHP through a company acquisition

I'd wonder why they're pressuring you to move to PHP. I've written PHP in the past, and recently started maintaining a site in PHP through a company acquisition. Normally I prefer Ruby on Rails and have used it since Rails v1.2.3. I consider PHP to be a step backwards technology and tooling wise. Laravel seems like the nicest copy of Rails, but it seems like everything nice in PHP is a crude copy of something from the Ruby/Rails ecosystems. Frequently in PHP I found myself missing a proper REPL, yes PHP can be run interactively with `$ php -a`, but it doesn't print the last returned value, so spelunking in a running system is slow and awkward, luckily I've found Boris(https://github.com/borisrepl/boris https://github.com/borisrepl/boris) which is more like IRB or Pry, but it's still unpleasant when I'm trying to kill a tricky bug. On the package management front Composer is a better solution than previous PHP offerings, but it's got some quirks that make it seem unpolished compared to Bundler. If I was given a choice PHP I would never willingly pick PHP. I suspect your company is pressuring you to move because they think they can get PHP devs at a lower cost than Ruby devs. If you're in the Bay Area there are plenty of companies that will hire you to write Ruby so you don't really have to switch if you're not comfortable with it.