3 ms·
it's a business decision comparison, not a technical categorical comparison. you need something to receive http request and return http responses, and you're co
by nrser 10y ago
it's a business decision comparison, not a technical categorical comparison. you need something to receive http request and return http responses, and you're comparing different popular (because hiring, training, and available community / support resources) ways to do that. they might be apples and oranges but at that level you're concerned with comparing fruits.
- bigtunacan 10y agoIn this case it was a technical comparison; the original poster stated, "php's performance was an order-to-two or magnitude better than rails". If you are making a technical comparison then it needs to be at the correct layer of abstraction. If we were to compare performance of Laraval and Rails that would be a fair comparison. If we are comparing on performance then PHP should be probably be compared to Ruby+Rack since that is sort of the lowest common denominator. I'm not dogging on PHP here either. Even comparing at the correct level; PHP is still faster, but lets make sure we are making the right comparisons.
- nrser 10y agoi am the original poster. i was clarifying the compassion.