3 ms·

Feels like nitpicking, but alright... What's better for making a blog? Tweaking a PHP wordpress theme or making something using Ruby on Rails? Your Mileage May

by RyanZAG 14y ago

Feels like nitpicking, but alright... What's better for making a blog? Tweaking a PHP wordpress theme or making something using Ruby on Rails? Your Mileage May Vary ? The reason that term is used a lot is because there is a huge amount of evidence that each technology choice usually has very specific project criteria in which it shines, and if you change the criteria even a little bit, there is often a technically better choice - let alone a new technology that could be developed specifically for those new criteria.

randomdata 14y ago
My experience with blogs says they will quickly turn into their own application and then you either have to mess with integration between the two systems, or you build the application on top of the blog. Each come with plusses and minuses, but in the latter case, if you start with something like Rails, then at least you have Rails at your disposal for the growing application. Though if it is really never going to become more than just a blog, I choose static files with a simple compilation procedure, personally.
theevocater 14y ago
I'm no ruby wizard but there are things like wordpress built on top of rails. monologue, enki, jekyll, etc so you give a false dichotomy
jessedhillon 14y ago
This seems like shifting goal posts. First we're talking about Facebook and half the internet, now we're talking about context-specific technical solutions (and I don't concede that WP is the unilaterally superior blogging option either.) Moreover, I'm not sure where your disagreement with OP is, since you're simply saying now that for a given set of criteria, a superior choice exists. Which was the message in the first place.
- RyanZAG 14y ago
  The OP is saying we should not use terms like 'Your Mileage May Vary'. Instead, we need to just say which solution is better. I'm pointing out how this isn't the correct way to go about it unless you specify the exact circumstances. And this is where I agree with you completely. You can't say that because someone is making a blog they must use WP as it is the correct choice. You can say 'I believe WP will be the correct choice in making a blog but Your Mileage May Vary depending on what you want to do with the blog and if you are more proficient in Ruby than in PHP. This is exactly my argument, as the OP says you can't do this kind of thing and need to give a concrete solution. However, this kind of thing is incredibly necessary, and saying to use WP for every blog is just wrong.

by RyanZAG 14y ago

randomdata 14y ago

My experience with blogs says they will quickly turn into their own application and then you either have to mess with integration between the two systems, or you build the application on top of the blog. Each come with plusses and minuses, but in the latter case, if you start with something like Rails, then at least you have Rails at your disposal for the growing application. Though if it is really never going to become more than just a blog, I choose static files with a simple compilation procedure, personally.

theevocater 14y ago

I'm no ruby wizard but there are things like wordpress built on top of rails. monologue, enki, jekyll, etc so you give a false dichotomy

jessedhillon 14y ago

This seems like shifting goal posts. First we're talking about Facebook and half the internet, now we're talking about context-specific technical solutions (and I don't concede that WP is the unilaterally superior blogging option either.) Moreover, I'm not sure where your disagreement with OP is, since you're simply saying now that for a given set of criteria, a superior choice exists. Which was the message in the first place.

RyanZAG 14y ago
The OP is saying we should not use terms like 'Your Mileage May Vary'. Instead, we need to just say which solution is better. I'm pointing out how this isn't the correct way to go about it unless you specify the exact circumstances. And this is where I agree with you completely. You can't say that because someone is making a blog they must use WP as it is the correct choice. You can say 'I believe WP will be the correct choice in making a blog but Your Mileage May Vary depending on what you want to do with the blog and if you are more proficient in Ruby than in PHP. This is exactly my argument, as the OP says you can't do this kind of thing and need to give a concrete solution. However, this kind of thing is incredibly necessary, and saying to use WP for every blog is just wrong.