Content deleted Content added
Stevebroshar (talk | contribs) →communication among different Windows applications: new section |
Stevebroshar (talk | contribs) →wrappers: new section |
||
Line 150:
The paragraph with "communication among different Windows applications" seems to be about stuff that Windows API is not. Suggest: remove it. [[User:Stevebroshar|Stevebroshar]] ([[User talk:Stevebroshar|talk]]) 11:28, 29 January 2024 (UTC)
== wrappers ==
Most of the tech listed as wrappers are not what I'd call a wrapper. IMO a wrapper exposes roughly the same capabilities as the wrapped tech -- just in a different form (interface). Just because one tech uses another tech, does not make it a wrapper. Consuming is not wrapping.
Wrapping requires design intent to replace all consumption need for the underlying tech. For example, MFC and ATL are not intended to replace all consumer need for Windows API.
Taking a step back: What is the point of this section? For example, it says MFC uses Windows API. ok. Everything built for Windows uses Windows API. What is interesting about MFC doing that? Goes without saying. Adds no value.
Suggest: Either remove this section or at least that these other techs are wrappers -- just list them as other Microsoft Windows tech that the reader might want to peruse. [[User:Stevebroshar|Stevebroshar]] ([[User talk:Stevebroshar|talk]]) 11:54, 29 January 2024 (UTC)
| |||