On 3-jun-2006, at 19:47, Kevin Clark wrote:
-1 because with this you are manifesting that Rails IS perfect and
anyone who thinks the way it works should be upgraded has to either
make workarounds or create exceptionally breakable plugins that
override code.
I disagree. The problem is that the trac has been the place to ask for
everything under the sun . No one is going to get to your enhancement
request unless you do it yourself
I am speaking about enhancment tickets that have patches and test
coverage. Maybe you mean just generic "enhancement requests" (i.e. `I
want this and that` - without any code)?
Sure, discuss it on one of the lists and maybe someone will pick
it up, but enhancement tickets are rarely taken on unless a developer
has the same need.
Which doesn't seem too nice to me. If the ticket is 20 lines, is
understandable and has test coverage - what is the problem?
The point isn't that Rails is perfect, the point is that what could be
improved shouldn't be discussed on Trac.
If plugins are easily breakable, maybe they need a redesign?
Have you ever implemented a plugin that needed to change a tiny, but
substantial feature of the Rails code? You wouldn't be asking this if
you did. Going back to my own tickets, for instance:
http://dev.rubyonrails.org/ticket/4947
Can you show me a way to do this kind of thing non-intrusively? I.E.
without introducing the "every-single-darn-bolt-and-nut-is-a-
pluggable-component" madness with DI and the like.
I agree that tickets with code should be closed as "wontfix" faster
if the core doesn't like them at all. There is an enormous backlog of
both experimental and non-experimental patches.
--
Julian 'Julik' Tarkhanov
please send all personal mail to
me at julik.nl
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
