[Bug 253398] KFind has no menu item under Tools in Konqueror or Dolphin

[Gérard Talbot]

https://bugs.kde.org/show_bug.cgi?id=253398





--- Comment #20 from Gérard Talbot <browserbugs gtalbot org>  2011-09-02 01:52:58 ---
Reindl,

I'm not going to try to convince you that your judgement is wrong, excessively
harsh, very unfair and inappropriate. But I hope one day you get to know what
is C++ (how fun C++ is!) and how many lines of code there is behind the whole
Konqueror software. There's probably 1 million lines of code.

C++ is foremost about reusing code; defining functions once and then reusing
those in as many components as possible. It's about shared libraries, reusing
modules, defining classes and interfaces, prototyping, etc. So, if you make a
change in a block or a module, it may, it can and it usually will have impacts
(and unwanted, unknown, unpredicted side effects) elsewhere, in other blocks
and modules not targeted.

A developer who is alone (this is the case here for KDE and the KHTML rendering
engine) to tackle bugs and fix bugs, who has no experienced reviewer, no
reviewer at all, no testers, no team of people to help is going to make
mistakes, unfortunate mistakes, honest mistakes. He would make mistakes
nevertheless and despite having reviewers, testers helping him. No developer
can know very well and intimately 1 million lines of code that have been
written and rewritten by dozens of people over the years and how such million
lines of code will interact when making a 1 line change in it.

Now, regarding your "IF IT AIN'T BROKEN DON'T FIX IT", that's called regression
bugs by professionals. And regression bugs happen often: that's the reality of
modern technology. Happens often in professional development software done by
IT corporations like Microsoft, Intel, HP, Dell, Apple, Google, etc. and in
other technological areas too (eg car manufacturers, airplanes manufacturers,
etc). I could name many famous regression bugs which have been widely
documented in public. 

Regression happens so often that, for your information, webkit and
bugzilla.mozilla even developed 2 keywords just to identify regression bugs:
regression and regressionwindow-wanted. Microsoft also uses this too in their
internal databases.

Just verify for yourself:

https://bugzilla.mozilla.org/describekeywords.cgi
identifies 27937 bug reports which are regression bugs 
https://bugs.webkit.org/buglist.cgi?keywords=Regression&resolution=---
and 443 regression bugs 
https://bugzilla.mozilla.org/buglist.cgi?keywords=regressionwindow-wanted&resolution=---
where they don't even know within which period of time and between which build
numbers the regression occured by change in the code. That's over 28,000
situations (components, functionalities, features, etc) which were working
accordingly, which were not broken and then broke.

https://bugs.webkit.org/describekeywords.cgi
identifies 2703 bug with the regression keywords: that is 2703 situations where
"something was working accordingly and then it broke"

Gérard

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.