2 ms·
> Right, but the problem is that there doesn't seem to be a 'right' way, That's the problem. The problem is that the state of the art changes. The reason Rail
by dasil003 15y ago
> Right, but the problem is that there doesn't seem to be a 'right' way, That's the problem.
The problem is that the state of the art changes. The reason Rails is still relevant is because the core team is committed to improvement, even at the expense of API stability and legacy support. That's definitely a valid concern for someone supporting apps on a shoestring, but on the other hand it makes Rails more suitable for someone who wants to stay on the cutting edge. You simply can't have it both ways...
> We were all prototype a few years ago, now it jquery ...
You mean __7__ years ago when they chose it as the default? Rails was the first framework with Ajax support built-in, and it was done poorly because nobody understood how it should really work at the time.
> we (well I) hadn't heard of coffeescript till a few months ago and now its a default option in rails
It's easy to argue that CoffeeScript shouldn't be a default, but then it's even easier to just turn it off. Shouldn't be a point of major contention, but I can see how people don't like it.
> The way we were constructing ActiveRecord finders had been set all through Rails 2, now we've changed it
Yes, they replaced a hodge-podge of ad-hoc query construction with a relational algebra library that enables dramatically more flexible query construction and lazy loading. Who knows how many broken edge cases were fixed merely by the switch to a proper mathematical basis.
> the way we dealt with gems was set all through rails 2 now its changed completely in Rails 3.
Bundler solves dozens of thorny issues that were intractable in the Rails system. Now Rails is simpler because it doesn't have to have any gem activation code, it's handled by a separate library that can solve your gem management problems for your non-Rails projects as well. You may not have run into any of these issues, but I assure you there were real and Bundler is a big step in the right direction.
> the way we dealt with gems was set all through rails 2 now its changed completely in Rails 3.
Yeah but what are the implications of that? You want Microsoft-style legacy support from Apple? They ain't gonna give it to you, because that lack of legacy support is what enables them to move forward at the pace they do. This has definitely impacted the type of projects I feel comfortable delivering in Rails (ie. no low-budget small client sites), but for an actively developed app it makes Rails a more attractive place to be.