Here's the one thing. I really like Ruby and I have used it within the last few years. I really like everything concerning the language and also the community.
However I have this soon-to-be-large WordPress site, where I must implement lots of additional functinality. The issue is, I truly hate designing WordPress beyond simple theme design.
Good examples of things I have to do:
- then add more information to profiles, like karma/points/status system
- offer customers to produce their very own page after they are permitted to get it done
- tugging data from some exterior API and exhibiting it around the user's profile
I acquired really accustomed to the entire agile BDD workflow, where Time passes from Cucumber features to RSpec to applying the stuff, and also the whole WordPress architecture looks in my experience like ok I am just gonna need to pray this works.
I am unsure whether it's even smart to try and write some area of the application in Ruby and then try to have great results along with WordPress, or maybe I ought to simply take WordPress because the only factor I have got and take full advantage of it's strenghts and weak points.
The primary problem for me personally is the fact that everything I am likely to write in PHP will require about 5 occasions as lengthy than basically get it done in Ruby, and it'll most likely be also safer and robust, since i have do not have just as much knowledge about complex PHP stuff. I am talking about I have done lots of PHP previously, however i always felt such as the whole factor will break apart at some point.
I understand there's most likely no definite answer regarding how to approach this, but any suggestions are welcome.
We have integrated a Rails application right into a TYPO3 installation. It exercised pretty much. The main factor is by using Rails' support for adapting models to tables of the legacy application. An essential point would be to handle authentication which we handle by passing the TYPO3 session answer to the Rails application inside a hidden way (using PHP because the web-client and passing appropriate headers) and searching up within the session table (improving the session timeouts). The Rails application is planned right into a sub directory using passenger. Performance is excellent, it's even amazing in comparison to the previous implementation attempting to use Extbase.
So, to conclude: Should you choose it right and also the connects between your two applications are very well planned this kind of approach can provide wonderful benefits and the very best of two mobile phone industry's. Otherwise done correctly or else you do not understand some implications of Wordpress (like security) you'll produce a large mess vulnerable to security breaches.
BTW: We arrived at feature parity using the Extbase (MVC framework in TYPO3) solution after 4 times of using Rails. The Extbase solution required 6 weeeks and triggered lots of headache and trouble. So that your time factor might be better still than 5:1.