On 28 May 2010 07:24, Norman Clarke <[email protected]> wrote:
> Why? SQLite3 was made the default database in 2.0.2 and the world
> didn't stop. It's a change that affects people creating new Rails
> applications - not ones that have already been created.
>
There's a big difference between changing the default database system and
changing the default javascript engine. For a very basic example:
Model.create will work the same on whatever database system you're using
where $('blog_1') will behave differently depending on the javascript
engine.
I see your point.
>
> I'm a big fan of jQuery too but maybe at this point it would be nice
> to take an issue off the core team's table. At the end of the day
> Rails 3 is still going to work great no matter what the default is.
>
Indeed and I'll agree with Yehuda here. 3.0's gotta be out soon, right?
>
> On Thu, May 27, 2010 at 17:59, Ryan Bigg <[email protected]> wrote:
> > I would not go changing this in a minor release. Major or bust.
> >
> > Ryan Bigg / Radar
> >
> > On 28/05/2010, at 1:58, Norman Clarke <[email protected]> wrote:
> >
> >> On Thu, May 27, 2010 at 12:45, Xavier Noria <[email protected]> wrote:
> >>>
> >>> On Thu, May 27, 2010 at 5:32 PM, Yehuda Katz <[email protected]> wrote:
> >>>
> >>>> The idea that 16% of Rails users use jQuery is divorced from reality.
> >>>
> >>> But you are talking perceptions, and the sample talks numbers.
> >>>
> >>> Of course 16% has to be taken with some margins, but you can't deny it
> >>> makes difficult to claim that the vast majority of Rails developers
> >>> use jQuery exclusively, which was the claim in (1). That is a strong
> >>> claim! (1 was originally stated as a feeling not a fact, that's fine).
> >>>
> >>> If the percent had been 84% then there would be no doubt about it,
> >>> right? But < 20%... dubious.
> >>
> >> This is why I stated that once Rails 3 comes out, it should be easier
> >> to get some "real" numbers on this, since presumably it will be just
> >> as easy for developers to use jQuery as it currently is to use
> >> Prototype, and those users
> >> who actively program in Javascript rather than just using the helpers
> >> will consciously decide to use one or the other.
> >>
> >> I would suggest it's a bit late to change the default option at this
> >> time, and if the decision is left for 3.1 it can easily be based at
> >> least in part on real-world numbers that nobody disputes.
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups
> >> "Ruby on Rails: Core" group.
> >> To post to this group, send email to [email protected].
> >> To unsubscribe from this group, send email to
> >> [email protected]<rubyonrails-core%[email protected]>
> .
> >> For more options, visit this group at
> >> http://groups.google.com/group/rubyonrails-core?hl=en.
> >>
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Ruby on Rails: Core" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected]<rubyonrails-core%[email protected]>
> .
> > For more options, visit this group at
> > http://groups.google.com/group/rubyonrails-core?hl=en.
> >
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<rubyonrails-core%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/rubyonrails-core?hl=en.
>
>
--
Ryan Bigg / Radar
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
