git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] doc: replace jargon word "impact" with "effect"/"affect"

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
May 27, 2021, 14:08 UTC
Message-ID
<60afa7d9d4ca_2056d208d9@natae.notmuch>
In-Reply-To
<20210527114629.GD8544@kitsune.suse.cz>
Michal Suchánek wrote:
Show 19 quoted lines
> On Wed, May 26, 2021 at 06:49:58PM -0500, Varun Varada wrote:
> > On Thu, 13 May 2021 at 04:48, Michal Suchánek <msuchanek@suse.de> wrote:
> > > Yet Felipe insists that 'impact' is somehow generally bad word to use or
> > > that it should be abolished solely because he finds it bad and nobody
> > > objected to the alternative wording.
> > >
> > > Opinions on use of 'impact' differ both among the participants of this
> > > discussion and authorities like authors well-known dictionaries.
> > >
> > > It looks like this is generally matter of stylistic preferences and
> > > opinions. That is even if there is some slight stylistic preference for
> > > not using the word 'impact' it is very hard to prove such and then it is
> > > very hard to request change based only on writing style preferences.
> > 
> > The argument is not that it is generally a bad word to use, but that
> > it is generally bad to use words when they don't mean what one thinks
> > they mean, especially when all evidence says otherwise.
> 
> Not all evidence. There are people who think the use is fine.
What people think is not evidence.
There's people who think the Earth is flat.
> > All major dictionaries define "impact" as "a strong effect" or "to
> > affect strongly". This is not style, but semantics. In the same way
> 
> Not all dictionaries, actually.
You don't need all dictionaries.

If 50% of trials show a drug is safe, and 50% show it's not, you don't approve bit because "not all say say it's unsafe".

If there's evidence that A is bad, you should consider avoiding A, especially when you have B, and you have *zero* evidence showing B is bad.

Show 9 quoted lines
> > that "per se" being used to mean "necessarily" is not a style issue,
> > using "impact" to mean "an effect" or "to affect" is not a style
> > issue.
> > 
> > As has been stated already, the clear and substantial argument for
> > this change is that it reduces the confusion that arises from
> > improperly using the word "impact" in the instances without any loss
> 
> There is no final authority on 'correct' word use in English.
You don't need a final authority.
There is evidence that A is problematic.
> We should learn to work together with people that use different
> variant of the language rather than insist that the variant that I or my
> teacher uses is the only correct one and everyone else should use it.
Except one variant is problematic, and the other is not.
Do you have *ANY* evidence that shows a problem with "effect"?
-- 
Felipe Contreras
Previous: Michal SuchánekNext: Michal Suchánek
Message 49 of 68 in “doc: replace jargon word "impact" with "effect"/"affect"”
  1. doc: replace jargon word "impact" with "effect"/"affect"Varun Varada, Apr 5, 2021
  2. Michal SuchánekApr 6, 2021
  3. Varun VaradaApr 6, 2021
  4. Jeff KingApr 6, 2021
  5. Varun VaradaApr 7, 2021
  6. Varun VaradaApr 28, 2021
  7. Michal SuchánekApr 28, 2021
  8. Varun VaradaApr 28, 2021
  9. Michal SuchánekApr 28, 2021
  10. Varun VaradaApr 30, 2021
  11. Michal SuchánekApr 30, 2021
  12. Varun VaradaMay 10, 2021
  13. Michal SuchánekMay 10, 2021
  14. Varun VaradaMay 10, 2021
  15. Michal SuchánekMay 11, 2021
  16. Junio C HamanoMay 11, 2021
  17. Felipe ContrerasMay 12, 2021
  18. Felipe ContrerasMay 12, 2021
  19. Felipe ContrerasMay 12, 2021
  20. Felipe ContrerasMay 12, 2021
  21. Felipe ContrerasMay 12, 2021
  22. Felipe ContrerasMay 12, 2021
  23. Felipe ContrerasMay 11, 2021
  24. Michal SuchánekMay 11, 2021
  25. Varun VaradaMay 11, 2021
  26. Felipe ContrerasMay 12, 2021
  27. Michal SuchánekMay 12, 2021
  28. Felipe ContrerasMay 12, 2021
  29. Michal SuchánekMay 12, 2021
  30. Felipe ContrerasMay 12, 2021
  31. Michal SuchánekMay 12, 2021
  32. Michal SuchánekMay 12, 2021
  33. Felipe ContrerasMay 12, 2021
  34. Michal SuchánekMay 12, 2021
  35. Robert P. J. DayMay 12, 2021
  36. Kerry, RichardMay 12, 2021
  37. Varun VaradaMay 12, 2021
  38. Michal SuchánekMay 12, 2021
  39. Felipe ContrerasMay 12, 2021
  40. Michal SuchánekMay 12, 2021
  41. Felipe ContrerasMay 12, 2021
  42. Michal SuchánekMay 13, 2021
  43. Felipe ContrerasMay 13, 2021
  44. Robert CoupMay 13, 2021
  45. Michal SuchánekMay 13, 2021
  46. Felipe ContrerasMay 13, 2021
  47. Varun VaradaMay 26, 2021
  48. Michal SuchánekMay 27, 2021
  49. Felipe ContrerasMay 27, 2021
  50. Michal SuchánekMay 27, 2021
  51. Felipe ContrerasMay 27, 2021
  52. Varun VaradaJun 12, 2021
  53. Michal SuchánekJun 13, 2021
  54. Felipe ContrerasJun 13, 2021
  55. Michal SuchánekJun 13, 2021
  56. Felipe ContrerasJun 13, 2021
  57. Varun VaradaMay 12, 2021
  58. Felipe ContrerasMay 13, 2021
  59. Felipe ContrerasMay 12, 2021
  60. Felipe ContrerasMay 11, 2021
  61. Michal SuchánekMay 11, 2021
  62. Felipe ContrerasMay 12, 2021
  63. Michal SuchánekMay 12, 2021
  64. Felipe ContrerasMay 12, 2021
  65. Varun VaradaMay 12, 2021
  66. Philip OakleyMay 13, 2021
  67. Varun VaradaMay 26, 2021
  68. Philip OakleyMay 27, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.