3 ms·

LOL. Why not just go the whole hog and run wordpress inside ruby, using tenderlove's Phuby bridge/adapter/thing. https://github.com/tenderlove/phuby https://g

LOL. Why not just go the whole hog and run wordpress inside ruby, using tenderlove's Phuby bridge/adapter/thing. https://github.com/tenderlove/phuby https://github.com/tenderlove/phuby Demo of him actually using this to run wordpress inside rack: http://www.youtube.com/watch?v=MXERy8Y2eVo http://www.youtube.com/watch?v=MXERy8Y2eVo Or, you know, spend a day knocking together your own blog in rails. I guess it could be good if you are wedded to a preexisting client base which demands wordpress, even for new projects, in which case my sincerest condolences go out to you. To be fair, I'd imagine that those people who are raking in big $$$ doing WP themes must have something like this set up already.

steffoz 15y ago
I'll quote Wynn Netherland on a post about his take on the very same problem: "I'm a Rubyist. But I'm also a pragmatic front-end developer. When I have to write a full-stack solution, I pick Rails or Sinatra because writing Ruby is a joy and the Ruby ecosystem is so darn cool. But when I have to create a CMS-based site for myself or a client I love the usability and community behind WordPress. Although I can reluctantly lay Ruby aside when I extend WordPress, I really miss my syntactically awesome stylesheets. Until now." http://wynnnetherland.com/journal/sass-up-your-wordpress-themes-with-compass http://wynnnetherland.com/journal/sass-up-your-wordpress-the...
smcnally 15y ago
"Or, you know, spend a day knocking together your own blog in rails." Understood you're exagerating for effect, but underestimating the complexity of a process like "blogging," over-estimating how much of it can be "simply" reëngineered, and dismissing the collective work of tens of person years is a real issue. I've witnessed that attitude cost businesses dearly. Just because you can do something doesn't mean you should. Just because you do do something, doesn't mean you didn't spend a ton more resource than was necessary. And because you spent more resource than needed doesn't mean you delivered the best possible result.

steffoz 15y ago

I'll quote Wynn Netherland on a post about his take on the very same problem: "I'm a Rubyist. But I'm also a pragmatic front-end developer. When I have to write a full-stack solution, I pick Rails or Sinatra because writing Ruby is a joy and the Ruby ecosystem is so darn cool. But when I have to create a CMS-based site for myself or a client I love the usability and community behind WordPress. Although I can reluctantly lay Ruby aside when I extend WordPress, I really miss my syntactically awesome stylesheets. Until now." http://wynnnetherland.com/journal/sass-up-your-wordpress-themes-with-compass http://wynnnetherland.com/journal/sass-up-your-wordpress-the...

smcnally 15y ago

"Or, you know, spend a day knocking together your own blog in rails." Understood you're exagerating for effect, but underestimating the complexity of a process like "blogging," over-estimating how much of it can be "simply" reëngineered, and dismissing the collective work of tens of person years is a real issue. I've witnessed that attitude cost businesses dearly. Just because you can do something doesn't mean you should. Just because you do do something, doesn't mean you didn't spend a ton more resource than was necessary. And because you spent more resource than needed doesn't mean you delivered the best possible result.