3 ms·

However with Rails being an opinionated framework, there is typically one really publicized opinionated way to do one thing (ala Python style). Perhaps so, but

However with Rails being an opinionated framework, there is typically one really publicized opinionated way to do one thing (ala Python style). Perhaps so, but as with Python that way changes over time.

chaostheory 14y ago
Staying on subject - does it matter, as long as that evolved way remains a reasonable and good way to develop? I started with Rails 2.x, and I did find it painful to transition to Rails 3.x after a few years of not using it. In the end though, I find myself really liking the decisions made for Rails 3.x. It's helped my productivity a lot.
- drbawb 14y ago
  >Does it matter . . . To you, no; to me? No. The same thing happened to me: Rails 3 came along. My web applications weren't so large that the port would be unreasonable, so I gritted my teeth and came out feeling like I had gained something. (Knowledge, experience, productivity.) --- For every "you", however, there is someone with a non-trivial Rails 2.x codebase that simply won't invest the time or energy to port it. So they'll keep using it; keep developing libraries for it, keep patching it, etc. Continue this trend, and I'd imagine you end up with something like the Python2/3 schism. For an example of what this leads to, look at Rust. Arch Linux uses Python 3 as the default for /usr/bin/python, Rust (0.3 and it looks like 0.4) fails to compile because LLVM can't stand Python 3. [This is described in the Rust 0.4 release notes. Of course the fix is a simple symlink and an EXPORT= away once you install Python2.] So you end up with _new and exciting projects_ that require you to install and maintain old tools and libraries. Why? Because eventually _a non-negligible_ number of library maintainers stop trying to hit a moving target. I'm not saying Rails will _necessarily_ go down that road; but Python has already been there, and the Python 2/3 schism isn't pretty. It's a possibility worth entertaining, anyways.
  - chaostheory 14y ago
    You have good and valid points that I agree with, I was just arguing was from the standpoint of "Rails / Ruby becoming another PHP" > I'm not saying Rails will _necessarily_ go down that road; but Python has already been there, and the Python 2/3 schism isn't pretty. It's a possibility worth entertaining, anyways. I feel the Ruby community is different from Python's. I think people who work with Ruby and/or Rails like new toys and they are willing to adapt in order to keep playing. If anything I feel the bigger danger is for Ruby devs migrating to nice shiny toys that node.js has to offer.

chaostheory 14y ago

Staying on subject - does it matter, as long as that evolved way remains a reasonable and good way to develop? I started with Rails 2.x, and I did find it painful to transition to Rails 3.x after a few years of not using it. In the end though, I find myself really liking the decisions made for Rails 3.x. It's helped my productivity a lot.

drbawb 14y ago
>Does it matter . . . To you, no; to me? No. The same thing happened to me: Rails 3 came along. My web applications weren't so large that the port would be unreasonable, so I gritted my teeth and came out feeling like I had gained something. (Knowledge, experience, productivity.) --- For every "you", however, there is someone with a non-trivial Rails 2.x codebase that simply won't invest the time or energy to port it. So they'll keep using it; keep developing libraries for it, keep patching it, etc. Continue this trend, and I'd imagine you end up with something like the Python2/3 schism. For an example of what this leads to, look at Rust. Arch Linux uses Python 3 as the default for /usr/bin/python, Rust (0.3 and it looks like 0.4) fails to compile because LLVM can't stand Python 3. [This is described in the Rust 0.4 release notes. Of course the fix is a simple symlink and an EXPORT= away once you install Python2.] So you end up with _new and exciting projects_ that require you to install and maintain old tools and libraries. Why? Because eventually _a non-negligible_ number of library maintainers stop trying to hit a moving target. I'm not saying Rails will _necessarily_ go down that road; but Python has already been there, and the Python 2/3 schism isn't pretty. It's a possibility worth entertaining, anyways.
- chaostheory 14y ago
  You have good and valid points that I agree with, I was just arguing was from the standpoint of "Rails / Ruby becoming another PHP" > I'm not saying Rails will _necessarily_ go down that road; but Python has already been there, and the Python 2/3 schism isn't pretty. It's a possibility worth entertaining, anyways. I feel the Ruby community is different from Python's. I think people who work with Ruby and/or Rails like new toys and they are willing to adapt in order to keep playing. If anything I feel the bigger danger is for Ruby devs migrating to nice shiny toys that node.js has to offer.