[development] has this been discussed here?

[Dries Buytaert]

On 26 Dec 2006, at 15:49, Eric Goldhagen wrote:
> http://drupal.org/node/87145
>
> I seem to have missed any discussion of this issue.
>
> I feel very strongly that a bad decision is being made based on bad  
> reasoning. In my opinion the break tag is not broken and changing  
> it is not helpful or wise.

I strongly suggest you add your arguments to the issue.  Scattering  
the discussion makes it hard to keep an overview.  For most people,  
such an overview doesn't really matter, but for issue reviewers like  
me, it does.  Keeping on top of the issue tracker is one thing,  
keeping on top of both the fora, the mailing lists, and the issue  
tracker is virtually impossible, and introduce lots of redundancy.   
Important comments should go in the issue or they might not get my  
attention/consideration.  Not because I'm unwilling, but because of  
the sheer volume.  Thanks.  :)

That said, I _still_ have to read up on the issue follow-ups but last  
time I checked (1 week ago), this particular issue seemed to be a  
tough one.  From what I remember, quite a few people didn't care to  
research the problem before sharing their opinion.  Their gut feeling  
tells them that <!--break--> is semantically better, without knowing  
what is going on under the hood.  As a result, the issue carries  
quite a number of incorrect assessments and fair amount of personal  
taste.

Of course, "gut feeling" matters too ... it is closely related to  
"the first impression".  Gut feeling is not something we can discard,  
but I highly recommend people to invest some time into this before  
sharing their opinions.  It helps us focus.

Either way, I'll read up on the issue in a couple of days.  I'll  
probably have to sit down and spent an hour with that particular  
issue.  Hopefully, things have settled by than.  If not, I'll make a  
decision based on the information available in the issue, the  
collective gut feeling, and the technical arguments that appear sound.

--
Dries Buytaert  ::  http://www.buytaert.net/