Having occasion to write a small webapp, which I want to be fairly portable, I'm dusting off my PHP.
After having used Ruby for a couple of years, the return to PHP is jarring.
It's not the lack of object orientation (yeah, I know, PHP does have an object system grafted on). Heck, I still do most of my programming in C!
No, it's little stuff, like only being able to interpolate variables into strings, instead of entire expressions as in Ruby. So, I end up evaluating a bunch of fairly simple expressions into variables, and then interpolating the variables into a heredoc. Fiddly stuff like that.
I have the feeling that the script that turns the output of the webapp into configuration files will be written in Ruby. It doesn't need to use a web browser as a front end, and thus a web server as an intermediary, and it'll be running in an environment where a Ruby interpreter is required anyway.
Of course, I could, in principle, write the whole mess in Ruby, with a GTK or QT GUI... but that would take a whole bunch longer, and this particular task is well suited to Web 1.0 forms. Coding up a GUI with a lot of repeated (but uniquely tagged) form elements gets to be a pain, and I don't have a lot of either GUI-coding or toolkit-(re)learning time in my schedule just now.
(Update: and then I go back to programming in C, and get the switch/case statement syntax mixed up with Verilog. What fun!)