Is it worth overpaying for a ruby ​​site today? Or save on php?

Question

CMS

Good afternoon everyone.
The question is.
You need to make a website from several components: News (large main page, categories, etc.), blogs (standard functionality) and a registered user page (avatar, own news feed, pm, comments, subscriptions, nothing special at all). In the future, the site is planned to be seriously developed and developed in the social. direction + there will be a lot of additional functionality (for example, an online store, etc.)
The cost of development on php is about 2 times lower than on ruby, hence the question is it worth overpaying for ruby? Further development in ruby ​​will also be more expensive.
Is it possible to end up with a product of higher quality and performance on ruby ​​than on php (for example, on symfony2) or will it be about the same thing only 2 times more expensive?
Thank you all in advance for your help.

Answer 1

An extensible and productive application can be developed in any language, the question, as always, is in the performers.
You argue too naively: I will invest 2 times less and get the same. Alas, you can get anything from 10 times better to 10 times worse, regardless of technology.
If we are talking about the same developer, he still knows one technology (PHP) better and perhaps you are also offered to pay for your training (Rails) with an unpredictable result for you.
If these are different developers, then you need to look and compare. Perhaps those who ask cheaper and do worse. Or, for example, standard requirements fit into their CMS, but extended ones - the price tag can grow 5 times.
In any case, it is necessary to discuss the maximum program with the developers in advance, to clarify how much it will cost in terms of time and money.
PS: I read here about the slowness of ruby ​​from fellow php-shniks, briefly - this is a myth from the distant past, it does not correspond to the current state of affairs

Answer 2

In my humble opinion, this makes no sense (as a symfony2 developer).
Why not: because ruby ​​has no advantages in this case. As you said - the cost of development is higher, the profit in terms of performance is 0, Ruby even eats more resources.
If there was a choice between JVM languages ​​(java, scala) or the recently popular go and erlang, for the sake of performance, it might be worth it. But clearly not a slow ruby.

Answer 3

If you need tools such as newrelic , airbrake , deploy with capistrano and others from the rail ecosystem.
PS: I don't think Symfony will be cheaper.

Answer 4

Carefully! Not the traditional way of looking at the question.
Any site works according to the "HTTP request - HTTP response" scheme.
Which technology will respond to requests in general is not very important, and if it becomes important for specific requests, it can be replaced.
You need to think about how the application will work with the so-called. business and from the user's point of view.
Get, conditionally, a bunch of requests (urls with parameters) and responses (screens, pages), grouped by functions or something else.
Then look for responsible people and give them to study and implement certain parts of the project.
They themselves will choose the appropriate technology. Why should you think about it?
Evaluate everything in terms of money, time and quality.
Some things can be done in Ruby, other things can be done in PHP, because they can be done in 2 days. Something in general will be given as a static.
The main thing is a good project (characters, scenarios, screens, TK) and people on the sites, whether it's one person or ten.

Answer 5

I don't understand why it's twice the price. Well, it would be 30% more expensive there, but two? The development time for this project in Ruby is even slightly less than in PHP, or approximately equal. Covering the code with tests and so on does not give much difference in terms either.
Conclusion, either you found a Ruby developer with an overpriced rate, or a PHP developer with a rate twice as low. If the latter, then it is worth wondering if he has enough qualifications? Maybe during the evaluation, he did not take into account code coverage by integration / functional tests, maybe something else.
On a good cost should not be so much different. The rate of a strong Symfony developer is not lower than the rate of a good RoR developer. According to your meager description, RoR will most likely have less time. Conclusion, RoR should be cheaper. In terms of capabilities, Symfony is more suitable for long-term projects, it is faster than Ruby (on hhvm it is decently faster), but there are more high-quality ready-made solutions for RoR, which should also reduce development time.
In a word ... somehow cloudy. Describe how you got "2 times cheaper".

Answer 6

Rails is a very well built MVC framework. But despite this, performance even compared to slow PHP is very lame. In general, my experience with rails did not make me understand why to switch from PHP to it. Symfony2 and Laravel are excellent frameworks. See for yourself.
Why is it more expensive - everything is very simple. Almost every web programmer is familiar with PHP but not Ruby. Hence the price - those who write on Rails, at the moment, are very few, and are unlikely to increase in the near future. But, there are few competent web programmers in the PHP world, not everyone knows and is familiar with MVC. Therefore, you also need to look for a Symfony developer. Despite the fact that the MVC pattern is gaining popularity at a breakneck pace, Yii is mainly used in the Russian-speaking community.

Answer 7

Behind rails is DHH and a large community. Bugs are fixed quickly, new versions improve the performance of both the rails themselves and the ruby ​​itself. And according to rps benchmarks, they are all in the same category. I generally keep quiet about various kinds of gem's.
On rails, a bunch of startups have been written and fired - everything works and scales well.
twitter.com/
github.com/
www.shopify.com/
basecamp.com/?source=rail...
soundcloud.com/
www.hulu.com/
Who writes symfony? Will this framework die tomorrow and why exactly symfony and not some codeigniter?
IMHO, I would choose rails, at least for the stable future of this framework. DHH has a business tied to it, several startups have been written such as -https://basecamp.com/ so that the framework will only develop and improve.

Answer 8

To an experienced php programmer, I would prefer an experienced ruby. In 90% of cases, a ruby ​​person has already tried php and php frameworks or frameworks in other languages. And with a greater probability, he will be able to bring the project to production and develop further.

Answer 9

As a customer, it would never even occur to me to develop something like this in ruby. Swap for soap, and then suffer in search of competent rubists...
PS There is no need to make ridiculous comparisons - nameless ordinary customers, usually with a limited budget, against well-known companies with a reputation and external investments.
First of all, for start-up businesses, money plays a paramount role.

Answer 10

you will never save money on symfony2

Answer 11

In my unqualified opinion, the cost of professionals will be equivalent. I am very new to Rails but have long experience with PHP. I really liked Ruby in terms of having scaffold, which significantly speeds up development. Again, the level of entry into Rails is quite high, which suggests that even an average Rails programmer will be more competent than a PHP developer.
Ruby has no performance problems, but there are scaling problems (relevant for projects with a million daily traffic), but they are solvable. I believe that in the next couple of years this will not threaten you.
If you really have the site described above, then professional rubists will make it for you in a week, because. there is nothing special for them. In the presence of layout, of course. It will cost more, but the faster you can develop the project, the better. Again, continuous integration tools will automate the deployment of new versions, testing, etc. As a result, it will allow to keep the development and testing at a very high level.

Answer 12

in your case, you can not look at RoR :) this is definitely not for your project.