Rails 3.1 Release notes

[魏伦 Allen Wei]

http://guides.rubyonrails.org/3_1_release_notes.html

大家对哪些feature比较感兴趣，我们可以做个demo的app

[Andy]

其实已经作了两个rails3.1的项目了..

做个demo的建议不错，你可以在github上面起一个app，大家谁有空可以按照release notes提到的feature往里面填一点例
子。

On Aug 31, 11:23 pm, 魏伦 Allen Wei <digr...@gmail.com> wrote:
> http://guides.rubyonrails.org/3_1_release_notes.html
>
> 大家对哪些feature比较感兴趣，我们可以做个demo的app

[Jonathan Palley]

对不起，我不会用中文解释, 但是。。。

Even though 3.1 is a "minor" upgrade, I think the new Sprockets/"assets" pipeline is a BIG deal and totally changes RoR from a "conceptual" standpoint.   RoR has stopped being Ruby on Rails and is now Web-App on Rails (using Ruby, Coffeescript/Javascript, SASL, and ultimately X - where "X" is whatever you technology you need to get the app done). 

I think we are going to see more and more gems that allow you to package all the different bits-and-pieces of technologies that make new apps into a nice convention-over-configuration structure in Rails.  I'm just speaking from personal experience: the current system I'm working on has many, many different technologies we are trying to merge together.  Right now the technologies are in different projects, in different git repositories.  After reading about sprockets I'm immediately thinking how to better merge the code into Rails.

Ironically, Ruby comes back to be how it was used BEFORE Rails.  Before Rails, its most popular use was as a scripting language to tie different parts of systems together.  Its essentially going to do that now, I think - but on steroids.

JP

2011/8/31 魏伦 Allen Wei <dig...@gmail.com>

http://guides.rubyonrails.org/3_1_release_notes.html

大家对哪些feature比较感兴趣，我们可以做个demo的app

--
--
微群：http://q.weibo.com/793783
--
You received this message because you are subscribed to the Google
Groups "Rails Wednesday" group.
To post to this group, send email to rail...@googlegroups.com
To unsubscribe from this group, send email to
railswed+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/railswed?hl=en?hl=en

[Andy]

@Jonathan - Good Points!

Btw, I think that's ok to write here in English, Thanks for sharing
your thoughts on Rails3.1.

Anyway, other quotes from one of my colleagues (on Rails3.1):

* SASS is awesome
* CS is neat, but I haven't bothered to learn it
* That's fine. You don't have to use SASS/CS.
* No need to do anything different other than putting your css/js
files in app/assets instead of public/
* Yeah, 3.1 requires sass-rails and coffee-rails gems. big deal. If
that ruins your day, you've got bigger problems.

On Sep 1, 12:03 am, Jonathan Palley <jpal...@gmail.com> wrote:
> 对不起，我不会用中文解释, 但是。。。
>
> Even though 3.1 is a "minor" upgrade, I think the new Sprockets/"assets"
> pipeline is a BIG deal and totally changes RoR from a "conceptual"

> standpoint. RoR has stopped being *Ruby *on Rails and is now Web-App on

> Rails (using Ruby, Coffeescript/Javascript, SASL, and ultimately X - where
> "X" is whatever you technology you need to get the app done).
>
> I think we are going to see more and more gems that allow you to package all
> the different bits-and-pieces of technologies that make new apps into a nice
> convention-over-configuration structure in Rails. I'm just speaking from
> personal experience: the current system I'm working on has many, many
> different technologies we are trying to merge together. Right now the
> technologies are in different projects, in different git repositories.
> After reading about sprockets I'm immediately thinking how to better merge
> the code into Rails.
>
> Ironically, Ruby comes back to be how it was used BEFORE Rails. Before
> Rails, its most popular use was as a scripting language to tie different
> parts of systems together. Its essentially going to do that now, I think -
> but on steroids.
>
> JP
>

> 2011/8/31 魏伦 Allen Wei <digr...@gmail.com>

[Allen Wei]

Totally agree with u, like the saying of "ultimately X". 

People may say no to some of the features Rails introduced but Rails is absolutely improve our productive.

When we are seeking better solution for some problems, Rails say: "Hey we have it in our next release". 

But I have concern: It will introduce some problem if Rails have kind of "big" feature too often.

You can see people spend lot's of time upgrade his Rails application, lot's gem don't have support to lower version Rails.

-- 
Allen Wei
Sent with Sparrow

[Jonathan Palley]

Allen -
  I think your concern is exactly what the Rails 3.X series is trying to fix: add a standard "plugin" interface and "abstract" out all dependencies to independent gems.  Like in 3.1 they switch the default js from prototype to jquery.  But, because these were extracted out in 3.0, it won't affect you.  If this was Rails 1 or Rails 2, it would be a big deal.

Of course Rails 3 broke gems from Rails 2 (due to how they were making this "standard API"), but I wonder if Rails 3.1 is breaking Rails 3 gems?  Are we now "safe"?  Have you seen any problems?

[Allen Wei]

yeah, Rails is trying hard to make standard api and make it modular. so we can replace any of the components. 

It's a right way to go, Rails is really belongs to the whole community.

I'd like to see lot's of good features are included in Rails.

I think it's backwards compatibility is a common problem for most of open-souce project, like python 2 and python 3.

Rails did great job to print deprecation warning before drop it.

Rails rocks! 

-- 
Allen Wei
Sent with Sparrow