Most developers I've met or talked to online are lazy when it comes to supporting something they didn't account for from the start of a project. Especially in open source and volunteer projects or that involve a set of changes that span many files or functions. It is easier to say "no" than to actually support somethingRon wrote:I've already researched this whenever the first wikipedia link with a paren was posted here. The general consensus I've found is that most developers are just saying "No" when allowing parens in URL's because they are generally unsafe, and I agree.
To allow parens like wikipedia does is a safe practice for them because they are parsing the URI in the end. But it has an impact on any software that tries to work with their seemingly malformed links. It's just bad practice.

I had to let go of two PSU-educated programmers about 4 years ago because they would say something is impossible or shouldn't be done either because they really thought it so or they were to lazy to do it right.
Turns out that it was a mixure of both stupidity and laziness and they were completely wrong about their stance, only added a few pages of code and 10 hours of time in the project they were let go over...
I've made many lines of code to deal with the stupidity of users when you present them a text box (still havn't figured out a function to cure my own). So I do understand the choice. But if it were so unsafe, then phpbb3 and vbulletin would disallow usage of them in links, and they don't.
At least can we have HTML links back?