2 ms·
It can go both ways, there are engineers who use their prior knowledge to understand where the design principles come from yet acknowledge the current state of
by neonsunset 2y ago
It can go both ways, there are engineers who use their prior knowledge to understand where the design principles come from yet acknowledge the current state of affairs and there are engineers which use it as an excuse to ignore anything that happened past their active learning phase.
I worked with sufficient amount of the latter type to remind myself everyday to be wary of this failure mode, and to appreciate the former when such people do come by.
- pjmlp 2y agoI agree, but hardly any of your replies were into the sense of what WinDev is doing to support .NET on Windows like Swift are Java/Kotlin are on their respective platforms, instead of their usual COM and C++ agenda, rather what DevDiv, rogue engineers we should be thankful for their sice project efforts, and FOSS .NET community. Yes the community is doing lots, WinDev is not.
- neonsunset 2y agoMy goal was to provide context on what is out there in terms of consumption of Windows APIs (many people are hand-rolling bindings, where they could have added CsWin32/Rt and two lines to an imports file, or write a complex C++ sandwich for DX12 where they could have consumed it, effectively, directly) and to that extent it is achieved :) We don't know what is current WinDev situation, FWIW COM interop changes in .NET are "official" rather than grassroots, but then again, MSFT is pretty much a huge conglomerate of smaller sized companies rather than a huge monolithic entity.