4 ms·

I am not sure installing a full stack web framework, a version control system, and automated deployment to public hosting should be _that_ easy. Learning how to

I am not sure installing a full stack web framework, a version control system, and automated deployment to public hosting should be _that_ easy. Learning how to install it all is very informative as to what is going on. e.g. Deploying to Heroku is in fact very easy. Ok you have to mess around with ssh keys, but you don't want that to be automagic - you want to have some understanding of why what you are doing is secure, and why anyone else can't access your code.

j45 14y ago
If you want it to replace php (or anything), it has to be as accessible as php for the same developer. Until then, all the conversation about standards, best practices, and tutorials are far less accessible.
- philwelch 14y ago
  The purpose of Rails isn't to replace PHP.
  - j45 14y ago
    It might not be, but our Rails heads sure do like talking about PHP a lot. If a technology is truly supposed to be accessible it needs to actually, be accessible instead of carrying an air of superiority, otherwise software continues to suffer.
    - deleted 14y ago
      [deleted]
    - philwelch 14y ago
      Rails isn't supposed to be accessible the way PHP is, i.e. built into every shared hosting account with unlimited flexibility as to what you can do with it. If that was the right way to go for web applications, there would have been no need for Rails in the first place, since PHP would have been sufficient.
      - j45 14y ago
        I'm not sure where it was said PHP is only shared hosting. Besides, many places start on shared hosting, kind of like Heroku for rails code, no? I'm also not sure where the idea is coming from that Rails shouldn't be accessible to developers. If you have some wider posts or links I'd love to read some more.
        philwelch 14y ago
        Rails is accessible to developers who have a baseline of competence. PHP is accessible to complete beginners.
        j45 14y ago
        Again, is that your opinion / preference, or can you share a source? Most interested to see where this is coming from beyond things I could google myself.

j45 14y ago

If you want it to replace php (or anything), it has to be as accessible as php for the same developer. Until then, all the conversation about standards, best practices, and tutorials are far less accessible.

philwelch 14y ago
The purpose of Rails isn't to replace PHP.
- j45 14y ago
  It might not be, but our Rails heads sure do like talking about PHP a lot. If a technology is truly supposed to be accessible it needs to actually, be accessible instead of carrying an air of superiority, otherwise software continues to suffer.
  - deleted 14y ago
    [deleted]
  - philwelch 14y ago
    Rails isn't supposed to be accessible the way PHP is, i.e. built into every shared hosting account with unlimited flexibility as to what you can do with it. If that was the right way to go for web applications, there would have been no need for Rails in the first place, since PHP would have been sufficient.
    - j45 14y ago
      I'm not sure where it was said PHP is only shared hosting. Besides, many places start on shared hosting, kind of like Heroku for rails code, no? I'm also not sure where the idea is coming from that Rails shouldn't be accessible to developers. If you have some wider posts or links I'd love to read some more.
      - philwelch 14y ago
        Rails is accessible to developers who have a baseline of competence. PHP is accessible to complete beginners.
        j45 14y ago
        Again, is that your opinion / preference, or can you share a source? Most interested to see where this is coming from beyond things I could google myself.