[wp-trac] [WordPress Trac] #13971: "Wordpress" being turned into CamelCase "WordPress" breaks URLs

[WordPress Trac]

#13971: "Wordpress" being turned into CamelCase "WordPress" breaks URLs
--------------------------+-------------------------------------------------
 Reporter:  tfotherby     |        Owner:        
     Type:  defect (bug)  |       Status:  closed
 Priority:  lowest        |    Milestone:  3.0.1 
Component:  Formatting    |      Version:  3.0   
 Severity:  normal        |   Resolution:  fixed 
 Keywords:  has-patch     |  
--------------------------+-------------------------------------------------

Comment(by chrisbliss18):

 So I'm late to the party, but I just have to throw my hat in this
 discussion. Honestly, I have to say that I'm amazed. Amazed and disturbed
 by this entire situation. And frankly, it's lowered my opinion of some
 developers that I have had very high regard for in the past.

 As a software developer, I am constantly concerned about making my code as
 efficient as possible. Why? Because I never know when some poor coding
 practice will make the difference between someone's server being able to
 handle the load and complete failure. And it is my responsibility as a
 coder to ensure that my code doesn't needlessly waste resources.

 Let's all be honest with ourselves and admit that this entire situation is
 silly and highly unnecessary. Some core devs chatted about their dislike
 of the misspelling and *BAM* in goes code. No concern over bugs (nor of
 the bug reports). No concern over the efficiency issue. No concern over
 the freedom of words that Matt talked about in San Francisco. No concern
 over anything other than personal pet peeves. Frankly, it's unacceptable.

 Now some may argue that it is insignificant in the grand scheme of the
 code stack. True, but it is mighty absurd to add to the execution stack
 over the need to scratch an itch. Beyond that, it's rude to the community
 at large to leverage core contributor authority over such trivial matters
 and an amazing level of arrogance to be so dismissive when genuine issues
 and complaints come up. On top of that is how we are wasting valuable devs
 time trying to "optimize" and "improve" such code to not have bugs when
 its value is nil to begin with.

 "It's plugin territory" should be reserved for adding trivial bits of
 code, not for adding more code to remove the actions of trivial bits of
 code. "Acceptable edge cases" should be reserved for solving issues that
 are genuine software or usability issues which has benefit that outweighs
 the detriment. "Let's stop wasting our time" should be reserved for
 commentary about adding such trivial code not for commenting on the outcry
 to remove such trivial code. "It can be removed with one line of code"
 should only affect developers and not users. Marking a legitimate bug as
 "fixed" when it has neither been properly addressed nor fixed is also a
 critical problem.

 Citing other filter actions such as autop, et al as justification for such
 short-sighted actions is absurd. Those filters add what most would agree
 is benefit to the user. Since most would easily, seamlessly, and without
 complaint benefit from these filters without a chance of a site-breaking
 bug, using their existence and general acceptance for justification is
 irrational.

 Since the only benefit of this filter is perceived (the devs who like this
 and support its inclusion "feel" better about the world due to its
 existence), the staunch determination to keep the code in spite of the
 massive backlash is inane. To uphold the inclusion of the code based upon
 the only justification being "I don't like seeing it spelled that way" is
 to hold your personal beliefs above those of the other millions of users
 of WordPress... across the world... regardless of language or technical
 skill.

 The only obvious answer from a software development, project management,
 public relations, or community management standpoint is to remove it.
 There simply is no rational reason on any level to keep it, no matter what
 your opinion or lack of opinion about the spelling of WordPress is.

 If WordPress is truly a community project as numerous Automattic employees
 and core contributers constantly profess, how can it be that things like
 this (which everyone admits is trivial) which has massive negative
 community feedback are still so difficult to affect change in. This is the
 true heart of the issue: the helpless feeling of the community to make
 even the slighted shift in core contributer opinion on the most trivial of
 matters. I think it is this central issue that will leave a stain on devs
 opinion of WordPress, Matt, and core contributers for some time to come.

 Can devs and users walk? Surely, but the point is that people don't truly
 want to walk over something so stupid. At least make it a fight worth
 fighting.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/13971#comment:75>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software