https://bugs.kde.org/show_bug.cgi?id=404313
arcli...@gmail.com <arcli...@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |ASSIGNED --- Comment #4 from arcli...@gmail.com <arcli...@gmail.com> --- I apologise, it is clear from your response that you are indeed unable to understand what it means to have a piece of application code misbehave because the author has no awareness of basic ettiquette. Not only does it, your code, fail to follow best practices in checking and negotiating control of multiple instances of its own existence, with the 'very least of iterative code investment', so to maintain code validity at all times. But it fails to prevent serious inconvenience to the end user and their execution space as they attempt to get work done in what is generally termed a 'tight schedule'. This is outrageous, crude coding that breaks trust in Linux applications. Gone are the days where chucking rubbish at users is even close to adequate because there is serious competition in the marketplace. Have you thought of working for Microsoft? In such circumstances your contribution for all its legendary capabilities is not yet house trained. A virus in your clear experience is a valid piece of code since it contains no bugs! Apart from my disbelief, you have clearly done substantial research to get this far. Just think how far you would get if your editor/compiler or IDE simply screwed up your code but provided you with no error narratives? Could you stick with having to hand code every byte without access to any libraries? Should I care about your situation at all? Most programmers work in teams. I think you will find it is because after work everybody gets a kick from sharing a good laugh - because getting to know each others values make life much brighter, from which our collective code is much sharper! -- You are receiving this mail because: You are watching all bug changes.